Hey folks,
Trying to push a call to a different queue from my backend service using the Conversations API. The idea is straightforward: grab the active conversation ID, send a PATCH with the target queue ID in the routing object, and let the platform handle the rest.
I’m hitting PATCH /api/v2/conversations/voice/{conversationId} with this payload:
{
"routing": {
"queueId": "550e8400-e29b-41d4-a716-446655440000"
}
}
The API returns a 200 OK, which feels good. But when I check the conversation in the admin UI, the call is still sitting in the original queue. It doesn’t jump to the new one. I’ve verified the target queue ID is valid and has agents logged in.
I know I can use the transfer action in Architect, but I need this to happen via API call based on external data. Is there a specific flag I’m missing in the routing object? Or do I need to call a different endpoint to actually trigger the re-routing? The docs are a bit vague on the difference between updating the routing config and actually moving the interaction.
Appreciate any pointers.