API documentation that stays correct
Alidade makes one Confluence app: Swagger UI, OpenAPI Docs & API Catalog for Confluence. It renders an OpenAPI or Swagger specification on a Confluence page — and then does the part the rest of the category leaves out.
Your endpoints reach Confluence search
Every operation, path and tag from every specification is published to
Confluence's search index. Ask the catalog's Find by endpoint tab which page
documents POST /v2/invoices — or a tag, or an operation id — and it tells you.
The same index answers CQL anywhere in Confluence: the advanced search, the query builder, the Page Properties Report macro. It does not answer the plain search box at the top of the page — that reads page text, and a content property is not page text. The limitations page says so plainly.
A rendered macro is invisible to Confluence search either way. This is real indexed content.
One catalog of every API you document
A page under the Apps menu lists every specification published with the macro, across every space: title, version, endpoint count, where it lives, and how long since it changed.
It is built from a single search request, made as you — so it shows exactly the pages you are allowed to see, and it never crawls your instance.
Four ways in, and none of them ask for a credential
Paste a document. Point at a public URL. Pick a page attachment. Or have your CI pipeline push it — which is how a specification in a private repository gets here without anyone handing us a repository token.
This app stores no repository credential, ever. That is a rule, not a setting. Your pipeline already holds the credential; it never leaves your side.
What it does not do is written down
The limitations page is published and kept current. It was written alongside the product rather than after the first bad review, and it says plainly where the platform stops us and where we stopped ourselves.
Read it before you buy.