API documentation your whole team can trust

Shared docs only help if people can tell who changed what and undo a mistake. Every collection is shared with your workspace, and every change leaves a trail.

History and view-only sharing are on every plan. Comments and review of AI changes are on Team.

An AI agent's proposed change to the Refund a charge endpoint, shown as a diff with Review, Approve and Dismiss buttons
Review a proposed change before it is applied.

History and restore

Every real change to an endpoint is kept with who made it, which fields it touched and the version it produced. Open History to see the before and after, and restore any earlier version. Restoring is a new version, so you can undo it too. The latest 50 changes per endpoint are kept, on every plan.

Changes by AI agents are labeled as such, with the start of the token they used, so you can tell them from a teammate's.

Comments

On the Team plan, teammates can leave comments on an endpoint. Anyone can mark one resolved or reopen it, which makes a comment a shared to-do, and only its author can delete it. A comment keeps its author's email even if they leave.

Share an endpoint outside the workspace

Sometimes the person who needs to see an endpoint isn't on your team: a partner integrating with you, a client reporting a bug, a contractor. Press Share and invite them by email, or open the endpoint to anyone with the link, the way you share a Google Drive file. Each person, and the link, is a viewer or a commenter.

You can also share a whole collection: they browse every endpoint in it, including ones added later, but never your environments, and they can't export it. What they open is read-only: the endpoint's docs, its examples and always its latest run, so a failing response is right there. Nobody can send the request from it, and Authorization headers, cookies, API keys and secret environment values are always hidden. Each endpoint keeps one link that never changes. Comments from a shared link join the endpoint's thread, marked as coming from the share.

Review of AI changes

Turn on “Require approval for AI changes” and what an agent tries to write waits as a proposal. You see a line saying what it would do and the exact call, then approve or reject. Approving applies the agent's own call once, and the history still names the agent as the author. Reading, exporting, checking drift and running requests are never held.

Who gets what

  • ›Every plan: shared collections, history and restore, and sharing an endpoint view-only by link or email.
  • ›Team: comments (including from people you share with) and review of AI changes.

Shared by default

Collections belong to the workspace, not to a person. Every member can read and edit them, and the workspace's plan sets the limits. If a workspace is suspended for billing, its docs stay readable but can't be changed until billing is fixed.

A typical review, start to finish

  • ›You change a route and your agent proposes the matching update to the docs.
  • ›The proposal appears under “AI changes” with a one-line summary and the call it would make. Deletions are flagged.
  • ›A teammate opens the details, approves it, and it is applied once. The history shows the agent as the author and the proposal shows who approved.
  • ›If it can't be applied any more, for example because the endpoint was deleted meanwhile, it is marked as failed with the reason.

FAQ

How far back does history go?

The latest 50 changes of each endpoint. Endpoints that existed before history started begin with a baseline, so even their first change can be undone.

Are examples part of the history?

No. History covers the endpoint's definition: its name, method, path, description, parameters, headers, body, tests and folder.

Can people outside my workspace see an endpoint?

Yes, if you share it. Invite them by email (they sign in with that address) or turn on “Anyone with the link”. They get a read-only page with the docs, examples and latest run, with secrets hidden. On Team they can also comment, after signing in.

What if the workspace leaves the Team plan?

Existing comments stay readable. Writing new ones and requiring review need Team, and pending proposals can still be decided.

Keep reading

Everything is in the API workspace docs, and the other parts are Local, staging and production, Document your API from real traffic, API drift detection.

Document and test your API in minutes

Free plan, no credit card. Import a spec or start from your webhooks, and keep it true from there.

Get started free