Regional Endpoints

Deepgram offers regional endpoints so you can process audio, text, and voice agent traffic 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

For customers requiring data processing within the EU, Deepgram provides an EU-specific endpoint at api.eu.deepgram.com. While Deepgram guarantees the service will be hosted within the EU, the specific country location may change over time. Requests to the EU endpoint are never routed outside the EU: if the region is unavailable, requests fail rather than fall back to another region. If you require hosting in a specific EU country, consider Deepgram Dedicated (see also our technical documentation).

Endpoint URL: api.eu.deepgram.com

How to Configure

1. Replace the base URL: In any SDK or API request, replace api.deepgram.com with api.eu.deepgram.com.
2. Use your existing credentials: Your existing API keys and tokens work on the EU endpoint.

Feature Compatibility

The EU endpoint supports the following Deepgram APIs:

• Speech-to-Text: /v1/listen and /v2/listen (excluding Whisper models)
• Text-to-Speech: /v1/speak and /v2/speak
• Voice Agent: /v1/agent/converse
• Text Intelligence: /v1/read

See our API Documentation for more information.

Known Limitations

• Whisper models are not supported in the EU region. Use Flux or Nova STT models instead.

WebSocket Connections

For streaming features on the EU endpoint, use the following URLs:

SDK Configuration Examples

from deepgram import DeepgramClient
from deepgram.environment import DeepgramClientEnvironment
eu_env = DeepgramClientEnvironment(
    base="https://api.eu.deepgram.com",        # REST APIs
    production="wss://api.eu.deepgram.com",     # STT/TTS WebSocket
    agent="wss://api.eu.deepgram.com",          # Agent WebSocket
    agent_rest="https://api.eu.deepgram.com",   # Agent REST
)
client = DeepgramClient(api_key="YOUR_API_KEY", environment=eu_env)

AU Endpoint

For customers requiring data processing within Australia, Deepgram provides an AU-specific endpoint at api.au.deepgram.com. Deepgram guarantees the service will be hosted within Australia. Requests to the AU endpoint are never routed outside Australia: if the region is unavailable, requests fail rather than fall back to another region.

Endpoint URL: api.au.deepgram.com

How to Configure

1. Replace the base URL: In any SDK or API request, replace api.deepgram.com with api.au.deepgram.com.
2. Use your existing credentials: Your existing API keys and tokens work on the AU endpoint.

Feature Compatibility

The AU endpoint supports the following Deepgram APIs:

• Speech-to-Text: /v1/listen and /v2/listen (excluding Whisper models)
• Text-to-Speech: /v1/speak and /v2/speak
• Voice Agent: /v1/agent/converse
• Text Intelligence: /v1/read

See our API Documentation for more information.

Known Limitations

• Whisper models are not supported in the AU region. Use Flux or Nova STT models instead.

WebSocket Connections

For streaming features on the AU endpoint, use the following URLs:

SDK Configuration Examples

from deepgram import DeepgramClient
from deepgram.environment import DeepgramClientEnvironment
au_env = DeepgramClientEnvironment(
    base="https://api.au.deepgram.com",        # REST APIs
    production="wss://api.au.deepgram.com",     # STT/TTS WebSocket
    agent="wss://api.au.deepgram.com",          # Agent WebSocket
    agent_rest="https://api.au.deepgram.com",   # Agent REST
)
client = DeepgramClient(api_key="YOUR_API_KEY", environment=au_env)

India Endpoint

For customers requiring data processing within India, Deepgram provides an India-specific endpoint at api.in.deepgram.com. Deepgram guarantees the service will be hosted within India. Requests to the India endpoint are never routed outside India: if the region is unavailable, requests fail rather than fall back to another region.

Endpoint URL: api.in.deepgram.com

How to Configure

1. Replace the base URL: In any SDK or API request, replace api.deepgram.com with api.in.deepgram.com.
2. Use your existing credentials: Your existing API keys and tokens work on the India endpoint.

Feature Compatibility

The India endpoint supports the following Deepgram APIs:

• Speech-to-Text: /v1/listen and /v2/listen (excluding Whisper models)
• Text-to-Speech: /v1/speak and /v2/speak
• Voice Agent: /v1/agent/converse
• Text Intelligence: /v1/read

See our API Documentation for more information.

Known Limitations

• Whisper models are not supported in the India region. Use Flux or Nova STT models instead.

WebSocket Connections

