API & Specs · OpenAPI / Swagger macro
Consumers integrate on their own, and your inbox notices
With the OpenAPI / Swagger macro your machine-readable, human-hostile spec becomes full Swagger UI inside the Confluence page: every endpoint documented, every schema expandable, requests fired without leaving the page. Consumers get their answers from the page, and you stop getting the messages.
You stop answering "what does this endpoint return?"
The question stops being a message to your team. A reader expands the operation, reads the schema, sends a request and sees the real response - with the round trip time if you want it shown. Consumers integrate on their own, and your inbox notices.
Each audience gets the slice of the spec it needs
A hundred-endpoint spec is not the page a partner team needs. Let readers filter by tag, cap how many tags are shown, choose how operations are ordered and how much starts expanded - so the payments team's page and your internal reference come from the same file and still read like they were written for each other.
Readers try GET without being able to DELETE
Choose which HTTP methods stay interactive, so your documentation page offers
GET on real data while DELETE is there to read about and
not to run. Credentials for a spec behind a protected URL are stored encrypted with
the macro rather than pasted into the page body, and vendor or common extensions are
shown or hidden depending on who is looking.
Your documentation cannot fall behind the API
Point the macro at the spec your build already publishes - a URL, a GitHub, GitLab or Bitbucket repository, a page attachment, Google Drive, or a credentialed S3, SFTP or database connection - and the page renders that file rather than a description of it. Readers download the spec as JSON or YAML, whichever their generator wants, and links in the rendered docs open in a new tab so nobody loses the page they came from.
What the other Swagger apps leave you copying by hand
Rendering Swagger UI in Confluence is a crowded shelf - seven apps, some with thousands of installs. Every one of them takes the spec from a URL, a page attachment or text pasted into the page. That is fine until the spec you need is the one your pipeline drops in an S3 bucket, keeps behind SFTP, or holds in Google Drive - then someone on your team is copying files by hand into a page again. This macro reads it from any of those, through a connection an admin sets up once and every other macro in the pack shares.
OpenAPI / Swagger is one of 31 macros in Macro Pack
One app to install, one licence to renew, one place your team learns - and 30 more formats it already reads, from spreadsheets and diagrams to API specs and documents.
See every macro in the pack