# Update Nova-3 Keyterms Mid-Stream on Every Regional Endpoint By Steven Van · 2026-10-19 Nova-3 Configure messages on /v1/listen now work on the EU, Australia and India endpoints, and behave the same as on the global endpoint. Mid-stream keyterm updates for [Deepgram]() Nova-3 now work on every regional endpoint. Sending a Configure message on /v1/listen to change keyterms is supported on the EU (api.eu.deepgram.com), Australia (api.au.deepgram.com) and India (api.in.deepgram.com) endpoints, as well as the global endpoint (api.deepgram.com). Deepgram says the feature behaves the same on all of them, as [announced in its docs](). ## Switching endpoints Regional endpoints use the same API keys and SDKs as the global endpoint, so the only change is the base URL. For streaming, the Speech-to-Text WebSocket URL follows the pattern wss://api.eu.deepgram.com/v1/listen, with au or in in place of eu for the other regions. Requests to a regional endpoint are never routed outside that region. If the region is unavailable, requests fail rather than fall back. ## Confirmation of updates The same day's release note adds a response to every Configure message on a /v1/listen stream: exactly one ConfigureSuccess or ConfigureFailure. When an update replaces the stream's keyterms, ConfigureSuccess lists the keyterms now in effect, so a client can tell when the change took effect. ![Deepgram]() Deepgram Power enterprise voice solutions with Deepgram’s Speech-to-Text, Text-to-Speech, and Voice Agent APIs. Real-time, accurate, and built for scale. [View Deepgram →]() Sources [Original source]() [Read Update Nova-3 Keyterms Mid-Stream on Every Regional Endpoint on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/deepgram-update-nova-3-keyterms-mid-stream-on-every-regional-endpoint