Provider:ElevenLabsAsyncAPI: v2.6.0Spec: ElevenLabs Conversational AI EventsOperations: 2Messages: 9
Channel address
/conversation
Operations
publish
receiveConversationEvent
Receive conversation events from the agent
subscribe
sendConversationInput
Send input to the conversation
Messages
conversation_initiation_metadata
Metadata sent when the WebSocket connection is established
Content-Type:
audio
Audio chunk from the agent's speech output
Content-Type:
agent_response
Text of the agent's response
Content-Type:
user_transcript
Transcription of the user's speech input
Content-Type:
conversation_end
Signals the end of the conversation
Content-Type:
interruption
Signals that the agent was interrupted
Content-Type:
ping
Server ping for connection keep-alive
Content-Type:
user_audio_chunk
Audio chunk from the user's microphone
Content-Type:
pong
Client pong response to server ping
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.