# Confirm Nova-3 Configure Updates

By Steven Van · 2026-10-19

Every Configure message on a Nova-3 /v1/listen stream now gets a ConfigureSuccess or ConfigureFailure reply, with the keyterms in effect.

Deepgram now answers every Configure message sent on a [Deepgram](<https://creatorstoolbox.com/tools/deepgram>) /v1/listen stream with exactly one ConfigureSuccess or ConfigureFailure message. The change, [listed in the docs as "Confirm Nova-3 Configure Updates"](<https://developers.deepgram.com/docs/configure>), lets an application know whether a mid-stream update took effect.

## What the confirmation contains

Both responses include the stream's request\_id. When the update replaces the stream's keyterms, ConfigureSuccess lists the keyterms now in effect. Fields the message did not change are left out of the response.

A ConfigureFailure means Deepgram rejected the whole message and applied none of it, including any features sent alongside keyterms. The stream stays open with its previous settings. Each failure carries a code and a description:

- CONFIGURE\_KEYTERMS\_NOT\_SUPPORTED: the stream's model is not Nova-3, such as Nova-2.

- CONFIGURE\_KEYTERM\_LIMIT\_EXCEEDED: the keyterms exceed the 500-token limit.

- CONFIGURE\_ALREADY\_PENDING: a Configure was sent before the previous one received its response.

- CONFIGURE\_INTERNAL\_ERROR: Deepgram failed to apply the update.

## How Configure works

Configure changes settings on an open stream without reconnecting. It accepts two optional fields. keyterms is an array of strings that replaces the stream's keyterms, works on Nova-3 models only (including multilingual and Nova-3 Medical), and is cleared by an empty array. features is an object that turns formatting features on or off, for example {"numerals": true}. An omitted field keeps its current value.

Each keyterms array replaces the whole list, including any set with the keyterm query parameter when the stream was opened. To add a term, send the existing terms plus the new one. New settings apply to audio Deepgram has not yet transcribed, and transcripts already returned are not revised.

Deepgram processes one Configure at a time, so an application should wait for the response before sending the next. A field the message does not support, such as keyterm instead of keyterms, returns an Error message and the stream stays open with its previous settings.

![Deepgram](<https://www.google.com/s2/favicons?domain=deepgram.com&sz=128>)

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 →](<https://creatorstoolbox.com/tools/deepgram>)

[Original source](<https://developers.deepgram.com/changelog/2026/10/19#confirm-nova-3-configure-updates>)

[Read Confirm Nova-3 Configure Updates on Creators Toolbox](<https://creatorstoolbox.com/blog/deepgram-confirm-nova-3-configure-updates>)

---
Canonical source: https://creatorstoolbox.com/blog/deepgram-confirm-nova-3-configure-updates
