POST /api/v2/conversations
{
“type”: “cobrowse”,
“to”: [
{
“id”: “user-12345”,
“type”: “user”
}
]
}
Getting a 400 Bad Request with message “Invalid conversation type for this endpoint”. The docs mention cobrowse is supported, but I’m clearly missing something in the payload structure or the initial handshake requirements.
I’ve tried adding "subject": "Support Session" and explicit "from" fields with the agent’s user ID, but the error persists. The goal is to start this session programmatically from a custom Client App widget, not through the standard UI flow.
Checked the event logs on the target user’s side-nothing shows up. No pending requests, no errors. It’s like the request never leaves the gate.
Is there a specific pre-requisite configuration I need to enable on the user profile or organization level before the API accepts this? Or is cobrowse initiation strictly UI-bound and I’m barking up the wrong tree?