Moving your OpenAPI macros off Connect

Atlassian ends support for Connect apps on January 31, 2027.

Atlassian is retiring Connect, the original framework for Confluence Cloud apps, in favour of Forge. After the end-of-support date, Connect apps receive no fixes from Atlassian. They won't disappear overnight, but as Confluence keeps changing, they are expected to break more and more often.

If your API documentation relies on a Connect-based macro, now is a good time to plan the move rather than discovering broken pages later.

Check which app you use

In Confluence, open Settings → Apps → Manage apps. Atlassian marks apps that still use Connect. These widely installed OpenAPI and Swagger macros were still on Connect when we last checked the Marketplace (October 2026):

Vendors may still publish Forge versions of these apps; check each app's Marketplace listing for its current status.

Move to API Docket

1. Install API Docket alongside your current app. Both can run at the same time, and API Docket is free to try for 30 days.
2. On each page, insert the API Docket macro next to the old one and point it at the same source: the same URL, attachment or repository file. Pasted specifications can be copied across as they are.
3. Check the result, then delete the old macro and publish the page.
4. When no pages use the old app any more, uninstall it.

To find every page that uses an old macro, search Confluence with CQL, for example macro = "swagger", or ask us: we're happy to help with larger migrations.

What changes for readers

• Try it out works without CORS errors, through API Docket's relay.
• A Changelog tab shows what changed between versions and flags breaking changes.
• The documentation follows Confluence's light and dark themes.

Why Forge matters

Forge apps run on Atlassian's own infrastructure and are maintained by Atlassian's platform team. API Docket has no external servers: specifications, history and tokens are stored in your site's Forge storage. See Security for details.