Skip to main content
Transcription modes let your app choose between a clean transcript and a word-for-word transcript that preserves fillers, repetitions, interrupted words, self-repairs, false starts, and vocal sounds such as laughter.
Automatic transcription currently defaults to intended. Beginning September 1, 2026, the default will change to verbatim. Set transcription_mode=intended explicitly to preserve clean-transcript behavior after that date.

Choose one transcript style

When automatic transcription is used, transcription_mode controls the style of transcript returned by the API. Only these two values are supported. transcription_mode applies only when the API performs automatic transcription. Supplying reference_text or reference_phones continues to define the pronunciation target and does not allow generated text to replace that target.

Intended response

Through August 31, 2026, omitting transcription_mode has the same effect as sending transcription_mode=intended. Send the value explicitly if your integration always requires a clean transcript.

Verbatim response

All start and end values are milliseconds from the beginning of the uploaded audio. A timestamp can be null when the recognizer cannot obtain a reliable boundary. events is always an array and is empty when no supported events are detected.

Transcription fields

The events array is derived from the verbatim transcript and its timings. It does not expose model-specific token IDs or internal labels.

Words and pronunciation scoring

Each transcription.words[] entry contains its detected phones in surface_phones. When a transcript word corresponds to a scored target, word_group_index points to its entry in word_groups. A value of null means the token is not scored. This includes extra words, fillers, abandoned repetitions, cut-offs, and vocal events. events[].word_indices points to the related entries in transcription.words.

Event types

The v1 event schema is a discriminated union selected by type.

filler

A filled pause normalized to one of the supported labels. Words such as “like,” “well,” “I mean,” and “you know” are ordinary transcript words. They are not classified as filler events.

repetition

An adjacent repetition of the same word, such as I I or we we we. Non-adjacent repetitions and repeated phrases are preserved in the transcript but are not guaranteed to produce a repetition event.

cutoff

An interrupted word or audible word fragment. The verbatim transcript uses a trailing *, for example th* Thursday. Short word fragments are acoustically ambiguous. The model may detect that an interruption occurred while producing an imperfect fragment spelling.

vocal_event

A supported non-lexical vocal or acoustic event. Supported labels are:
  • breath
  • cough
  • laughter
  • lipsmack
  • noise
  • sigh
  • sniff
  • throatclearing
  • yawn
  • other
other preserves a detected bracketed event that cannot be mapped safely to one of the named labels.

What is not a structured event

The verbatim transcript can preserve more speech detail than the v1 event schema classifies.
  • Self-repairs and false starts can appear in text, but the API does not currently return a structured relationship between abandoned words and the speaker’s correction.
  • Stuttering is not returned as a single event type. Whole-word repetitions may appear as repetition, and interrupted attempts may appear as cutoff. Blocks, prolongations, and physical secondary behaviors are not classified.
  • Silent pauses are represented by gaps between word timestamps and by the top-level pauses and pause_metrics fields. They are not transcription events.