Migrating from Open API (Swagger) Editor for Confluence (EliteSoft) to OpenAPI Viewer
If your Confluence Cloud pages render an OpenAPI or Swagger spec with Open API (Swagger) Editor for Confluence by EliteSoft, this guide moves them to OpenAPI Viewer, an app built on Atlassian Forge and designed to be Runs on Atlassian: nothing leaves Atlassian and no credentials are stored. One thing to decide first: the old app is a viewer and an editor, and OpenAPI Viewer is a viewer only.
Facts about the old app were checked on 13 October 2026 against its Marketplace listing and vendor documentation.
Why migrate now
Atlassian ends support for the Connect framework on 31 January 2027, and warns that breakages will increase afterwards. Since July 2026, Confluence admins have seen a banner on apps that still run on Connect, saying the platform will be unsupported after that date.
The Confluence Cloud edition is a Connect app (version 1.0.17-AC, released 25 September 2024), and its listing shows no Forge version. Newer 4.x releases on the listing are for Data Center and Server.
Feature map
| Open API (Swagger) Editor for Confluence | OpenAPI Viewer | Status |
|---|---|---|
| Viewer macro that renders interactive documentation | Viewer macro, Swagger UI-compatible renderer bundled in the app | Same |
| Supported OpenAPI versions (not stated on listing) | OpenAPI 2.0, 3.0.x, 3.1 | Same or wider |
| Spec pasted in macro body | Paste source, up to about 150 KB | Same |
| Spec from a hosted URL entered in the macro | Not supported | Not in v1. Workaround: CI push |
| Spec as page attachment | Attachment source: pick from a list, "always latest" or pinned | Not documented for old app; ours: yes |
| Git hosting (Bitbucket, GitLab, GitHub) | Not supported | Not in v1. Workaround: CI push |
| "Try it out" while composing and viewing | Not supported | Not in v1. Workaround: Postman, curl or your gateway console |
| Built-in editor (open from your profile menu; export to JSON or YAML) | None | Not in v1. Workaround: edit in your repo or IDE, or in the Swagger Editor in a browser |
| Search, expand/collapse, deep links, full-screen, auto-height, dark mode | Included | Not documented for old app; ours: yes |
| Price: from USD 10/year at 10 users; USD 150 at 100; USD 425 at 500 | Free up to 10 users, then paid by user tier | Different |
Five steps
- Export every spec, including the ones in the editor. For a pasted spec, open the old macro and copy the body into
openapi.yaml. For a URL, download the file. Then open the old editor from your profile menu and export each definition you still maintain as YAML or JSON. Where the editor keeps definitions is not documented, so do not assume the macro body has the latest copy. - Move the source of truth into your repo. OpenAPI Viewer does not edit specs, so each spec should live in a Git repository or a shared folder. Commit the exported files there. A spec under about 150 KB can be pasted into the new macro; a larger one is attached to the page. To update the page on every merge, add the pipeline from Push your spec from CI; ready-made pipelines are on that page.
- Install OpenAPI Viewer and replace the macro. Install it beside the old app (30-day trial). On each page add the new macro, choose Paste or Attachment, then delete the old macro. See the quick start and attachment mode.
- Verify. Reload as a normal reader. Check paths, schemas, deep links and dark mode, and compare your busiest page with the old rendering.
- Delete the old app. Once every page and every exported definition is confirmed, uninstall the old app well before 31 January 2027.
What you lose, and why
- The editor. Version 1 is a viewer only, and writing specs is a different job. A spec in Git, edited in your IDE and reviewed in pull requests, then pushed to the page, gives you history and review that a macro editor does not.
- Try it out. Live requests need external permissions on Forge, and an app with external permissions cannot be Runs on Atlassian. See the FAQ.
- URL and Git fetch. Fetching is outbound traffic, which Runs on Atlassian does not allow. With the push model, your pipeline uploads the spec using your own Confluence token, kept in your CI secret store. The app never reaches your repository and never holds a credential.