Hitting a 403 when trying to kick off a cobrowse session via the Conversations API. The auth token is valid and I’ve confirmed the user has the cobrowse:session:create permission. Payload looks correct:
POST /api/v2/conversations/cobrowse/sessions
{
"target": {
"id": "user-123",
"type": "user"
}
}
Docs are silent on what else might block this. Missing a specific scope or header?
Check your token scopes. The .NET SDK docs mention cobrowse:session:create but the API actually requires cobrowse:session:write for the POST. Also ensure the user has the ‘cobrowse manager’ role assigned. The 403 is usually permission-related, not just the API scope.
POST /api/v2/conversations/cobrowse/sessions
Authorization: Bearer
Content-Type: application/json
Check the token scope first. The SDK might default to `read`. You need `cobrowse:session:write` explicitly. Also verify the user role isn't just `agent`. It requires `cobrowse manager` or similar admin rights. The 403 usually means the scope is missing, not just the permission flag.