Breaking change
A breaking change is a request setting or endpoint that fails after you switch model ids or move to a new API version. The new model can still be up, and the old field is what fails.
Last reviewed . Publisher: SunsetDiff. A source line names the day that page was read.
The rows below are copied from this site's model records. A shutdown cell is the date stored for that provider, not a date copied from another host.
How this differs from a shutdown
A shutdown means the old id is no longer served. A breaking change means the call reached a model, or a new API version, and a field or endpoint from the old request was rejected.
SunsetDiff keeps those rules on the breaking changes page: the old setting, the models or the API version, what the source says happens, the fix, and the source URL. An error sentence is quoted only when the linked source prints it.
Sources: SunsetDiff breaking changes , Claude API migration 2026-10-21 , checked October 22, 2026.
Examples the provider pages name
Claude API version 2026-10-21 rejects temperature, top_p, and top_k on every model. claude-sonnet-5-5 also rejects a non-default temperature on its own, which is a model rule, not the API version rule.
OpenAI's Chat Completions reference says max_tokens is deprecated in favor of max_completion_tokens and is not compatible with o-series models. That is a field change, not the shut down of the model id.
Sources: Claude API migration 2026-10-21 , OpenAI Chat Completions , checked October 22, 2026.
Rows from this dataset
The rules are on the breaking changes page, not a status column.