Invalid Example: Missing Required Field
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 the same user-profile schema as the valid preset — requiring id, email and age — but with a JSON payload that omits the email field entirely. Validation runs on load, so the failure shown below is a real, live check of this exact pair.
A missing required field is one of the most common ways real-world API payloads fail schema validation: a form that doesn't collect every field, a client that skips an optional-looking property that's actually mandatory, or a partial update that forgets a required key. The schema's required array lists exactly which properties must be present regardless of type, separately from the type and format rules that apply to each individual field.
The error message below names the missing property directly rather than making you compare the payload and schema by eye. Compare this preset against valid-user-profile-schema, which uses the identical schema with all three required fields present, and against wrong-type-field-schema for a different failure mode — a field that's present but has the wrong type.
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.