I am currently working on integrating real-time speech-to-text transcription using the Deepgram API.

[chrome sentinel]

While testing with ephemeral tokens, I am consistently receiving 401 Unauthorized and WebSocket closure code 1006.

On reviewing the JWT payloads, I have noticed that the scopes field may not be correctly set to include "listen:stream". Since live transcription requires this permission, I would like your guidance on:
1. How to verify which scopes are enabled for my main API key in the Deepgram Console.
2. Whether additional steps are required to activate or request access to the listen:stream scope.
3. Best practices for generating ephemeral tokens with the correct scope (listen:stream) for WebSocket connections to wss://api.deepgram.com/v1/listen.

Could you please confirm if my current project is provisioned with the correct scopes, and advise on how I can enable listen:stream for successful real-time streaming?

[ashen mountain]

Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently.
-# If you haven't done so, ensure your Discord and Github profiles are linked to Deepgram so you can earn points to redeem on cool stuff just by being active!

It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?

• The deepgram product you are using (e.g Speech to Text, Agent API)
• A request ID that triggered your error or issue.

[native trench]

Deepgram doesn't have any narrow inference scopes like listen:stream; if you're hitting /v1/listen, your token definitely has the right permissions (and you should expect a 403 if it didn't). Most likely the token is malformed, or missing from your /listen request altogether. Do you have some sample code (with no sensitive details, please)?