Claude's First New API Version Since 2023 Breaks Everything: No More temperature, top_p or top_k
Anthropic shipped API version 2026-10-21 on October 21, the first new Claude API version since 2023. Passing temperature, top_p or top_k now returns a 400, and every official SDK shipped a breaking major version. Here is what changed and how to migrate.

Anthropic shipped its first new Claude API version since 2023 on October 21, and the Claude API breaking changes are the kind that page you at night. Version 2026-10-21 removes temperature, top_p and top_k from the Messages API entirely. Send any of them and you get a 400 error back, even if you set them to their defaults. Every official SDK simultaneously shipped a new major version that defaults to the new API version. The old 2023-06-01 version still works and has not been deprecated, so nothing in production breaks today. But the moment you upgrade a client library, old request shapes start failing.
The Claude API breaking changes, one by one
The removal list is short but sharp. According to coverage of the release notes, temperature, top_p and top_k are gone from Messages requests, with no replacement parameter. Anthropic's guidance is blunt: omit them and steer the model with prompts instead. Claude 4.7 and later already refused non-default values anyway, according to the migration guide, so the new version mostly extends that behavior to every model. If your application depends on a low temperature to keep outputs stable, you now have a problem to solve rather than a knob to turn.
Two more 400s arrived with the same version. Putting a document block directly inside an assistant message is rejected, so move documents onto user messages. A non-empty citations array on a text block inside a user message is rejected too, while citations on assistant text stay fine. The update also replaces some deprecated fields in the Admin and Enterprise Analytics APIs, which matters if you pull usage data into dashboards.
New SDK majors and the migration path
Alongside the API version, Anthropic published new major versions of every official SDK and the ant CLI: Python 2.0.0, TypeScript 1.0.0, C# 13.0.0, Go 2.0.0, Java 3.0.0, PHP 1.0.0, Ruby 2.0.0 and ant CLI 2.0.0. All of them send 2026-10-21 by default. That default is the trap: bump the dependency in CI and your requests silently move to the stricter API.
The new releases carry a few extras. The spend-limits API gained a workspace_id filter and a usage_tier scope, and user profiles now expose enforcement_status and enforcement_actions so you can see whether Anthropic has restricted one of your end customers. Notably, the SDKs also changed license from MIT to Apache 2.0, which changes the patent grant language in your dependencies and deserves a look from anyone shipping a product built on these clients. Claude Code, Anthropic's coding agent, shipped a /claude-api api-version command that moves code onto the new version for you.
The migration checklist is straightforward:
- Pin your SDK versions in CI before upgrading anything, and read the diff between your current release and the new major.
- Grep your codebase for temperature, top_p and top_k in Claude API calls, then remove them or stay on 2023-06-01 if a non-default value is load-bearing.
- Run Anthropic's migration guide end to end in staging, including the document-block and citation rules, before touching production.
- If you consume Admin or Enterprise Analytics data, check the replaced fields before your dashboards go red.
Why Anthropic is versioning like this now
The logic is defensible. Newer models already behaved this way, the company says, and the API is catching up to model behavior instead of the other way around. Anthropic also says it plans to publish API versions more frequently from here on, giving developers a window to absorb incompatible changes before new models force them. Versioned breakage beats silent breakage every time, and after years of a single 2023-06-01 version, this is how a maturing platform should behave.
There is a pattern here worth watching. OpenAI recently made a similar trade with its Decisions API, swapping prose for probability and asking developers to adapt their call patterns. Both labs are converging on the same philosophy: fewer knobs, stricter contracts, more versioning. It is painful in the quarter it lands and calmer every quarter after. Claude's footprint in developer tooling keeps growing too, from formal verification applied to open-source libraries to this kind of platform plumbing. Upgrade on your own schedule, but schedule it: Anthropic's next models will eventually make the choice for you.


