Skip to main content
AI sessions are created automatically when a voice agent connects to a call. The control endpoint lets your AI service (or any authorized caller) send telephony commands to an active session.
For the full list of 25 control verbs with detailed parameters, see the Control API reference.

Send a control event

Dispatches a telephony verb to an active AI session. Your AI service calls this endpoint during or after a conversation to transfer, hang up, set dispositions, manage conferences, and more.
Status: 200 OK

Authentication

Two auth options — use whichever fits your architecture: Callback tokens are delivered in the metadata frame when the WebSocket connects. They auto-rotate at 25 minutes via a token_refresh text frame — your AI service should swap to the new token on receipt.

Request body

Response

Rate limit

10 requests per second per call_id. Exceeding returns 429.

Revoke a callback token

Immediately invalidates a per-call callback token. Use this when your AI service detects a token compromise or needs to force a session handoff.
Scope: ai_sessions:control_admin  |  Status: 200 OK

Response

Token revocation requires ai_sessions:control_admin scope — callback tokens cannot revoke themselves. The token’s embedded call_id must match the URL path call_id (tenant fence).

Control verbs reference

The control endpoint supports 25 verbs organized in three groups: See the Control API reference for detailed parameters, idempotency behavior, and error codes for each verb.

Errors