Stop breaking API changes at pull request time.
When an API contract lives in GitHub, the safest time to catch a breaking change is before merge. API Contract Guard compares the proposed OpenAPI contract and flags compatibility risks early.
Catch consumer-visible breaks
Removed endpoints, removed response codes, newly required fields and incompatible schema changes are highlighted before release.
Keep review close to code
Developers see the compatibility result on the same pull request as the implementation change, not days later in a release checklist.
Give API owners a clear gate
Use the GitHub Check as a lightweight contract gate for teams that want fewer accidental API regressions.
Protect every pull request automatically
Install the GitHub App, choose a repository and get a clear pass or fail status whenever its OpenAPI contract changes.
Frequently asked questions
What counts as a breaking API change?
Examples include removing a path, removing a response status, making a parameter required or changing a schema in a way existing consumers cannot safely accept.
Does it replace human API review?
No. It gives reviewers a focused compatibility report so they can spend time on design decisions instead of manually scanning OpenAPI diffs.
Can I start without changing branch protection?
Yes. Install it first, watch the results on pull requests, then require the check once your team is comfortable with it.