r/microapis • u/Important_Fault_5725 • Mar 12 '26
How do you detect breaking API changes before they hit production?
Hey everyone,
Working in a microservices environment and keep running into the same problem:Â breaking API changes that slip through and cause issues.
Typical scenario:
Team A changes their OpenAPI spec (removes a field, changes a type)
Team B's service depends on that field
Nobody notices until something breaks in staging or worse, production
What we've tried:
Manual code reviews → doesn't scale, easy to miss
Contract testing (Pact) → works but heavy setup, needs buy-in from all teams
Just hoping for the best → 😅
I'm thinking about building a tool that:
Stores a baseline of your API contracts (OpenAPI, Protobuf)
Detects breaking changes automatically (removed fields, type changes, etc.)
Shows the "blast radius" - which downstream services would be affected
Integrates into CI/CD to warn or block PRs with breaking changes
My questions:
Is this actually a pain point for your team, or do you have it solved?
What tools/processes are you using today?
Would something like this actually help, or is it solving a problem that doesn't really exist?
CLI tool vs. web dashboard - what would be more useful?
Curious to hear how other teams handle this. Maybe I'm overcomplicating something that has a simple solution I'm missing.
Thanks!