Overview
Support sessions enable customer-agent interactions with role-based features. The SDK provides support session management for both customers and agents.Starting a support session (provisioning)
A support conversation is bot-eligible only when it’s linked to a customer + app. Use one of these endpoints to open one and get an SDK token for the visitor — then connect the SDK with them.Server-side (one call)
POST /apps/:id/support-sessions — auth with X-Api-Key + X-Api-Secret (or a dashboard JWT in dev).
Mints an SDK token and opens an app-linked support conversation in a single call.
Anonymous (public key, no secret)
POST /sdk/anonymous-session — browser-callable with X-Api-Key: <public key> for
unauthenticated visitors. The request Origin must be in the app’s allowed_origins (set via
PATCH /apps/:id). Great for static sites — this is what the widget’s anonymous mode calls.
Update a visitor’s contact info
PATCH /sdk/customers/me — auth with the SDK token. Lets a visitor add their name/email after
starting (e.g. from a pre-chat form), so agents can reach them.
Getting a Support Session
Roles
Support Session API
Checking Role
Session Status
Session States
Listening for Events
Customer Flow
Agent Flow
React Integration
Support Events
Complete Example
Next Steps
Conversations
Conversation management
Messaging
Sending messages
Examples
Complete examples
Support Routing
Support routing guide