Session lifecycle
Create a session
POST /api/v1/sessions with a conversation engine config. Response contains session_id (backend) and token (frontend).Hand the token to the frontend
The
token is the only credential the browser needs. The Web SDK uses it to join the avatar room over WebRTC.Terminate the session
DELETE /api/v1/sessions/{id} when you’re done, or rely on auto-termination (user_absent_timeout / max_duration).