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

  1. Load the sample and retain the default Schema: age has type integer and minimum 0.
  2. Validate structure: the first mismatch is /age with the type rule. Locate field selects "30".
  3. 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

Continue this workflow

Find a string where your JSON Schema expects an integer →

About this tool

Syntax validity does not prove that an API response satisfies its contract. This tool checks required fields, types, bounds and other draft-07 rules using Ajv in a browser worker. It reports the first mismatch without modifying data.

How to use

Try the sample: remove extra to resolve additionalProperties, then change age from "30" to 30 to resolve the type error. Validate again to see a passing result. Required-field errors identify the parent object and missing property in the details.

Tips & Notes

Only draft-07 and in-document references are supported. Unknown formats and keywords fail explicitly. No remote schemas are downloaded. Duplicate keys and unsafe numbers block validation. Schema/data limits are 30,000/100,000 characters with a 3-second timeout.