LegilioMove to Legilio from another OpenAPI or Swagger macro
Steps
- Install Legilio from the Atlassian Marketplace, if your site doesn’t have it yet. A site admin does this once.
- Keep the old app installed until you finish: its macro settings show where each spec comes from.
- Edit the page, select the old macro and click the pencil icon to open its settings.
- Type
/legilionext to it, pick Legilio API Docs and set the spec as described below. - Check the docs, delete the old macro and publish the page.
If the old macro loaded the spec with a username, password or token, they’re stored in the page and its history. Change them once you’ve switched.
Where the spec comes from
- Pasted into the old macro. Copy it and paste it into Legilio.
- A URL or a Git repository. Download the file, attach it to the page and pick it in Legilio.
- A page attachment. Pick the same file in Legilio. If it’s attached to another page, attach it to this one.
| App and macro | Spec sources |
|---|---|
| Open API (Swagger) Integration Macro: Open API (Swagger) Integration for Confluence | Pasted, URL or Git, link to an attachment |
| Visualize OpenAPI (Swagger) documentation Macro: OpenAPI (Swagger) documentation integration | Pasted, Remote location (URL or Git), Store API definition as attachment |
| Swagger UI for Confluence Macro: Swagger UI | Pasted, URL |
| Open API (Swagger) Editor for Confluence Macro: Open API Viewer | URL or Git, pasted (used when the URL is empty), attachment |
What works differently
Legilio has no Try it out, because it never connects to anything outside Atlassian. To call your API, use Copy as cURL. Other limits are listed in the documentation.