AsyncAPI channel · cartesia · Cartesia Streaming WebSocket APIs

/stt/turns/websocket

Ink STT Turns WebSocket. Clients send binary audio frames plus an optional JSON `close` control frame. The server emits `connected`, `turn.start`, `turn.update`, `turn.eager_end`, `turn.resume`, `turn.end`, and `error` events.

Open source AsyncAPI → All cartesia channels cartesia provider profile
Provider: cartesia AsyncAPI: v2.6.0 Spec: Cartesia Streaming WebSocket APIs Operations: 2 Messages: 9

Channel address

/stt/turns/websocket

Operations

publish
sttTurnsClientFrame
Client → Server frames for Ink STT Turns.
sttTurnsServerFrame
Server → Client frames for Ink STT Turns.

Messages

sttAudioBinary
Raw audio bytes matching the negotiated encoding and sample rate.
Content-Type: application/octet-stream
sttTurnsClose
JSON `{ "type": "close" }` control frame for the Turns WebSocket.
Content-Type: application/json
sttTurnsConnected
STT Turns Connected
Content-Type: application/json
sttTurnStart
STT Turn Start
Content-Type: application/json
sttTurnUpdate
STT Turn Update
Content-Type: application/json
sttTurnEagerEnd
STT Turn Eager End
Content-Type: application/json
sttTurnResume
STT Turn Resume
Content-Type: application/json
sttTurnEnd
STT Turn End
Content-Type: application/json
sttTurnsError
STT Turns Error
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.