You've seen this before: a frontend sends a request, the backend crashes, and the logs say TypeError: Cannot read properties of undefined. The payload was missing a required field, or a number arrived as a string. JSON Schema exists precisely to stop this class of bugs before they reach production.
This guide explains what JSON Schema is, how to write one, and how to validate JSON data against it — right in your browser.
What Is JSON Schema?
JSON Schema is a vocabulary that describes the structure of JSON data. It's itself written in JSON and defines:
- What fields are required
- What type each field should be (
string,number,boolean,array,object,null) - Constraints like minimum/maximum values, pattern matching, and array lengths
- Nested object structures
Think of it as a contract between a data producer (your API, your database, your user input) and a data consumer (your backend, your frontend, your analytics pipeline).
A Minimal Example
Here's a schema for a user profile object:
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": ["id", "email", "age"],
"properties": {
"id": {
"type": "string",
"description": "UUID v4 identifier"
},
"email": {
"type": "string",
"format": "email"
},
"age": {
"type": "integer",
"minimum": 0,
"maximum": 150
},
"name": {
"type": "string",
"maxLength": 100
}
}
}
And here's JSON that validates against it:
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"email": "[email protected]",
"age": 28,
"name": "Alex"
}
This JSON would fail validation:
{
"id": 12345,
"age": "twenty-eight"
}
Two errors: id should be a string, age should be an integer (and email is missing entirely).
Core JSON Schema Keywords
type
The most fundamental constraint. Allowed values: string, number, integer, boolean, array, object, null.
{ "type": "string" }
{ "type": ["string", "null"] } // nullable field
required
An array of property names that must be present in the object.
{
"type": "object",
"required": ["username", "password"]
}
properties
Defines the schema for each named property.
String constraints
{
"type": "string",
"minLength": 8,
"maxLength": 64,
"pattern": "^[a-zA-Z0-9_]+$"
}
Number constraints
{
"type": "number",
"minimum": 0,
"maximum": 100,
"multipleOf": 0.01
}
Array constraints
{
"type": "array",
"items": { "type": "string" },
"minItems": 1,
"maxItems": 10,
"uniqueItems": true
}
enum
Restricts a field to a specific set of allowed values:
{
"type": "string",
"enum": ["draft", "published", "archived"]
}
Nested Objects
Schemas can describe deeply nested structures. Here's an order item:
{
"type": "object",
"required": ["orderId", "items", "total"],
"properties": {
"orderId": { "type": "string" },
"items": {
"type": "array",
"items": {
"type": "object",
"required": ["sku", "quantity"],
"properties": {
"sku": { "type": "string" },
"quantity": { "type": "integer", "minimum": 1 },
"price": { "type": "number", "minimum": 0 }
}
}
},
"total": { "type": "number", "minimum": 0 }
}
}
Schema Composition: allOf, anyOf, oneOf
JSON Schema lets you combine schemas:
allOf— the data must be valid against all listed schemas
anyOf— the data must be valid against at least one
oneOf— the data must be valid against exactly one
{
"oneOf": [
{ "type": "string", "maxLength": 5 },
{ "type": "number", "minimum": 0 }
]
}
This accepts either a short string or a non-negative number — but not both.
Where to Use JSON Schema
API validation — Validate request bodies before processing them. Libraries like ajv (Node.js) and jsonschema (Python) implement the full spec.
Configuration files — Many tools (VS Code, Prettier, ESLint) use JSON Schema to provide autocomplete and validation in config files.
Database documents — MongoDB supports JSON Schema validation natively in collection rules.
CI pipelines — Validate data files, API responses, or config changes as part of your build.
OpenAPI/Swagger — OpenAPI 3.x uses JSON Schema to describe request and response bodies. Understanding JSON Schema means understanding your API docs.
Validate JSON Against a Schema Right Now
Instead of setting up a library locally, you can paste your JSON and schema into the JSON Schema Validator on SnappyTools — it runs entirely in your browser using the ajv library (the most compliant validator available), supports JSON Schema draft-07 and 2020-12, and gives you line-by-line error messages.
Useful when you're:
- Debugging why a payload is failing validation
- Testing a schema you're writing for the first time
- Checking a third-party API response against expected structure
Quick Reference
| Keyword | Purpose |
|---|---|
type | Data type constraint |
required | Mandatory properties |
properties | Property schemas |
enum | Allowed values list |
minimum / maximum | Number range |
minLength / maxLength | String length |
pattern | Regex constraint on string |
items | Schema for array elements |
minItems / maxItems | Array length |
allOf / anyOf / oneOf | Schema composition |
$ref | Reference to another schema |
Conclusion
JSON Schema is one of those tools that feels like extra work until the first time it catches a production bug before it ships. A well-written schema documents your data structure, validates it automatically, and gives teammates a clear contract to code against.
Start with type and required, then add constraints as needed. Use the online validator to test as you go.
SnappyTools builds free, fast, browser-based tools for developers. No signup, no data uploaded.
SOCIAL SHARE CARD GENERATOR