> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.deepgram.com/changelog/2026/9/15/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.deepgram.com/_mcp/server.

# September 15, 2026

> The Deepgram India endpoint (api.in.deepgram.com) is now generally available for Speech-to-Text, Text-to-Speech, Voice Agent, and Text Intelligence APIs.

## India Endpoint Now Generally Available

The Deepgram India endpoint (`api.in.deepgram.com`) is now generally available for customers requiring data processing within India.

### Supported APIs

The India endpoint supports the following Deepgram APIs:

* **Speech-to-Text**: `/v1/listen` and `/v2/listen`
* **Text-to-Speech**: `/v1/speak` and `/v2/speak`
* **Voice Agent**: `/v1/agent/converse`
* **Text Intelligence**: `/v1/read`

### Configuration

To use the India endpoint, replace `api.deepgram.com` with `api.in.deepgram.com` in your SDK or API requests. Your existing API keys and tokens work with the India endpoint.

For WebSocket connections, use the corresponding India URLs:

* **Speech-to-Text**: `wss://api.in.deepgram.com/v1/listen`
* **Speech-to-Text (Flux)**: `wss://api.in.deepgram.com/v2/listen`
* **Text-to-Speech**: `wss://api.in.deepgram.com/v1/speak`
* **Text-to-Speech (Flux)**: `wss://api.in.deepgram.com/v2/speak`
* **Voice Agent**: `wss://api.in.deepgram.com/v1/agent/converse`

For detailed configuration instructions and SDK examples, see our [Regional Endpoints](/reference/regional-endpoints) documentation. For what Deepgram guarantees about where your data is processed and stored, see [Your Data at Deepgram](/trust-security/your-data).

> The Deepgram India endpoint (api.in.deepgram.com) is now generally available for Speech-to-Text, Text-to-Speech, Voice Agent, and Text Intelligence APIs.