conversation_context field lets you supply dialogue that preceded the audio provided in the current request. It gives the model continuity across a multi-turn conversation (for example, a human speaking with a voice agent) to boost transcription accuracy, while still transcribing only the current turn.
Include turns from either side of the conversation as separate list items in chronological order (oldest first, most recent last), where a single string is treated as one turn.
- Value: an array of strings (one per turn) or a single string (treated as one turn)
- Maximum: 100 turns / 4096 characters total — context over either cap is trimmed, not rejected
- If the context exceeds a cap or the model’s context window, the oldest turns (those at the start of the list) are dropped first
- Entries carry no speaker labels — include the agent’s replies and the caller’s utterances as separate entries
- Python
- Python SDK
- JavaScript
- cURL
Combining with other features
conversation_context composes with prompting and keyterms in the same config part — describe the call with prompt, list explicit vocabulary with keyterms_prompt, and pass the preceding dialogue with conversation_context.
Looking for streaming context?
For live audio, Real-time STT carries context across turns automatically within a session, and voice agents can interleave their replies with theagent_context parameter. See Context carryover (Real-time).