Skip to main content
Cloud only. The app is built on Atlassian’s Forge platform, which doesn’t support Data Center.
OpenAPI 2.0 (Swagger) and 3.0, via the underlying Swagger UI renderer.
Yes, if it’s configured with a URL — it’s fetched live on every page view. If you pasted the document directly as Content, it’s a static snapshot and only updates when you edit the macro and paste in the new version.
Yes. Set Authorization to Basic to provide a login and password, or Api Key to provide a key. Swagger UI applies them automatically when the page loads, so viewers don’t need to authorize manually.
There are two distinct warnings. A license warning means the site doesn’t have an active license or trial. A configuration warning means the macro doesn’t have a usable OpenAPI document yet — check that URL or Content is filled in for the selected OpenAPI document type. If it looks configured correctly but still won’t load, confirm the spec’s URL is reachable over plain http:// or https:// — Forge apps can only reach an allow-listed set of domains, and while most common top-level domains (.com, .io, .dev, .app, and similar) are covered, some country-code domains aren’t, so a spec hosted on one of those will fail to fetch.
Can’t find what you’re looking for? Visit the Better Swagger UI for Confluence service desk portal.