Anthropic API / Anthropic API

Anthropic Python SDK streaming TypeError — Pydantic union discriminator returns raw dict instead of typed model

Fix Anthropic Python SDK streaming error TypeError unexpected event runtime type dict instead of typed model Includes evidence for Anthropic API troubleshooting demand.

Source-backed Last updated May 15, 2026 1 source Needs local verification

Category: Anthropic API
Error signature: TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'>
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 15, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Anthropic API, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'> is a Anthropic API failure pattern reported for developers trying to fix anthropic python sdk streaming error typeerror unexpected event runtime type dict instead of typed model. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub PR #1542 in anthropics/anthropic-sdk-python fixes streaming TypeError when Pydantic union discriminator returns raw dict. accumulate_event raises TypeError at isinstance check because event.delta is a dict instead of TextDelta. Multiple prior PRs (#1167, #1287, #1448, #1467) attempted partial fixes but left nested fields as raw dicts. Category mapped to Anthropic API — this is an SDK bug affecting streaming responses.

Common causes

GitHub PR #1542 in anthropics/anthropic-sdk-python fixes streaming TypeError when Pydantic union discriminator returns raw dict. accumulate_event raises TypeError at isinstance check because event.delta is a dict instead of TextDelta. Multiple prior PRs (#1167, #1287, #1448, #1467) attempted partial fixes but left nested fields as raw dicts. Category mapped to Anthropic API — this is an SDK bug affecting streaming responses.

Quick fixes

Confirm the exact error signature matches TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'>.
Check the Anthropic API account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'> exactly before applying the quick fix.
Compare the failing environment with Anthropic API versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'> mean in Anthropic API?

TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'> indicates the workflow described by "Anthropic Python SDK streaming TypeError — Pydantic union discriminator returns raw dict instead of typed model" failed in a Anthropic API context. Start by confirming the exact signature and the component that emitted it.

What should I check first for TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'>?

Check whether this cause matches your environment: GitHub PR #1542 in anthropics/anthropic-sdk-python fixes streaming TypeError when Pydantic union discriminator returns raw dict. accumulate_event raises TypeError at isinstance check because event.delta is a dict instead of TextDelta. Multiple prior PRs (#1167, #1287, #1448, #1467) attempted partial fixes but left nested fields as raw dicts. Category mapped to Anthropic API — this is an SDK bug affecting streaming responses.

Is the TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'> guidance source-backed?

The "Anthropic Python SDK streaming TypeError — Pydantic union discriminator returns raw dict instead of typed model" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'>?

For "Anthropic Python SDK streaming TypeError — Pydantic union discriminator returns raw dict instead of typed model", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging TypeError: Unexpected event runtime type, after deserialising twice — {'type': 'content_block_delta', 'index': 0, 'delta': {'type': 'text_delta', 'text': '...'}} — <class 'dict'>?

For "Anthropic Python SDK streaming TypeError — Pydantic union discriminator returns raw dict instead of typed model", collect the failing Anthropic API command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.