Inspect a JSON Schema
Paste a JSON Schema and see its structure clearly — which properties exist, their types, which are required, and how nested objects fit together — instead of tracing the raw document.
Open the tool, then paste the sample input below. Everything runs locally in your browser.
The problem
A JSON Schema is itself nested JSON, so understanding what an API actually requires means tracing required arrays and property types by hand. Inspecting it as a structured view shows the fields, their types, and which are mandatory at a glance.
Sample input
{
"type": "object",
"required": ["id", "email"],
"properties": {
"id": { "type": "integer" },
"email": { "type": "string" },
"active": { "type": "boolean" }
}
}Expected output
object
id integer (required)
email string (required)
active booleanid and email are in the required array, so they are marked required; active is optional. The types come from each property's type keyword.
How to do it
- Paste the JSON Schema.
- View the property list and their types.
- Check which properties are required.
- Expand nested objects and arrays.
- Use the structure to build or validate a payload.
Common mistakes
- Assuming a property is required when it is only listed under properties.
- Ignoring the required array, which is what makes a field mandatory.
- Missing nested required arrays inside sub-objects.
- Confusing a schema with an example payload.
- Overlooking additionalProperties, which controls extra keys.
Related tools
Related guides
FAQ
How do I tell which fields a JSON Schema requires?
Required fields are listed in the schema's required array, not just under properties. A property defined under properties is only mandatory if its name also appears in required.
Where do property types come from?
Each property has a type keyword such as string, integer, or boolean. Inspecting the schema surfaces these next to each property name.
How are nested objects shown?
An object property has its own properties and required array. The inspector lets you expand it to see the nested fields and which of them are required.
What is the difference between a schema and an example?
A schema describes the allowed shape and types; an example is one concrete payload. The inspector reads the schema, not a sample document.
Is my schema uploaded?
No. Inspection runs locally in your browser. Your schema is not sent to a server.
Schema inspection runs locally in your browser. Nothing is uploaded.
Inspect and validate schemas, query and format JSON, and work with API contracts — grouped in one place.