API Change Detection
Detect breaking API changes before they reach production.
What It Does
API Change Detection continuously monitors your API specifications for changes. When a breaking change is detected (removed field, changed type, new required parameter), it flags every affected test, shows the impact analysis with before/after comparison, and provides an approval workflow so your team can review and adapt before anything breaks in production. Non-breaking changes are classified automatically and can be auto-accepted with test updates applied in the background. This protects API consumers from unexpected contract violations and gives your team confidence that spec changes are reviewed before they propagate.
Overview
Monitors your APIs for breaking changes by diffing your API specification on every sync. When a field is removed, a required parameter is added, a response type changes, or an endpoint is deprecated — the platform flags every affected test, shows a detailed impact analysis, and provides an approval workflow for your team. Non-breaking changes (new optional fields, new endpoints) are auto-accepted and tests are updated automatically. Breaking changes require team review before tests are modified. Combined with the scheduler, change detection can run on every deploy to catch API contract violations before consumers are affected.
Key Capabilities
How It Works
- 1
Sync your API specification regularly (manual upload, URL fetch, or CI trigger)
- 2
Platform diffs the new spec against the previous version field-by-field
- 3
Breaking changes trigger impact analysis and notifications to the team
- 4
Review changes in the approval workflow — accept, reject, or defer each change
- 5
Non-breaking changes are auto-accepted and tests updated automatically
Available on
business Plan & Above
Upgrade to the business plan to unlock this feature.
Try Change Detection Today
Start your 15-day free trial — no credit card required.