POST /api/v2/conversations/calls failing to initiate cobrowse session

Hey folks,

Trying to kick off a cobrowse session programmatically via the Conversations API. We’ve got the call initiated fine, but the cobrowse handshake seems to be dropping.

I’m sending the request to POST /api/v2/conversations/calls with the cobrowse config in the body. Here’s the payload structure I’m using:

{
 "from": {"id": "12345678-1234-1234-1234-123456789abc"},
 "to": [{"id": "87654321-4321-4321-4321-cba987654321", "type": "user"}],
 "type": "cobrowse"
}

The API returns a 200 OK, so the call object is created. But the agent side never receives the cobrowse invitation. The call state stays in ‘ringing’ indefinitely. I’ve checked the user permissions and they have the right roles.

Am I missing a specific header or is there a separate endpoint to trigger the actual cobrowse session once the call is established? The docs are a bit vague on the sequence for programmatic initiation versus the web client flow.