400 Error initiating cobrowse via /api/v2/conversations/messaging/{id}/actions

Why does this setting reject my cobrowse init request with a 400?

POST /api/v2/conversations/messaging/{conversationId}/actions

Payload:

{
 "actions": [
 {
 "action": "cobrowse",
 "cobrowse": {
 "type": "initiate",
 "mode": "view"
 }
 }
 ]
}

Response:

{
 "errors": [
 {
 "message": "Invalid action type 'cobrowse' for messaging channel. Supported actions are [send, update]",
 "code": "bad_request",
 "status": "400"
 }
 ]
}

The Genesys Docs list cobrowse as a valid action, but only for voice/video contexts. I’m trying to trigger a shared view from a web chat session. Is there a different endpoint or a specific header needed to enable this for messaging? Or is this strictly a client-side SDK thing and the server API just blocks it?

I’ve checked the conversation state, it’s active. Not sure if the media type mismatch is hard-coded in the validator.

What’s happening here is that cobrowse isn’t a valid action for the messaging channel, you need to use send-cobrowse-request instead.

{
 "actions": [
 {
 "action": "send-cobrowse-request",
 "cobrowse": {
 "type": "initiate",
 "mode": "view"
 }
 }
 ]
}

check the docs for supported actions per channel type.