APIBreak

What OpenAI changed, 16 July 2026 to 27 September 2026

281 operations became 352. None were removed, 10 were newly deprecated, 71 were added, and 0 request fields became required.

OpenAI's openapi.json first appears on the main branch of openai/openai-openapi on 16 July 2026, so the comparison starts there rather than six months back.

Read from openai/openai-openapi at db3e531 and bafb6ad (version 2.3.0). Generated 27 September 2026 by the specification parser the APIBreak Action uses, applied to OpenAI's published specification.

OpenAI does not pin accounts to a dated API version. Operations are marked deprecated in the published specification; this page reads that flag and does not know shutdown dates.

Removed from the specification

Nothing was removed in this window. That is a real result, not a gap in the check.

Newly deprecated in this window

A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss.

Deprecated as of the current specification (15)

Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.

Entries without a link were already marked deprecated at db3e531 · 16 July 2026, the baseline compared here.

The Action does not check OpenAI yet

It checks GitHub REST and Stripe. If you want your CI to check the OpenAI endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.

a real report

Other vendors we track

See every vendor