Valid Example: User Profile JSON Matches Its Schema
Check one JSON value against a small subset of JSON Schema: types, ranges, required keys, properties, items, pattern, and enum.
🔒 Processed entirely in your browser — nothing you enter here is ever uploaded.
The result appears on this page after you run the tool. Nothing you enter is uploaded.
Result
About this tool
This page opens the JSON Schema validator preloaded with a small user-profile schema — requiring id, email and age, with type and minimum/minLength constraints on each — and a JSON payload that satisfies every one of those rules. Validation runs the moment the page loads, so the pass result below is a real, live check, not a canned example.
A user object with a numeric id, an email string and an age is one of the most common shapes validated against a schema, whether for an API request body, a signup form payload or a database seed file. This payload passes because id and age are both whole numbers matching their integer type, email is a string of at least 5 characters as the minLength rule requires, and all three required fields — id, email and age — are present.
Use this pair as a template: edit either the schema or the JSON document in the two text areas to see how the result changes. The missing-required-field and wrong-type presets linked below use this exact same schema but with a payload that fails it, so you can see precisely how each kind of validation error is reported.
Example. The value {"age": 15} against a schema that requires name and an integer age of at least 0 fails with Required property "name" is missing. {"name": "Ada", "age": 15} against that schema passes.
Limit. Only type, minimum, maximum, minLength, maxLength, pattern, enum, required, properties, and items are applied. $ref, combinators, format, and additionalProperties are ignored, and a bad pattern is skipped.