Anthropic has released Claude API version 2026-10-21, the first new numbered version of its developer API since 2023-06-01, and the headline change is a removal: the Messages API no longer accepts the temperature, top_p or top_k sampling parameters. The announcement came from ClaudeDevs, Anthropic’s official developer account, on October 21.
The old version is not being retired. Anthropic says 2023-06-01 remains supported and undeprecated, and that it will ship API versions more frequently from now on, so developers can absorb incompatible changes gradually instead of facing them all at once when a new model requires them. New major versions of the Anthropic SDKs and the ant command-line tool were released at the same time, defaulting to 2026-10-21 and shipping with migration guides.
What The 2026-10-21 Version Changes
Three request-shape changes define the release. First, temperature, top_p and top_k are gone from the Messages API under the new version: integrations that pass them must drop the fields rather than retune them. The three parameters were the classic controls for output randomness — temperature scaling how adventurous the model’s token choices are, top_p restricting choices to a probability nucleus, and top_k limiting them to the k most likely tokens. Anthropic’s newer models had already been narrowing their use; on recent flagship models, non-default sampling values returned errors, and the migration advice was already to control behaviour through instructions, examples and format rules instead.
Second, two content placements now return a 400 error: documents passed in an assistant turn, and citations passed in a user turn. Third, several deprecated fields in the Admin and Enterprise Analytics APIs have been replaced with modernised equivalents. None of the changes affect the 2023-06-01 version, which keeps accepting the old shapes.
Why Anthropic Is Versioning Again
For three years the Claude API effectively had one version, which meant every breaking change had to be squeezed into model launches or avoided entirely. Anthropic’s stated plan is to decouple the two: frequent, smaller API versions let developers migrate on their own schedule, before a model release forces the issue. The SDK and CLI releases defaulting to the new version, plus the migration guides and the /claude-api update skill in Claude Code, are the tooling side of that bargain.
The sampling removal has a second logic. As models take on more of their own decoding discipline — reasoning effort, structured outputs, tool use — provider-side sampling knobs increasingly conflict with consistent, testable behaviour, especially for the agent workloads that now dominate API traffic. Removing them makes outputs more predictable across integrations, at the cost of a familiar tuning lever.
What Developers Need To Do
Nothing breaks today: applications pinned to 2023-06-01 keep working unchanged. The work arrives when a team upgrades its SDK or chooses the new version. At that point, code that sets temperature, top_p or top_k will fail validation and must be refactored to steer behaviour through prompts — stricter instructions, worked examples, explicit format rules and acceptance criteria — the same substitution Anthropic’s recent model migration guides already recommend. Pipelines that assemble assistant-turn documents or user-turn citations need restructuring, and admin dashboards reading the replaced analytics fields need updating to the new field names.
Why It Matters
The Claude API version matters because it signals how Anthropic now expects its platform to be programmed. Sampling parameters were the oldest control surface in LLM APIs — inherited from research code and beloved of tinkerers — and their removal marks the point where the provider, not the caller, owns output character, with behaviour steered by instructions instead. For the growing ecosystem built on Claude — from Claude Code to the agent products Anthropic shipped this week, Claude Duet and Claude Security’s continuous scanning — a versioned API with a stated faster cadence is also a stability promise: breaking changes will arrive in small, announced steps, and the three-year freeze that made 2023-06-01 a fossil is not coming back.
Background
Anthropic launched the Claude API in 2023 with version 2023-06-01 and then left the version untouched for more than three years, even as the model line went through Claude 3, 4 and 5 generations and the platform added tools, files, citations, computer use and managed agents. Sampling controls were already being squeezed in that period: successive flagship models restricted or rejected non-default temperature and nucleus values, pushing developers toward prompt-based control well before the parameters disappeared from the API contract itself.
Source: PANews, The Claude Code Daily
0 Comments