We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
there should be alternatives in the result type
enable alternatives and try to consume them.
The result should have typed alternatives
Alternatives are referenced in the API https://developers.deepgram.com/api-reference/ but not in the more detailed documentation
The text was updated successfully, but these errors were encountered:
Hi @wodka, alternatives should exist currently on the individual channel returned in the transcript. Their location on a result would look like:
const response = await deepgram.transcription.preRecorded(fileSource, { punctuate: true, }); const channel0Alternatives= response.results.channels[0].alternatives
Am I misunderstanding?
Sorry, something went wrong.
no you are completely right - I missed this. Thank you!
No branches or pull requests
What is the current behavior?
there should be alternatives in the result type
Steps to reproduce
enable alternatives and try to consume them.
Expected behavior
The result should have typed alternatives
Please tell us about your environment
Other information
Alternatives are referenced in the API https://developers.deepgram.com/api-reference/ but not in the more detailed documentation
The text was updated successfully, but these errors were encountered: