Diarization
Speaker diarization partitions transcribed speech by speaker - answering “who spoke when”. When enabled, each piece of transcribed text is labelled with a speaker_id so you can tell participants apart in a conversation.
Diarization is available on the Prerecorded and Realtime APIs. It is not available on the Turns API.
Enabling Diarization
Section titled “Enabling Diarization”Set the diarize query parameter to true. Optionally cap the number of distinct speakers with max_speakers (1-8); leave it unset to let the server determine the count automatically.
?diarize=true&max_speakers=2Speaker Limit
Section titled “Speaker Limit”Diarization distinguishes up to 8 speakers per session (prerecorded request or realtime connection).
max_speakersaccepts values from1to8. Any other value is rejected with400 Bad Request.max_speakersis an upper bound, not an expected count. If you know a call has two participants,max_speakers=2keeps their speech from being split across extra speaker IDs; fewer IDs may still appear if fewer people speak.- Audio with more than 8 distinct speakers can still be transcribed, but some speakers will share a
speaker_id, so IDs no longer map one-to-one to people.
Speaker IDs
Section titled “Speaker IDs”Each speaker is identified by an integer speaker_id from 0 to 7 (or up to max_speakers - 1 when set). IDs are assigned in the order speakers are first heard and remain stable for the duration of a session.
In the Response
Section titled “In the Response”On prerecorded, the response is split into per-speaker segments, each with its own speaker_id and text. On realtime, each transcript message carries the speaker_id of its dominant speaker. See the API reference for Prerecorded and Realtime for the full response fields.