Skip to main content
The Avaturn.Live API manages session lifecycle. Create a session with a conversation engine config; receive a session_id (backend handle) and a token (frontend credential).

​
Authentication

All endpoints require an Authorization: Bearer <API_KEY> header. API keys are issued in the dashboard.
API keys must stay on the backend. Anyone with the key can act on your behalf — rotate immediately in the dashboard if compromised.

​
Base URL

​
Errors

Endpoint-specific error codes are listed in each operation’s reference page. Common patterns:
  • 400 Bad Request — invalid payload (e.g. unknown voice_id, invalid render_model for the chosen avatar).
  • 401 Unauthorized — missing or revoked API key.
  • 410 Gone — avatar_id no longer exists.
  • 422 Unprocessable Content — missing required engine field (e.g. client_secret for openai-realtime).