Support Batch Speaker ID#105
Merged
J-Jaywalker merged 2 commits intomainfrom May 5, 2026
Merged
Conversation
dumitrugutu
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change exposes the speakers object from our JSON response to users using the batch SDK.
https://docs.speechmatics.com/api-ref/batch/get-the-transcript-for-a-transcription-job
At the moment this isn't exposed, which means that in order to get speaker IDs, you'd have to handle the raw websocket plumbing yourself.
This change makes it so that we can access the speakers straight away as a property from the transcription results object.