OpenAPI 3.2: the headline changes, supported today

OpenAPI 3.2 continues the 3.1 line — same JSON Schema 2020-12 foundation — and adds long-requested expressiveness. The changes you will actually meet in documents:

What 3.2 adds

Alongside these come further refinements to tags and media type handling — see the official specification for the complete list.

Editing 3.2 in the browser

Most online editors still reject openapi: 3.2.0 outright. OASForge recognizes it: the validator accepts $self, query operations and additionalOperations where they belong, flags them as errors in 3.0/3.1 documents (with a one-click version bump), and treats unknown future minor versions permissively with an informational note instead of a wall of false errors. Paste a 3.2 document into the editor and see.

No signup, no install — the editor runs entirely in your browser.

Start in the editor