I’m trying to set a wrap-up code programmatically right after a call ends. The interaction is already in the terminated state, but every time I send the PATCH request, I get a 409 Conflict.
Here’s the JSON payload I’m sending:
{
"wrapup": {
"code": "W001-CloseTicket",
"time": 120,
"note": "Automated closure"
}
}
The endpoint is PATCH /api/v2/conversations/calls/{conversationId}. I’ve verified the auth token has conversation:write scopes, and the user ID in the token is assigned to the queue handling these calls. The error message just says “Conflict” with no extra details in the response body.
If I wait a few seconds before sending the request, it works fine. But waiting isn’t an option for our automation flow. Is there a specific state I need to wait for, or is the API just rejecting rapid wrap-up assignments? I’ve tried adding the wrapup object to the routing property as well, but that gives me a 400 Bad Request saying the field is unexpected.