Release notes

What's new in Apifolio, the OpenAPI and Swagger docs app for Confluence.

2.2 (October 2026)

Macro dialog

  • Try a sample API: a fictional Payments API opens in the preview, and is attached to the page only if you choose to use it.
  • Drop a file anywhere on the dialog to attach it. On a page with exactly one YAML or JSON file, that file is selected for you.
  • Import from another app's macro on the same page (Open API (Swagger) Integration, Visualize OpenAPI, Swagger UI for Confluence, Open API (Swagger) Editor and more): the spec, its file and its display options carry over, and stored credentials never do. See Moving from another app.
  • Another page accepts short links (/wiki/x/…) and page titles, with pages that use Apifolio first.
  • Only these endpoints: pick endpoints to show. With 1 to 3, the macro becomes a compact endpoint card for how-to guides.
  • New options: Hide webhooks, Schema fields (collapsed, first level or all levels open), Density (comfortable or compact) and Code languages.
  • The dialog shows how many endpoints Confluence search covers, and warns when anonymous visitors won't see the file.
  • Works on pages that were never published: upload, drop or paste a spec, preview it and save.
  • With an inactive subscription, the dialog says so and previews what readers will see.

Reading the docs

  • 17 code languages: PowerShell, cURL for the Windows command prompt, HTTPie, raw HTTP, Node (axios), Python (httpx), Kotlin, Swift and Rust join the 8 default tabs.
  • Edit request: fill in parameters, the body, the server and credentials, and every code sample and Copy for AI follow. Nothing is sent or stored. See Edit request.
  • Server variables, and a choice between security alternatives, reach every code sample.
  • Variant pills follow the selected example, and discriminator subtypes (schemas that extend a base schema with allOf) get pills too.
  • Expand all and Collapse all on every schema.
  • Navigation tree with OpenAPI 3.2 nested tags at any depth, with full keyboard support.
  • Search finds endpoints from pasted URLs, typos and request or response field names. Arrow keys and Enter move through the results.
  • The Overview shows the terms of service, documentation links, the x-logo (from the spec or the page, never from the web), OAuth and OpenID Connect URLs, scope descriptions and an offline Get a token request.
  • Parameter examples as chips, example descriptions, and response links that open the linked endpoint.
  • The classic layout gets a Schemas section. With filters, only the schemas the shown endpoints use are listed.
  • Copy as Confluence content: a dated snapshot that pastes as native headings, tables and code blocks, visible on public links, in the table of contents and in search.
  • Embed this API on another page copies the page link, with a one-line how-to.
  • The footer says when the file changed, with its version, its version comment and a History link.
  • In edit mode, a note says when the Confluence search index is older than the file.
  • Clearer errors: no access to the source page (with Open source page), Confluence busy (automatic retries, then Try again), parse errors with the lines around the error and a hint, files with data models only, and specs split over several files.
  • A part that fails to render shows a short note instead of blanking the macro.
  • Macros that show the same file on a page share one download.

Exports, search and Rovo

  • PDF and Word exports add response field tables, a cURL request per endpoint, server variables, sign-in details, an Errors section and a Data models appendix. Big exports keep every endpoint.
  • The Confluence search index of large APIs holds operation IDs, path words and common summary words: all 1,232 endpoints of GitHub's REST API are findable.
  • Rovo agent: find-api-operations uses the macro's search, get-code-sample knows all 17 languages, page inputs accept short links, and specs on blog posts work with every action.
  • Spec files saved as UTF-16 load.

Macros saved with 2.0 keep their settings. Apifolio 2.2 asks for no new permissions.

2.0 (4 October 2026)

First release on the Atlassian Marketplace.

  • Modern three-pane and classic Swagger-style layouts.
  • OpenAPI 3.0, 3.1, 3.2 and Swagger 2.0, YAML and JSON, up to 25 MB.
  • Search across endpoints, parameters and data models, with keyboard shortcuts.
  • Code samples in 8 languages with correct parameter serialization.
  • One example per oneOf/anyOf variant, with discriminator values.
  • Copy for AI and Markdown download.
  • Apifolio API Expert agent for Rovo.
  • PDF and Word export with real content.
  • Confluence search indexing of endpoints.
  • Guests and anonymous visitors in public spaces.
  • Data model pages with an example generated from the schema.
  • Links between endpoints and schemas written for Redoc or Swagger UI (#operation/..., #/components/schemas/...) work inside Apifolio.
  • Light and dark mode, full screen, accessible keyboard navigation.

View as Markdown