The State of OpenAPI Specification: what's new in 3.1
summary
OpenAPI 3.1 arrives imminently (RC1 available, general release estimated January) and makes three concrete changes: full compatibility with JSON Schema 2020-12 (null as a type and type arrays, examples alignment), true first‑class web hooks as top-level element while keeping callbacks, and reusable path items in components so an API can be a components‑only document. Also: license identifier via SPDX, mutual TLS scheme, relaxed request body rules for GET/HEAD, responses optional for earlier validation, and Redoc already supports x-webhooks.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:41Summary
- 7:07Data types
- 9:52JSON Schema examples
- 17:20RedArc
- 18:09Required paths and components
- 19:51Callbacks vs web hooks
- 22:06Reusable components
- 22:45Proposal process
- 26:20Small and wonderful improvements
- 26:55Summary description as siblings
- 27:41Summary in info
- 29:15License identifier
- 30:41Mutual TLS
- 31:14Request bodies
- 32:14Optional responses
- 33:25The OpenAPI is about the community
- 34:33OpenAPI Documentation
- 35:41Involvement
- 38:56OpenAPI Tools
- 40:14Recap
- 43:24Resources
- 45:15QA
related talks
28mWhat’s new in OpenAPI 3.2
21mLet there be docs!
35mDocumenting APIs: new era, same craft
19mSecure and accelerate APIs' lifecycle with the OpenAPI specification
53mAPI Standards 2.0
22mSpecification-Driven Development of REST APIs
39mAPI Development in 2017
21mDesigning APIs with OpenAPI: Build the Right APIs the Right Way.