Skip to content
The Docs Report
Tuesday, November 17, 2026NewsletterRSS

Bump.sh Now Renders AsyncAPI 3 Documents, Replies Included

Bump.sh's Oct. 27 update renders AsyncAPI 3 with send and receive badges, operation replies, dynamic addresses and OAuth 2 scopes.

2 min read

Bump.shAsyncAPIAPI reference

Product photo of a white megaphone on a cobalt blue, teal and violet gradient

Bump.sh now renders AsyncAPI 3 documents, the company said in an Oct. 27 product update. Teams deploy them the same way as their other API documents.

Operations get their own section

AsyncAPI 3 declares operations separately and points each one at a channel. Bump.sh follows that model. Operations appear in an “Operations” section with a send or receive badge. They are grouped by tag or by channel name. The standard navigation options, including x-tagGroups, still apply. If an operation lists no messages, Bump.sh shows all the messages on its channel. Operations display their title, or their summary when no title is set.

Replies, addresses and servers

An operation’s reply renders as a “Reply” block showing the reply’s address, messages, parameters and bindings. Channels with no address display as {dynamicAddress}. A reply’s address.location appears in place of the reply channel address. Server URLs are built from protocol, host and pathname. Channels and servers show their titles and summaries.

Operation and message traits follow AsyncAPI 3 rules. A trait never overrides a value already set on its target. External docs links work on the info object, servers, operations, channels and messages. For OAuth 2, Bump.sh shows availableScopes for each flow, along with the scopes a security scheme requires.

Bump.sh pointed to an AsyncAPI 3 cheat sheet for newcomers and to its help center for the full list of supported and unsupported fields.

The take

We think the reply block matters most. AsyncAPI 3 split operations from channels. One channel can now serve several operations. Request and reply flows are first-class. A reference that ignores that split forces readers to rebuild the flow in their heads. Putting the reply next to the operation shows the whole exchange in one place. Bump.sh’s help center holds the list of unsupported fields. Check it against your own spec before you announce event docs. Then deploy a preview and read one operation top to bottom.