PATCH /api/v2/conversations/voice/{id}/participants disconnecting wrong leg

NICE CXone API & Integrations
1

Trying to drop a specific participant from an active conference using the Conversations API. The request to disconnect a participant returns 200 OK, but the customer gets hung up instead of the agent. Tried setting the state to dropped in the routing block.

{
 "routing": {
 "state": "dropped"
 }
}

Is the participant ID correct for the agent leg?

2 Likes
2

You’re missing the participantId in the request path or body. The API defaults to dropping the initiator if you don’t explicitly target the agent’s ID. Check the conversation participants endpoint to grab the right ID first.

3

Yeah, you need to specify the participant ID in the URL path when updating a participant. Sending a body without that path parameter just hits the default leg, which is why the customer gets dropped.