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), 3.0, and 3.1, via the underlying Stoplight Elements renderer. Documents that use $ref to other http(s) documents are also supported.
Yes, if it’s configured with a URL (Elements macro) or a Project ID (Dev Portal macro) — both are fetched live on every page view. If you pasted the OpenAPI document directly as text, it’s a static snapshot and only updates when you edit the macro and paste in the new version.
Stoplight Elements renders any OpenAPI document you give it — useful for specs hosted anywhere, including outside Stoplight’s platform. Stoplight Elements Dev Portal embeds a project’s full hosted dev portal from stoplight.io, and requires a paid Stoplight plan.
There are two distinct warnings. A license warning means the site doesn’t have an active license or trial. A configuration warning means a required field is empty — the API document (URL or pasted text) for the Elements macro, or the Project ID and Platform URL for the Dev Portal macro. 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. If only the Try It console is failing, check the Try It CORS Proxy setting.
Can’t find what you’re looking for? Visit the Stoplight Elements for Confluence service desk portal.