Configuring Custom Endpoints
Instructions for using Deepgram’s regional, Dedicated, and self-hosted endpoints with your applications.
Instructions for using Deepgram’s regional, Dedicated, and self-hosted endpoints with your applications.
This guide provides instructions for configuring your applications to use Deepgram’s regional endpoints, Deepgram Dedicated endpoints, or self-hosted endpoints.
Deepgram offers regional endpoints for customers who need data processing within a specific geography. Regional endpoints use the same API keys and SDKs as the default global endpoint — you only need to change the base URL.
EU Endpoint URL: api.eu.deepgram.com
The EU endpoint supports Speech-to-Text, Text-to-Speech, Voice Agent, and Text Intelligence APIs. Replace api.deepgram.com with api.eu.deepgram.com in any SDK or API request to route traffic through the EU.
For full configuration details, SDK examples, WebSocket URLs, known limitations, and information about managed LLM/TTS provider regional routing, see Regional Endpoints.
Deepgram Dedicated allows you to run speech-to-text, text-to-speech, and voice agent workloads with performance, compliance, and regional control, without the complexity of managing infrastructure.
If you have a Deepgram Dedicated (DGD) endpoint, you’ll receive endpoint details similar to:
Endpoint URL: {SHORT_UID}.{REGION_SUBDOMAIN}.api.deepgram.com
api.deepgram.com with your dedicated endpoint URL.All Deepgram API features are available on self-hosted deployments. See our API Documentation for more information.
For self-hosted Deepgram deployments, you’ll use your own custom domain and infrastructure.
Common Endpoint Patterns:
https://your-deepgram-instance.comhttp://your-deepgram-instance.com:8080http://10.0.1.100:8080For more information about self-hosted deployments, see our Self-Hosted Documentation.
api.deepgram.com with your self-hosted endpointAll Deepgram API features are available on self-hosted deployments. See our API Documentation for more information.
For streaming features, update WebSocket connection URLs accordingly:
/v1/listen)wss://api.deepgram.com/v1/listenwss://{YOUR_DEDICATED_ENDPOINT}/v1/listenwss://your-deepgram-instance.com/v1/listenws://your-deepgram-instance.com:8080/v1/listen/v1/speak)wss://api.deepgram.com/v1/speakwss://{YOUR_DEDICATED_ENDPOINT}/v1/speakwss://your-deepgram-instance.com/v1/speakws://your-deepgram-instance.com:8080/v1/speak/v1/agent/converse)wss://api.deepgram.com/v1/agent/conversewss://{YOUR_DEDICATED_ENDPOINT}/v1/agent/conversewss://your-deepgram-instance.com/v1/agent/conversews://your-deepgram-instance.com:8080/v1/agent/converseStandard endpoint:
Dedicated endpoint:
Self-hosted endpoint (HTTPS):
Self-hosted endpoint (HTTP with custom port):