# Migrate from SwaggerHub Integration for Confluence

Move Confluence pages from SmartBear's SwaggerHub Integration for Confluence, a Connect app, to Apifolio: export the API definition from SwaggerHub, attach it, and keep it in sync from CI.

**SwaggerHub Integration for Confluence** by SmartBear shows API definitions hosted in SwaggerHub on Confluence pages. In October 2026 it is a Connect app on the Atlassian Marketplace, and Atlassian ends support for Connect apps on 31 January 2027. Apifolio is a Swagger UI alternative built on Forge that runs on Atlassian.

Apifolio never calls SwaggerHub or any other service outside Atlassian, so the definition has to be a file attached to a Confluence page. The Apifolio dialog does not import this app's macro: move each page by hand, as below.

## Steps

1. In SwaggerHub, download the API definition as one YAML or JSON file. If it references SwaggerHub domains or other files, download a version with the references resolved: Apifolio reads one file and never fetches the others.
2. Edit the Confluence page, type `/apifolio` and drop the file on the dialog (or click **Upload a file**). It is attached to the page and selected.
3. Choose the display options. **Classic (Swagger style)** keeps a Swagger UI look; **Modern (3 panes)** puts navigation, docs and code side by side.
4. Click **Save**, delete the old macro and publish the page.
5. If you gave the old app a SwaggerHub API key, revoke it in SwaggerHub once no page uses the app.

## Keep the definition in sync

The definition now lives in two places: SwaggerHub, where you edit it, and the Confluence attachment that readers see. To keep them aligned, add a step to your CI that downloads the definition from SwaggerHub (with SwaggerHub's API or CLI) and uploads it to Confluence as a new version of the same attachment. The upload is the same as in [Keep the docs in sync](/docs/keep-in-sync/). All of this runs in your own CI, with your own tokens: Apifolio never sees them.

## What changes for readers

- **Try it out** is replaced by [Edit request](/docs/edit-request/): readers fill in parameters, the body and credentials, and copy a ready-to-run request in one of [17 languages](/docs/code-samples/). Nothing is sent from Confluence.
- New: search that understands pasted URLs and typos, PDF and Word exports with the full reference, Copy for AI and the Rovo agent.
- AsyncAPI definitions from SwaggerHub can't be shown: Apifolio shows OpenAPI 3.x and Swagger 2.0 files.

See [What Apifolio does not do, and why](/docs/what-apifolio-does-not-do/).

SwaggerHub Integration for Confluence is a product of SmartBear Software. SwaggerHub and Swagger are trademarks of SmartBear Software. Apifolio is an independent product, not affiliated with or endorsed by SmartBear.
