## TL;DR

For "pydantic_core._pydantic_core.ValidationError: 1 validation error for TranscriptResponse": maintainer ccampbell-aai confirmed the fix landed in PR #162: upgrade to any SDK version above 0.49, with 1.1.0 being the latest at the time. It was fixed in PR #162, so upgrade to any assemblyai version above 0.49.

```text
pydantic_core._pydantic_core.ValidationError: 1 validation error for TranscriptResponse
```

## Steps

1. Reading a completed transcript raised `pydantic_core._pydantic_core.ValidationError: 1 validation error for TranscriptResponse` with `chapters.0.gist` and `Field required [type=missing, ...]`, because the API returned chapter objects without a `gist` key while the SDK model required it. The reporter's own response JSON showed the missing key plainly. Maintainer ccampbell-aai confirmed the fix landed in PR #162: upgrade to any SDK version above 0.49, with 1.1.0 being the latest at the time.

2. This validation error means the API returned chapters without the `gist` field that your SDK version requires. It was fixed in PR #162, so upgrade to any assemblyai version above 0.49. The failure happens when deserializing the transcript response, not during transcription itself, so your audio processing is fine. Pin above 0.49 in your requirements to keep this from coming back.

3. The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.

## When to use

You are seeing this: The reporter's own response JSON showed the missing key plainly. Use this skill when you run into "pydantic ValidationError: chapters.0.gist Field required on TranscriptResponse".

## 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: 1.1.0. If you are on something much newer or older, the details may have shifted.

## Why this happens

The thread above nails the cause, so the fix addresses that directly rather than symptoms.

## Sources

- https://github.com/AssemblyAI/assemblyai-python-sdk/issues/103