DEBUGGING PLAYBOOK · REVIEWED 2026-10-08
Valid JSON fails the API contract
A quoted age is valid JSON, but the default draft-07 Schema requires an integer. Separate grammar errors from contract errors before changing a response.
Sample input
{"name":"Ada","age":"30"}Steps and checks
- Load the sample and retain the default Schema: age has type integer and minimum 0.
- Validate structure: the first mismatch is /age with the type rule. Locate field selects "30".
- Change "30" to 30 and validate again: it passes. Change it to -1 to trigger minimum; deleting age triggers required on the parent object.
Reference result
{"path":"/age","keyword":"type"}Avoid a misleading conclusion
Only the first mismatch is reported. Fixing one can reveal another. Unknown formats or remote references fail explicitly; they are not a successful data check.
What to do next
Use the API provider’s actual contract. The default Schema is a teaching fixture; relaxing it merely to accept a bad response hides the defect.
Related case and technical reference · Report an error or missing edge case