OpenAPI Breaking Change Diff
Compare two OpenAPI specs and flag removed paths, stricter schemas, and other breaking API changes.
Compare OpenAPI specs for breaking API changes
API teams evolve OpenAPI 3 documents when they add endpoints, tighten request
bodies, or narrow enums. A breaking change removes a path, drops an HTTP method, deletes a schema,
or makes fields required. This diff tool parses two YAML or JSON OpenAPI files in your browser and
lists breaking and compatible differences at the path and components.schemas level.
What the diff checks
- Removed API paths or operations
- JSON request body schema regressions on matching operations
- Shared model changes under
components.schemas(required fields, removed properties, enum narrowing)
For JSON Schema-only comparisons without full OpenAPI context, use JSON Schema Compatibility Diff. To lint a single spec, try OpenAPI Validator.
Frequently Asked Questions
Are specs uploaded to your servers?
No. Both documents stay in the browser. Paste from CI artifacts or local files.
Does this resolve $ref pointers?
Not fully. Inline schemas and shared component schemas are compared. External references may need bundling first.
Is every server-side behavior detected?
No. Response schema removals, status code changes, and undocumented headers are not exhaustively modeled. Treat results as a focused compatibility checklist, not a formal guarantee.
Related Tools
Dockerfile Generator
Regex Memo
Plist to YAML Converter
JSON-LD To Flattened
Mixed Air Calculator
Typography Scale Generator
Chocolate Fountain Calculator
Circadian Rhythm Calculator
WHIP Calculator
Permutation with Replacement Calculator
Project Cost Estimator
SVG to Base64 Converter
Drone Flight Time Calculator
Rational Exponents Calculator
Hypothesis Testing Calculator
URL Decode JSON
Price Per Weight
Mortgage Calculator
Natural Gas Converter
Newton Meter Converter