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.

Provider: Retell AI AsyncAPI: v2.6.0 Spec: Retell AI WebSocket APIs Operations: 2 Messages: 6

Channel address

audio/{call_id}

Parameters

Operations

publish
clientToRetell
Messages sent from the frontend client to Retell.
retellToClient
Messages sent from Retell to the frontend client.

Messages

ClientAudioFrame
Raw microphone audio bytes streamed in 20-250ms chunks.
Content-Type: application/octet-stream
AgentAudioFrame
Raw binary agent audio response bytes, emitted when `enable_audio_alignment=false`.
Content-Type: application/octet-stream
AudioClear
String literal "clear" sent when the user interrupts the agent so the client can flush any buffered agent audio.
Content-Type: text/plain
AudioUpdate
Live call update containing transcript and optional turn-taking info.
Content-Type: application/json
AudioAlignment
Emitted when `enable_audio_alignment=true`. JSON envelope containing base64-encoded agent audio aligned with the corresponding text.
Content-Type: application/json
AudioMetadata
Custom metadata forwarded from the LLM server to the frontend.
Content-Type: application/json

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.

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.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel
curl "https://apis.io/api/v1/channels/audio-call-id"
All event channels
curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

A second provider on the same verified email joins the account you already have.