AsyncAPI channel · Sanas
· Sanas Stream API
/v3/stream
Bidirectional WebSocket carrying JSON control text frames and PCM audio binary frames.
Channel address
/v3/stream
Operations
send
sendControl
receive
receiveEvents
Messages
init
Opens the session and declares input/output sample rates.
Content-Type:
application/jsonconfigure
Sets or reconfigures the translation pipeline (languages, voice, glossary, features); server replies with configured when ready. Carries optional request_id for correlation.
Content-Type:
application/jsonflush
Manually finalizes the current turn; server confirms when fully processed.
Content-Type:
application/jsonconfigured
Confirms the pipeline is ready to accept audio; echoes request_id.
Content-Type:
application/jsontranscript
Source and target transcript segments delivered as JSON.
Content-Type:
application/jsonerror
Application-level error event on the stream.
Content-Type:
application/jsonaudioFrame
Raw PCM audio bytes carried as a WebSocket binary frame (not JSON/base64).
Content-Type:
application/octet-streamAbout 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.