dg-token key doesn't match API_KEY provided in callback POST call to /listen | Deepgram | Page 1

opal vectorBOT Nov 10, 2023, 2:54 PM

#

Thanks for asking your question. Please be sure to reply with as much detail as possible so we can assist you efficiently. Such as:

Provide the request_id if you've a question about a transcription response.
The options you used or the api.deepgram.com URL you sent your request to, including parameters.
Any code snippets you can include.
Any audio you can include, or if you can't share it here please email it to us at [email protected] and provide a link to this thread.

raven wigeon Nov 10, 2023, 2:54 PM

#

The request_id was b1af97d6-7954-4fd2-9976-a37fbf5632b8 for example

#

This was the full POST call to the API https://api.deepgram.com/v1/listen?smart_format=true&model=nova&language=en-US&diarize=true&punctuate=true&callback=https://e1df-2003-d7-f47-7122-4484-27a9-b787-2ce5.ngrok-free.app/api/webhooks/deepgram

#

This is how I check the token in my nextjs serverless function.

The format of the API KEY is in the format \b[a-f0-9]{40}\b, however the answer I get in dg-token has the format of a typical UUID

zinc socket Nov 11, 2023, 9:02 AM

#

Hey @raven wigeon

Looks like there is misunderstanding about what Deepgram sends to you. Each API Key has unique UUID indentifier. So you need to copy it from API Keys management page.

And exactly this UUID will be in DG-Token header. Basically you need to compare 2 UUIDs: from request and one from you DEEPGRAM_API_KEY_IDENTIFIER variable for example

#dg-token key doesn't match API_KEY provided in callback POST call to /listen