Bump.sh Now Renders Every OpenAPI 3.2 Feature, Including Streaming
Bump.sh's Oct. 12 update adds nested tag navigation, badges, streamed-item schemas and custom HTTP methods, finishing OpenAPI 3.2 support begun in December.

Bump.sh now renders every feature of OpenAPI 3.2 in its documentation, the company said in an Oct. 12 product update. It had supported only part of the spec since December. Teams need no extra setup: Bump.sh said to deploy 3.2 documents as usual.
Tag hierarchies build nested navigation
A tag with a parent now creates a navigation section named after that parent. Its child tags become operation groups inside it. Bump.sh’s example uses “Journeys” as the parent with “Stations” and “Trips” as children. It calls this the native version of its x-tagGroups extension. When a tag hierarchy exists, x-tagGroups is ignored. The extension remains the route for OpenAPI 3.1 and earlier and for AsyncAPI documents. Nested navigation works only in the “automatic” or “group by tag” grouping modes.
Badges, streaming and custom methods
A tag with kind: badge puts a badge carrying the tag’s name on every operation or webhook that uses it. Bump.sh suggested beta features, release candidates and plan-restricted endpoints. Its example is a “Release candidate” badge on a streaming trip-updates endpoint.
For streams, the itemSchema field shows the structure of each item in a streamed response instead of an opaque stream. The example uses application/jsonl. The additionalOperations field documents custom HTTP methods the way standard ones appear. The example is a PURGE operation that clears a cache entry.
Examples and authentication details
Example dataValue shows pre-serialization data in request and response examples. serializedValue shows the example as sent over the wire, unchanged. It also feeds the cURL samples for path, query and header parameters. A security scheme referenced by URI, such as #/components/securitySchemes/apiKey, now displays like any other security requirement. The OAuth 2 deviceAuthorization flow, for devices without a browser, appears with its Device Authorization URL. The oauth2MetadataUrl field shows in the Authentication section.
The December release had already covered the QUERY method, tag summary, server name, response summary and deprecated security schemes.
The take
We think the tag hierarchy is the change most teams will feel first. A spec that describes its own grouping carries that grouping with the file. Any tool that reads 3.2 can use it. x-tagGroups works only where a tool knows about it. Badges and itemSchema follow the same idea: the information lives in the spec, not in a vendor’s settings. The ignore rule is the risk. If a spec carries both a tag hierarchy and x-tagGroups, Bump.sh drops the extension. Navigation can change on the next deploy. We’d run a preview deploy of any 3.2 spec that has both. Compare the sidebar before publishing.


