We're excited to announce general support for OpenAPI 3.2.0 across the Swagger open-source ecosystem.
In summary:
- OpenAPI 3.2.0 support added across Swagger UI, Swagger Client, Swagger Editor, and ApiDOM.
- As clients of Swagger Opensource - SmartBear’s commercial tooling also support OpenAPI 3.2.0 in Swagger Studio and Swagger Portal
- Swagger is the first open-source tooling suite to ship support for OpenAPI 3.2.0.
- Check the Swagger open-source project details on swagger-api.
Following our earlier work to support OpenAPI 3.1, we continue delivering comprehensive tools for the latest OpenAPI Specification versions. With OpenAPI 3.2.0 supported across Swagger, teams can leverage new features including streaming API patterns, richer tag hierarchies, additional HTTP methods, and improved data modeling as support expands across the tooling suite.
This release marks a milestone: by using AI-assisted development throughout implementation, we shipped OpenAPI 3.2.0 support faster than any previous version, closing the gap between specification publication and tooling availability.
What is OpenAPI 3.2.0?
OpenAPI 3.2.0 is the latest version of the OpenAPI Specification (OAS). It defines a standard, language-agnostic interface description for HTTP APIs, enabling humans and computers to discover and understand a service's capabilities without source code, additional documentation, or network traffic inspection.
OpenAPI 3.2.0 builds on OpenAPI 3.1 and introduces features targeting real-world API patterns, improved data modeling, and better developer experience. Five key additions stand out.
Streaming and sequential media types - First-class support for text/event-stream (SSE), application/jsonl, multipart/mixed, and other sequential formats using the new itemSchema field on media type entries.
Multipurpose tags with nesting - Tags gain summary, parent, and kind fields for hierarchical grouping and audience-based navigation in documentation tooling.
Support for additional HTTP methods - The new query HTTP method is now part of the specification, alongside additionalOperations for describing any non-standard methods.
The querystring parameter location - A new in: querystring option allows parsing the entire query string as a single field, similar to handling a request body.
$self for document identity - A new top-level $self field lets authors declare the document's base URI, resolving ambiguity in relative reference resolution for multi-file API descriptions.
For a detailed list of changes, see the OpenAPI 3.2.0 release notes.
How we delivered faster than ever before
We are proud of how quickly we delivered this release.
Historically, a lag existed between publishing a new OpenAPI Specification version and when API teams could rely on tooling support. Supporting a new spec version across Swagger's open-source and commercial ecosystem is a large, interconnected effort — changes ripple across Swagger UI, Swagger Editor, Swagger Client, and ApiDOM simultaneously. For OpenAPI 3.1, that gap was significant, and we aimed to improve.
For OpenAPI 3.2.0, we paired our deep knowledge of the OpenAPI Specification with today's modern coding assistants. We provided the intent, context, and guardrails; the tooling helped us execute across the breadth of the ecosystem at a pace that was previously out of reach. This enabled us to:
- Rapidly analyze the specification diff between OpenAPI 3.1 and 3.2.0, systematically identifying every affected area across our tooling suite - a task previously requiring days of manual review.
- Accelerate generation of validation rules for the new OAS 3.2.0 constructs - such as itemSchema for sequential media types, in: querystring parameters, and the query HTTP method - directly from the specification prose.
- Expand test coverage across new and modified behaviors quickly, guided by our understanding of how the spec should behave in practice.
As a result, we shipped OpenAPI 3.2.0 support significantly faster than any previous version. We see this approach — expert-led, tool-accelerated — as our new standard for keeping pace with the OpenAPI community.
What's next
Next, we will close remaining gaps in OpenAPI 3.2.0 support and collaborate with the community to ensure smooth adoption of Swagger's latest capabilities.
We remain committed to shortening the gap between specification publication and tooling readiness. AI integration is now core to our workflow, and we will invest further to keep pace with the OpenAPI community.
We invite your help. Check our contributing guide and join the open-source initiatives across Swagger - every contribution matters.