AsyncAPI channel · Retell AI
· Retell AI WebSocket APIs
audio/{call_id}
Audio WebSocket channel (deprecated). Carries raw audio bytes from the frontend microphone to Retell, and a mix of raw audio bytes plus JSON / string control events from Retell back to the frontend.
Channel address
audio/{call_id}
Parameters
call_id— Identifies the call and authenticates the connection.
Operations
publish
clientToRetell
Messages sent from the frontend client to Retell.
subscribe
retellToClient
Messages sent from Retell to the frontend client.
Messages
ClientAudioFrame
Raw microphone audio bytes streamed in 20-250ms chunks.
Content-Type:
application/octet-streamAgentAudioFrame
Raw binary agent audio response bytes, emitted when
`enable_audio_alignment=false`.
Content-Type:
application/octet-streamAudioClear
String literal "clear" sent when the user interrupts the agent so the
client can flush any buffered agent audio.
Content-Type:
text/plainAudioUpdate
Live call update containing transcript and optional turn-taking info.
Content-Type:
application/jsonAudioAlignment
Emitted when `enable_audio_alignment=true`. JSON envelope containing
base64-encoded agent audio aligned with the corresponding text.
Content-Type:
application/jsonAudioMetadata
Custom metadata forwarded from the LLM server to the frontend.
Content-Type:
application/jsonAbout 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.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.