Plans

Catch breaking API changes in every pull request — free forever.
Upgrade to Pro to enforce a review and approval process before they ship.

Free

Detect breaking changes in CI. No account needed.

oasdiff CLI — all commands
300+ breaking change rules
GitHub Action with inline annotations
Side-by-side spec diff
All output formats (JSON, YAML, text, HTML)
CI/CD integration (any platform)

View on GitHub

Pro

Approval workflow for teams managing up to 5 API repositories.

$100/month

Everything in Free
Rich PR comment — like Codecov, but for API changes
Commit status check blocks merge until all changes reviewed
Side-by-side spec diff with approve / reject per change
Private repository support

Start free trial

No credit card required · Cancel anytime

Enterprise

For organisations managing many APIs at scale.

Custom

Everything in Pro
Unlimited repositories
SSO / SAML
Dedicated support & SLA
Custom contract & invoicing
On-premise deployment option

Talk to us →

What you see on a pull request

Both tiers detect breaking changes. The difference is what happens next.

Free

Inline annotations on the Files Changed tab

openapi.yaml

42- 200:

43 description: Success

removed the success response with the status '200' for the response with the status '200' [GET /orders]

removed the required request property 'email' [POST /users]

No context — who approved this? Is it intentional?

Pro

Auto-updating bot comment on the PR timeline

oasdiff-botcommented

oasdiff API Change Report

🔴 2 breaking·🟢 3 info

Sev	Change	Review
🔴	GET /orders — success status removed	✅ Approved
🔴	POST /users — required property removed	⏳ Review

1 of 2 breaking changes reviewed · merge blocked

What the PR comment looks like

A single auto-updating comment on the PR timeline. Each change links directly to the side-by-side diff and review page.

oasdiff-botcommented

oasdiff API Change Report

🔴 3 breaking changes·🟡 2 warnings·🟢 5 info

Severity	Change	Path	Review
🔴	response-success-status-removed	`GET /orders`	✅ Approved by @alice
🔴	request-property-removed	`POST /users`	⏳ Review
🔴	request-parameter-type-changed	`GET /products`	❌ Rejected by @bob
🟡	response-optional-property-removed	`DELETE /sessions`	⏳ Review
🟢	endpoint-added	`POST /webhooks`	—

Compared at commit abc1234 · Powered by oasdiff

Review breaking changes before they ship

Each breaking change gets its own approve / reject decision with an optional comment and audit trail.

oasdiff.com/review/…/my-api/42

API Change Review

my-org/my-api · PR #42 · commit a1b2c3d

⏳ 1 change awaiting review · 1/2 reviewed

🔴GET /orders

✅

removed the success response with the status '200'

✅ Approved by @alice · 2h ago · "intentional — migrating to 201"

🔴POST /users

⏳

removed the required request property 'email'

Getting started with Pro

Sign up

Add to your workflow

Add the oasdiff PR comment action to your GitHub Actions workflow with your token.

See it in PRs

Every API spec change gets a rich PR comment with a link to the hosted review page.

Review and approve

Open the review page to see a side-by-side diff, approve or reject each breaking change with a comment, and unblock the merge.

.github/workflows/api-diff.yml

- uses: oasdiff/oasdiff-action/pr-comment@v0.0.36
  with:
    base: base/openapi.yaml
    revision: openapi.yaml
    oasdiff-token: ${{ secrets.OASDIFF_TOKEN }}

Common questions

Will the CLI always be free?

Yes. oasdiff is open source and the CLI stays free forever. The paid tier adds the hosted service layer (PR comments, hosted reports) on top.

What is the oasdiff-token?

An API token that authenticates your team with the oasdiff service. Sign in with GitHub to get one — your token is available instantly after signup. Each token is associated with your account.

Does this work with multi-file specs?

Yes. oasdiff tracks source locations across $ref chains, so breaking changes in referenced schemas point to the right file and line.

How is pricing structured?

$100/month per organization, billed monthly. Start with a 30-day free trial — no credit card required.