#Problems to use Speech to Text - 401 Error
1 messages · Page 1 of 1 (latest)
Hey there! This channel allows you to ask Kapa.ai for assistance. But it looks like you haven't connected your Discord profile to your Deepgram account yet. You can do so at https://community.deepgram.com - by doing so, you'll be able to ask questions in #1115960287183511643 if you need human assistance!
Deepgram’s community offers tons of resources to support you on your voice AI journey
Hi @loud bay. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Based on the error message you're receiving, it appears you're encountering an authentication issue when trying to use Deepgram's Speech-to-Text service. This 401 Unauthorized error indicates that the API key you're using is not valid or not properly authorized. Here are some steps you can take to resolve this issue:
-
Check your API key: Ensure that you're using the correct API key for your Deepgram project. You can view and manage your API keys in the Deepgram Console (https://console.deepgram.com) Authenticating (https://developers.deepgram.com/docs/authenticating).
-
Verify API key format: Make sure you're including the API key in the correct format in your request. The API key should be sent in the
Authorizationheader like this:Authorization: Token YOUR_DEEPGRAM_API_KEYAuthenticating (https://developers.deepgram.com/docs/authenticating)
-
Test your API key: You can quickly test if your key is valid by making a request to the
/auth/tokenendpoint:curl <https://api.deepgram.com/v1/auth/token> \ -H "Authorization: Token YOUR_DEEPGRAM_API_KEY"This will return details about your key if it's valid Authenticating (https://developers.deepgram.com/docs/authenticating).
-
Check permissions: Ensure that your API key has the necessary permissions for the action you're trying to perform. If you're getting a 401 error, it could also mean insufficient permissions API Errors (https://developers.deepgram.com/reference/errors).
-
Verify HTTPS: Make sure you're sending requests over HTTPS. Calls made over plain HTTP will fail Authenticating (https://developers.deepgram.com/docs/authenticating).
-
Create a new API key: If you're still having issues, try creating a new API key in the Deepgram Console and use that for your requests.
- Check for expiration: If you've set an expiration date on your API key, make sure it hasn't expired.
If you've tried these steps and are still encountering issues, you may want to contact Deepgram support with your request_id (fd7ba615-684f-4d21-af2d-0b70061d0ffa) for further assistance.
Remember, it's crucial to keep your API keys secure and not share them in publicly accessible areas Authenticating (https://developers.deepgram.com/docs/authenticating).
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@loud bay Kapa.ai is still learning and improving, please let me know how I did by reacting below.
I too started getting this error @loud bay
I wish I could tell you!
Lets wait then because this web is awesome
Lets try to find out a solution bet we 2
I think we need to verify the API
You should create an API and then verify it
But i dont know how
I'm also hitting this now too, even on something like the management API (https://api.deepgram.com/v1/projects) with a fresh API token.
On the Deepgram website, the demo app is having websocket connection issues, too.
@clever wing I guess you have this problem too 😂
Hey there, it looks like you've been talking with Kapa for a bit. If you need additional help, you should consider moving to #1115960287183511643 where our team can answer your query.
I had "we didn't catch that. please try again" problem but it just fixed
strange
Is it fixed for everyone now?
Mine worked 👍