Overview
Stream raw PCM audio frames and receive transcript segments as speech is detected. The server uses Voice Activity Detection (VAD) to identify speech boundaries and returns a transcript for each segment.Endpoint
Connection Headers
All configuration is passed as WebSocket upgrade headers at connection time. Headers cannot be changed mid-session — reconnect with new headers to change settings.
Choosing the right sample rate:
Connection Flow
A WebSocket session follows a strict sequence:- Client connects — opens a WebSocket to
/stt/v3/streamwith all required headers. - Server confirms — immediately sends a
connectedmessage echoing the active configuration. - Client streams audio — continuously sends binary frames of raw PCM audio at a steady real-time cadence.
- Server detects speech — VAD identifies end-of-speech boundaries and emits a
processingmessage to acknowledge that a segment was captured. - Server returns transcript — sends a
transcriptmessage with the transcribed text, segment metadata, and latency. - Either side closes — client or server may close the connection at any time.
The
processing message is a low-latency signal that audio was captured and transcription has begun. Expect a transcript message shortly after.Audio Format & Sending Audio
All audio must be sent as raw PCM binary frames over the WebSocket. No container format (WAV, MP3, etc.) is accepted mid-stream.PCM Specification
Sending Rules
- Each binary frame must be exactly 1,024 bytes.
- Frames must be sent at real-time cadence — one frame every 32 ms (16 kHz) or 64 ms (8 kHz). Do not buffer and burst; this degrades VAD accuracy.
- For
44100and48000Hz sources, the server resamples internally — still send 1,024-byte frames at the appropriate cadence.
Server Messages
The server sends JSON text frames. All messages share atype discriminator field and an ISO-8601 timestamp.
connected
Sent once immediately after the WebSocket handshake succeeds.
processing
Emitted when VAD detects the end of a speech segment and transcription has begun. Use this as a low-latency acknowledgment that audio was captured.
transcript
Contains the transcribed text for a completed speech segment.
error
Sent when the server encounters a recoverable or fatal error. The connection may remain open after a recoverable error.
Python SDK
The official Python SDK wraps the WebSocket connection, audio pacing, and event parsing into a clean async interface.Installation
Authentication
The streaming client requires your API key and language code.Stream Audio from a File
Use the async context manager and thestream_audio helper. It handles real-time pacing automatically so frames are sent at the correct cadence for VAD.
Iterate Over Events Manually
For lower-level control — handling each event type differently or interleaving sending and receiving — iterate over the stream directly.Using 8 kHz Audio (Telephony)
SDK Event Types
All events are typed dataclasses with araw field containing the full server JSON.
Error Handling
Supported Languages
Inverse Text Normalization (ITN)
Whenx-format: transcribe is set, ITN runs on every transcript segment immediately after recognition — converting spoken-form numbers, currency, dates, times, and phone numbers into the compact written form a reader expects.
What ITN Normalizes
1 — Cardinal & Ordinal Numbers
2 — Currency & Money
3 — Dates
4 — Times
Indian time-of-day words (सुबह, दोपहर, शाम, रात) automatically map to 24-hour HH:MM output.5 — Phone Numbers & PIN Codes
6 — Mixed & Code-Mixed Utterances
Native Script Digits — itn_native_numerals
By default, ITN outputs Western Arabic digits (0–9). Set itn_native_numerals: true in the connection headers to render digits in the native script of the target language.
What ITN Does Not Change
ITN intentionally preserves idiomatic and ambiguous phrases to avoid incorrect normalization.- दो तीन (meaning a few) stays as text, not
2or3 - कर दो / ले दो (imperative verbs) are kept as words, not treated as cardinal 2