Conversations API POST /cobrowse/session returns 400 Bad Request with invalid_session_token

Trying to spin up a cobrowse session programmatically for a custom agent assist tool. The UI cobrowse works fine, but hitting the API endpoint directly fails. I’m using the Node SDK to generate a valid JWT for the agent, then passing that token to the conversation init endpoint.

const response = await client.conversationsApi.postConversationsCobrowseSession({
 body: {
 agentId: '12345',
 customerEndpoint: {
 address: 'user-abc@domain.com',
 type: 'email'
 },
 settings: {
 mode: 'view',
 timeout: 300
 }
 }
});

The response is a 400 with message: Invalid session token provided. Ensure the token is valid and not expired. I’ve double-checked the token generation logic and it’s valid for other endpoints. The agentId exists and is online. Am I missing a specific header or scope requirement for cobrowse that isn’t documented in the OpenAPI spec? The SDK type definitions don’t show any extra fields for the request body. Checked the console logs on the agent side but nothing shows up when the API call fires. Just getting the 400 back.

Stop sending type: 'email' in the endpoint object. Cobrowse is a digital channel, so that field needs to be type: 'cobrowse' or omitted entirely to let the API infer it. Fix that and the 400 will vanish.