Migrate from Visualize OpenAPI (Swagger) documentation
Move Confluence pages from Dutch Beginners' Visualize OpenAPI (Swagger) documentation, a Connect app, to Apifolio: import the spec, the expand, operations and filter options, and rotate repository tokens.
Visualize OpenAPI (Swagger) documentation by Dutch Beginners shows OpenAPI and Swagger specs in Confluence with Swagger UI. 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.
What the import does
The Apifolio dialog recognises the app's swagger-open-api-macro macro.
| In the old macro | In Apifolio |
|---|---|
| A spec pasted into the macro | Checked, attached to the page as a file named after the API title, and selected |
| A spec stored as a page attachment | Selected |
| A link to the spec (a URL or a GitHub, Azure DevOps, GitLab, Bitbucket or SwaggerHub repository) | Not downloaded: the dialog shows the link, you download the file and click Attach the file |
| A repository token | Never copied. The dialog names it so you can rotate it |
expand |
full turns on Expand endpoints by default (classic layout); list or none keeps endpoints closed |
operations |
Only these endpoints, for the operation IDs (or methods and paths) that exist in the file |
filter |
Only these sections: the sections whose name contains the text |
order, methods, validator, maxDisplayedTags, displayOperationId |
No Apifolio equivalent: listed in the dialog |
The Classic (Swagger style) layout is preselected, so the page keeps a familiar look. You can switch to the modern three-pane layout in the same dialog. Other parameters follow the full table.
About the options without an equivalent: Apifolio always shows operation IDs, lists sections and endpoints in the order of the spec, never sends the spec to an outside validator, and has no limit on the number of sections it shows. To show fewer sections, use Only these sections.
Specs split over several files
If the old macro read a repository where the spec uses $ref to other files, bundle it into one file before you attach it, for example with npx @redocly/cli bundle openapi.yaml -o bundled.yaml. Apifolio reads one file and never fetches the others.
Steps
- Edit a page that uses the old macro and type
/apifolio. - In "Found 1 Open API (Swagger) macro on this page", click Import, Use this file or Attach the file.
- Check the preview and the display options, then click Save.
- Delete the old macro by hand and publish the page.
- Revoke any repository token that was stored in the old macro: it remains in the page history.
Details: Moving from another app.
What changes for readers
- Try it out is replaced by Edit request: readers fill in parameters, the body and credentials, and copy a ready-to-run request in one of 17 languages. Nothing is sent from Confluence.
- Specs that came from a repository are now page attachments. Keep them up to date from your CI: see Keep the docs in sync.
- New: search that understands pasted URLs and typos, PDF and Word exports with the full reference, Copy for AI and the Rovo agent.
See What Apifolio does not do, and why.
Visualize OpenAPI (Swagger) documentation is a product of Dutch Beginners. Apifolio is an independent product, not affiliated with or endorsed by its vendor.