Support
Start here
Instant answers
Ask AI lives right here in the docs. It answers from the pages you’re reading and links back to its sources, so you can check its work.
Prefer Slack? The Deepgram bot searches our docs and answers right in the thread, with code and links. Add it above, then mention @Deepgram in any channel.
Ask the community
Some of the best debugging help comes from someone who hit the same wall last month.
- Discord: builders and Deepgram engineers, in real time. Good for a quick gut check or a second pair of eyes.
- GitHub Discussions: for questions worth keeping. Threads are searchable, so your answer helps whoever hits this next.
One thing to know: nobody in the community can see your account. Keep billing questions and anything touching your project data to email, where we can pull up your account and help. Both spaces follow our Code of Conduct.
Check service status
When something breaks, check status.deepgram.com first. It’s the quickest way to rule out an issue on our end before you go digging through your own. You can subscribe there for incident and maintenance alerts.
During an incident we post updates on the status page as we work, so there’s no need to open a ticket to tell us something’s down. If your problem outlasts the incident, email us. We want to know.
Email us
We’re always happy to help. Send it to whichever address fits:
- A technical or API problem: support@deepgram.com, from the address on your Deepgram account so we can find your project.
- Account or billing: success@deepgram.com, or check the help center for the common ones.
When to expect a reply
- Blocked right now? Say so in your first line and we’ll get to you sooner.
- We answer on business days. Weekend and holiday mail is waiting for us the next morning we’re in.
- Mid-incident? status.deepgram.com updates fastest.
- Want a faster turnaround? Support plans add it. Ask us at success@deepgram.com.
What to send
The tickets we turn around fastest are the ones we can reproduce. You don’t need every item below, but each one you include saves us a round trip:
- A request ID. Every API response carries a
dg-request-idresponse header. This is the single most useful thing you can send. For a failed WebSocket connection, grab thedg-errorheader too. The speech-to-text and text-to-speech troubleshooting guides show where to find them. - Your project ID, from the Console.
- The endpoint and model you called, for example,
/v1/listenwithnova-3. - Your SDK and version, or a note that you called the API directly.
- When it happened, in UTC.
- What you expected, and what you got: the exact error message or status code.
- A minimal repro if you have one: a request, a snippet, or a short audio sample.
Support plans
Support plans are available on enterprise agreements. Your Deepgram rep can walk you through the options, or email success@deepgram.com if you don’t have a rep yet.
