AsyncAPI channel · PlayHT · PlayAI Realtime WebSocket APIs

/playht-tts/stream

TTS streaming channel for the Play3.0-mini model. Clients send JSON TTS command frames and receive JSON `start` / `end` control frames interleaved with binary audio chunks. The `fal_jwt_token` query parameter is obtained from the websocket-auth endpoint. The `/playht-tts-ldm/stream` path is used for the PlayDialog model, and similar per-model paths are returned for the other PlayDialog variants.

Open source AsyncAPI → All PlayHT channels PlayHT provider profile
Provider: PlayHT AsyncAPI: v2.6.0 Spec: PlayAI Realtime WebSocket APIs Operations: 2 Messages: 4

Channel address

/playht-tts/stream

Operations

publish
sendTtsCommand
Send a TTS synthesis command.
receiveTtsStream
Receive TTS synthesis events and audio.

Messages

TtsCommand
Synthesize text on the streaming TTS connection.
Content-Type: application/json
TtsStart
Marks the start of a TTS response stream for a given request_id.
Content-Type: application/json
TtsAudioChunk
Binary audio frame delivered between the `start` and `end` JSON frames. The payload bytes match the configured `output_format` (for example MP3 for `audio/mpeg`).
Content-Type: application/octet-stream
TtsEnd
Marks the end of a TTS response stream for a given request_id.
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.