OpenAPI (Swagger) Viewer by Bitwerf turns an OpenAPI or Swagger specification into API reference documentation on your Confluence pages. It is built on Atlassian Forge, so it keeps working after Connect support ends, and your API design stays inside Atlassian.
The app is on its way to the Atlassian Marketplace. Email hello@bizzkitt.ai if you want to hear when it is available.
Atlassian ends support for apps built on the older Connect platform on 31 January 2027 (Atlassian announcement). If your current Swagger or OpenAPI macro comes from a Connect app, switching takes a few minutes per page:
/openapi, paste the specification into the new editor and click Save.| OpenAPI (Swagger) Viewer by Bitwerf | Swagger UI in an iframe or Connect app | |
|---|---|---|
| Where it runs | Inside Confluence, on Atlassian Forge | On the app vendor's servers or a page you host |
| Where the specification lives | In the Confluence page | Often on an external URL or the vendor's side |
| Try it out requests | No, nothing is sent outside Atlassian | Usually yes |
| After Connect support ends | Keeps working | Depends on the vendor moving to Forge |
Yes. Paste the same OpenAPI or Swagger document, in JSON or YAML, into the new macro.
No. Sending requests to your API from the page would mean data leaving Atlassian. This app shows the documentation and sends nothing anywhere.
No. Nothing is fetched from outside Atlassian. Paste the specification into the macro; if it is split over several files, bundle it into one document first.
Up to 2 MB per macro. The details of an operation are built when a reader opens it, so large APIs stay quick.
Atlassian ends support for Connect apps on 31 January 2027. OpenAPI (Swagger) Viewer by Bitwerf is built on Forge, the platform Atlassian supports going forward.
Full documentation · Support · Privacy · Security
Bitwerf is a trade name of BizzKitt B.V., Frederikstraat 67, 3034 LD Rotterdam, the Netherlands (KvK 42149345, VAT NL869932354B01).