For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Ask AIPlaygroundLoginFree API Key
HomeAPI ReferenceVoice AgentSpeech-to-TextText-to-SpeechIntelligenceSelf-Hosted Deployments
HomeAPI ReferenceVoice AgentSpeech-to-TextText-to-SpeechIntelligenceSelf-Hosted Deployments
  • Audio Intelligence
    • Getting Started
    • Feature Overview
    • Entity Detection
    • Intent Recognition
    • Sentiment Analysis
    • Summarization
    • Topic Detection
  • Text Intelligence
    • Getting Started
    • Feature Overview
    • Template Apps
    • Intent Recognition
    • Sentiment Analysis
    • Summarization
    • Topic Detection
  • Results Processing
    • Intelligence Tagging
    • Intelligence Callback
LogoLogo
Ask AIPlaygroundLoginFree API Key
On this page
  • Enable Feature
  • URL Structure
  • Authenticating Callback Requests
  • Using Basic Auth
  • Using the dg-token Request Header
  • Results
  • Text
  • Using CallBack_Method
Results Processing

Text Intelligence Callback

Text Intelligence Callback allows you to have your submitted text processed asynchronously.
Was this page helpful?
Previous
Built with

callback string

Text Intelligence

Deepgram’s Callback feature allows you to supply a callback URL to which text can be returned. When passed, Deepgram will immediately respond with a request_id before processing your text asynchronously.

Enable Feature

To enable Callback, when you call Deepgram’s API, add a callback parameter in the query string and set it to the URL to which you would like transcriptions sent:

callback=URL

cURL
$curl \
> --request POST \
> --header 'Authorization: Token YOUR_DEEPGRAM_API_KEY' \
> --header 'Content-Type: text/plain' \
> --data 'Your Text.' \
> --url 'https://api.deepgram.com/v1/read?callback=URL'

URL Structure

An example URL is https://example.com/callback.

Your callback URLs may reference the following protocols:

  • http or https

Authenticating Callback Requests

Authentication ensures the security and integrity of callback requests. There are two main methods for authenticating callback requests: using Basic Auth and utilizing the dg-token request header.

Using Basic Auth

You may embed username-password authentication credentials in the callback URL in the format https://username:[email protected]. However, it’s important to note that only ports 80, 443, 8080, and 8443 are permitted for callbacks.

Only ports 80, 443, 8080, and 8443 are permitted for callbacks.

Using the dg-token Request Header

Alternatively, the callback request itself contains a header named dg-token. This header is automatically set to the API Key Identifier associated with the API Key used to submit the original request. This method provides a secure and straightforward means of authentication.

Results

Depending on the type of submitted text, the response will vary.

Text

When Deepgram has finished analyzing the text, it will send a POST request to the provided callback URL with an appropriate HTTP status code.

If the HTTP status code of the response to the callback POST request is unsuccessful (not 200-299), Deepgram will retry the callback up to 10 times with a 30 second delay between attempts.

Using CallBack_Method

To enable the Callback Method, include the callback_method parameter in the query string. By default, the method supports POST, but you can specify PUT instead.

cURL
$curl \
> --request POST \
> --header 'Authorization: Token YOUR_DEEPGRAM_API_KEY' \
> --header 'Content-Type: text/plain' \
> --data 'Your Text.' \
> --url 'https://api.deepgram.com/v1/read?callback=URL&callback_method=put'