How to use API Contract Change Analyzer
- Paste before and after OpenAPI 3.0.x JSON documents.
- Run the comparison and read breaking, added, relaxed and review findings.
- Inspect unsupported references, composition and schema keywords separately.
- Export the change report and review affected clients before changing a server.
Example: API Contract Change Analyzer
Review supported OpenAPI request and response compatibility changes.
Supported inputs and limits
- Up to 2 MiB, 30,000 JSON values, 40 nesting levels and 200 operations per document, with at most 5,000 findings.
- Supports OpenAPI 3.0.x JSON;
- Swagger 2, OpenAPI 3.1, YAML, reference expansion and composition evaluation are unsupported.
- Checks cover operation/media/status removals, parameter and body requirements, property requirements and enum directions.
- Bounds, types, nullability and security changes require review.
More details
No external reference is fetched.
A report without a breaking finding is not complete compatibility certification.
JSON numeric literals are limited to 128 characters and must retain their decimal value through browser Number conversion; integers outside the safe integer range and unsupported precision are refused.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Questions about API Contract Change Analyzer
Which compatibility direction is assumed?
The report considers an existing client calling an updated server. A newly required request field can break that client; a newly allowed response enum value can also require client changes.
Will a remote schema reference be downloaded?
References are reported as unexpanded and affected schemas need manual review. The tool makes no network request and does not follow even a local reference chain.
Does a clean report prove the APIs are compatible?
Only the documented subset is compared. Unsupported constructs, application behavior and generated-client assumptions still need separate review and tests.