Getting Started with Flux TTS Batch (REST)
Getting Started with Flux TTS Batch (REST)
Synthesize a complete block of text into a single audio file with the Flux TTS batch endpoint — POST /v2/speak — for pre-rendering fixed audio.
The batch (REST) transport synthesizes a complete block of text and returns the full audio in one response. Use it to pre-generate fixed audio — IVR prompts, notifications, audiobook lines — where the whole text is known up front and you don’t need incremental playback or interruption. For live, interruptible conversations, use the real-time WebSocket instead (see Batch vs Streaming).
Batch is stateless request/response: simple retries, high fan-out, no connection lifecycle to manage. It serves the same Flux voices as the streaming transport.
Make a request
The response body is the synthesized audio in the requested encoding. Per-request telemetry is returned as response headers, mirroring Aura’s REST conventions — including character counts. Pronunciation tallies (dg-pronunciations-applied) and the generic dg-warnings header are planned for GA.
Query parameters
Conversational constructs (Flush, speech_id, lifecycle events) do not apply to batch. model and the media-output settings behave the same as on the streaming surface, so the contract doesn’t fragment across transports. (speed is planned for GA, alongside streaming.)
When to use batch vs streaming
See Batch vs Streaming: Which Should I Use? for the decision guide.
Related resources
- Batch vs Streaming
- Real-Time / Conversational Getting Started
- Voices and Languages
- Media Output Settings