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. 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
• Voice Agent: /v1/agent/converse
• Text Intelligence: /v1/read

See our API Documentation for more information.

Known Limitations

• Whisper models are not available 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

1
from deepgram import DeepgramClient
2
import httpx
3
4
client = DeepgramClient(
5
    api_key="YOUR_API_KEY",
6
    httpx_client=httpx.Client(
7
        base_url="https://api.eu.deepgram.com"
8
    )
9
)

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.

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
• Voice Agent: /v1/agent/converse
• Text Intelligence: /v1/read

See our API Documentation for more information.

Known Limitations

• Whisper models are not available 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

1
from deepgram import DeepgramClient
2
import httpx
3
4
client = DeepgramClient(
5
    api_key="YOUR_API_KEY",
6
    httpx_client=httpx.Client(
7
        base_url="https://api.au.deepgram.com"
8
    )
9
)

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. 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.

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.

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.

How to Use

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

1
{
2
  "agent": {
3
    "listen": {
4
      "provider": {
5
        "type": "deepgram",
6
        "model": "nova-3"
7
      }
8
    },
9
    "think": {
10
      "provider": {
11
        "type": "open_ai",
12
        "model": "gpt-4o-mini"
13
      }
14
    },
15
    "speak": {
16
      "provider": {
17
        "type": "deepgram",
18
        "model": "aura-2-zeus-en"
19
      }
20
    }
21
  }
22
}

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.