Review the contract, not only the example
A changed type or required list can break a client without changing the sample response. Read the path-level result before approving a schema update.
Compare JSON Schema versions and review structural changes before publishing an API contract.
JSON Schema structure diff
Paste two JSON Schema or OpenAPI component drafts
Compare two JSON Schema or OpenAPI component drafts. The result reports structural paths, required-list changes, and type or constraint changes.
No. It compares two JSON documents. Use a schema validator separately when you need to check whether either draft is valid.
No when the default option is enabled; object keys are normalized before paths are compared.
The result is downloaded as a separate file. Keep your original until you have checked the JSON Schema structure diff.
Open the JSON Schema structure diff in the application that consumes it and spot-check the parts that matter to you; the original file stays untouched if you need to re-run with different options.
A changed type or required list can break a client without changing the sample response. Read the path-level result before approving a schema update.
Compare the JSON Schema structure diff with the original while both are fresh; destinations differ, and a quick check here saves a re-upload later.