Add a publishing API key
Call APIRecap from your CI or deployment workflow with your OpenAPI JSON, YAML, or Markdown document. Read the API guide ↗
API docs that publish with your release
Add one authenticated API call to your deployment. APIRecap publishes the latest docs, keeps every version, and gives clients a clear view of what changed.
No manual doc update after every release.
POST /api/v1/projects/42/apis/payments/versionsAPI callAlso ready for your clients v2.3 → v2.4
Publish the files you already generate.
THE WORKFLOW
Set up your publishing key once. After a successful release, your workflow sends the new document to APIRecap.
Call APIRecap from your CI or deployment workflow with your OpenAPI JSON, YAML, or Markdown document. Read the API guide ↗
After a successful deploy, that API call publishes a new version and updates the current documentation link.
Readers get the latest docs, a version history, and a side-by-side view of contract changes.
WHY APIRECAP
Your deployment can publish the latest docs for you. Your clients get a dependable current link and a clear record of what changed.
Get early accessSend a new document from your release pipeline. The latest docs update without a dashboard visit.
Every published version has its own URL. A later release doesn't rewrite what you shipped before.
Choose listed, unlisted, or private access, and decide whether readers can browse older versions or changes.
Keep multiple APIs under a client project, each with its own releases and documentation.
SIMPLE PRICING
Publish docs automatically, give clients a clear place to read them, and bring your team along. One straightforward monthly price.
Per workspace. Built for teams that publish APIs for clients.
Everything included
Early access is via the waitlist. Checkout opens at launch.
EARLY ACCESS
Join the waitlist and we'll let you know when APIRecap is ready for your team.