Configuring Custom Endpoints
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.
Regional 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 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
How to Configure
- Replace the base URL: In any SDK or API request, replace
api.deepgram.comwith your dedicated endpoint URL. - Use your existing credentials: You can use your existing API keys and tokens.
Feature Compatibility
All Deepgram API features are available on self-hosted deployments. See our API Documentation for more information.
Self-Hosted Endpoints
For self-hosted Deepgram deployments, you’ll use your own custom domain and infrastructure.
Common Endpoint Patterns:
- HTTPS:
https://your-deepgram-instance.com - HTTP with alternate port 8080:
http://your-deepgram-instance.com:8080 - Internal network:
http://10.0.1.100:8080
How to configure
For more information about self-hosted deployments, see our Self-Hosted Documentation.
- Replace the base URL: In any SDK or API request, replace
api.deepgram.comwith your self-hosted endpoint - Use your distribution credentials: Self-hosted deployments require specific credentials provided during setup.
- Configure protocol and port: Specify HTTP/HTTPS and custom ports as needed for your deployment.
Feature Compatibility
All Deepgram API features are available on self-hosted deployments. See our API Documentation for more information.
WebSocket Connections
For streaming features, update WebSocket connection URLs accordingly:
Speech-to-Text (/v1/listen)
- Standard:
wss://api.deepgram.com/v1/listen - Dedicated:
wss://{YOUR_DEDICATED_ENDPOINT}/v1/listen - Self-hosted (HTTPS):
wss://your-deepgram-instance.com/v1/listen - Self-hosted (HTTP with custom port):
ws://your-deepgram-instance.com:8080/v1/listen
Text-to-Speech (/v1/speak)
- Standard:
wss://api.deepgram.com/v1/speak - Dedicated:
wss://{YOUR_DEDICATED_ENDPOINT}/v1/speak - Self-hosted (HTTPS):
wss://your-deepgram-instance.com/v1/speak - Self-hosted (HTTP with custom port):
ws://your-deepgram-instance.com:8080/v1/speak
Voice Agent (/v1/agent/converse)
- Standard:
wss://api.deepgram.com/v1/agent/converse - Dedicated:
wss://{YOUR_DEDICATED_ENDPOINT}/v1/agent/converse - Self-hosted (HTTPS):
wss://your-deepgram-instance.com/v1/agent/converse - Self-hosted (HTTP with custom port):
ws://your-deepgram-instance.com:8080/v1/agent/converse
SDK Configuration Examples
Python SDK
JavaScript SDK
.NET SDK
Go SDK
Java SDK
Direct API Calls
cURL Examples
Standard endpoint:
Dedicated endpoint:
Self-hosted endpoint (HTTPS):
Self-hosted endpoint (HTTP with custom port):