For streaming features on the India endpoint, use the following URLs:

SDK Configuration Examples

from deepgram import DeepgramClient
from deepgram.environment import DeepgramClientEnvironment
in_env = DeepgramClientEnvironment(
    base="https://api.in.deepgram.com",        # REST APIs
    production="wss://api.in.deepgram.com",     # STT/TTS WebSocket
    agent="wss://api.in.deepgram.com",          # Agent WebSocket
    agent_rest="https://api.in.deepgram.com",   # Agent REST
)
client = DeepgramClient(api_key="YOUR_API_KEY", environment=in_env)

Voice Agent Managed LLM and TTS Providers

When you use Deepgram’s managed LLM or managed TTS providers with the Voice Agent API, Deepgram routes requests to those providers on your behalf. Where possible, Deepgram leverages regional endpoints for these managed providers to keep traffic within the same region as your Deepgram endpoint.

EU Regional Support

Today, Deepgram routes managed provider traffic through EU endpoints for OpenAI and Google. When you connect to api.eu.deepgram.com and use a managed OpenAI LLM or TTS model, the underlying requests to OpenAI are routed through OpenAI’s EU infrastructure. Managed Google LLMs default to the EU Gemini Enterprise Agent (GEA) endpoint — see Google LLM APIs below.

Other managed providers do not yet offer EU-specific endpoints. As providers expand their regional availability, Deepgram will adopt those endpoints automatically — no configuration change required on your side.

Google LLM APIs

Deepgram’s managed Google LLMs run on either of Google’s APIs:

• AI Studio (generativelanguage.googleapis.com) — a single global endpoint with the broadest model coverage.
• Gemini Enterprise Agent (GEA) — formerly the Vertex API. Offers regional endpoints, so requests to Gemini models stay in the region you select.

Select the API with the think.provider.version parameter in your Settings message, whichever Deepgram Voice Agent endpoint you connect to:

{
  "agent": {
    "think": {
      "provider": {
        "type": "google",
        "version": "gemini-enterprise-agent-v1",
        "model": "gemini-2.5-flash"
      }
    }
  }
}

When you omit version, the default depends on the Deepgram endpoint:

Fewer Gemini models are available on the EU GEA endpoint than on global AI Studio. For current model availability by region, see Google’s documentation.

AU Regional Support

When you connect to api.au.deepgram.com and use Deepgram managed models for speech-to-text (listen) and text-to-speech (speak) — for example, nova-3 and aura-2 — Deepgram processes that audio within Australia.

The voice agent LLM (think) runs on a third-party provider, where data residency and processing location are distinct. OpenAI, for example, offers Australian data residency — your content is stored at rest in Australia — but performs inference outside Australia. No managed in-region LLM is available today, so the think step is processed outside Australia even when residency applies. See OpenAI’s data residency guide for provider specifics.

India Regional Support

When you connect to api.in.deepgram.com and use Deepgram managed models for speech-to-text (listen) and text-to-speech (speak) — for example, nova-3 and aura-2 — Deepgram processes that audio within India.

The voice agent LLM (think) runs on a third-party provider, where data residency and processing location are distinct. OpenAI, for example, offers India data residency — your content is stored at rest in India — but performs inference outside India. No managed in-region LLM is available today, so the think step is processed outside India even when residency applies. See OpenAI’s data residency guide for provider specifics.

How to Use

No additional configuration is needed. Connect to your regional endpoint and select a managed provider as you normally would:

{
  "agent": {
    "listen": {
      "provider": {
        "type": "deepgram",
        "model": "nova-3"
      }
    },
    "think": {
      "provider": {
        "type": "open_ai",
        "model": "gpt-4o-mini"
      }
    },
    "speak": {
      "provider": {
        "type": "deepgram",
        "model": "aura-2-zeus-en"
      }
    }
  }
}

When this configuration is sent to wss://api.eu.deepgram.com/v1/agent/converse, Deepgram processes speech-to-text and text-to-speech within the EU, and routes the managed OpenAI LLM call through OpenAI’s EU endpoint. When sent to wss://api.au.deepgram.com/v1/agent/converse, Deepgram processes speech-to-text and text-to-speech within Australia; as noted above, the managed LLM (think) call is processed outside Australia. When sent to wss://api.in.deepgram.com/v1/agent/converse, Deepgram processes speech-to-text and text-to-speech within India; the managed LLM (think) call is likewise processed outside India.