Deepgram SDK v6 Listen V2 ConfigureSuccess validation error, fixed in 6.0.1

TL;DR

For "Deepgram SDK v6 Listen V2 ConfigureSuccess validation error, fixed in 6.0.1": upgrade to deepgram-sdk 6.0.1 or later on v6, or 5.3.3 on v5, which added the missing types. If your Deepgram SDK throws ValidationError about unknown Listen V2 message types like ConfigureSuccess, you are on an SDK version that predates the backend's message types.

Deepgram SDK v6 Listen V2 ConfigureSuccess validation error, fixed in 6.0.1

Steps

1. If your Deepgram SDK throws ValidationError about unknown Listen V2 message types like ConfigureSuccess, you are on an SDK version that predates the backend's message types. Upgrade to deepgram-sdk 6.0.1 or later on v6, or 5.3.3 on v5, which added the missing types. Do not stay on 6.0.0 with Listen V2 / Flux.

When to use

You are seeing this: Do not stay on 6.0.0 with Listen V2 / Flux. Use this skill when you run into "Deepgram SDK v6 Listen V2 ConfigureSuccess validation error, fixed in 6.0.1".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: deepgram-sdk 6.0.1, 5.3.3, 6.0.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Deepgram python SDK issue #668 (closed, maintainer fixed): upgrading to SDK v6 (or running v5 with Listen V2 / Flux) crashed with pydantic ValidationError: 'ListenV2FatalError.description Field required' and 'ConfigureSucces...' types unknown to the SDK. The root cause was the V2 backend sending message types like ConfigureSuccess that the SDK's strict response validation did not recognize. Deepgram maintainer lukeocodes acknowledged the bug and released patches on both channels: 6.0.1 and 5.3.3. A community workaround was to patch the response union types manually until upgrading.

Verified resolution: If your Deepgram SDK throws ValidationError about unknown Listen V2 message types like ConfigureSuccess, you are on an SDK version that predates the backend's message types. Upgrade to deepgram-sdk 6.0.1 or later on v6, or 5.3.3 on v5, which added the missing types. Do not stay on 6.0.0 with Listen V2 / Flux.

Source URL: https://github.com/deepgram/deepgram-python-sdk/issues/668