Schema template
JSON Schema
{
"type": "object",
"properties": {
"id": {
"type": "string"
},
"active": {
"type": "boolean"
}
},
"required": [
"id"
]
}Valid example JSON
{
"id": "user_1",
"active": true
}Invalid example JSON
{
"id": 123,
"active": true
}Fields
| Field | Type | Required | Description |
|---|---|---|---|
properties | object | Yes | Maps property names to schemas. Properties not listed here are allowed unless additionalProperties restricts them. |
How to use this schema
Use properties for API request bodies, responses, settings files, and structured event payloads. Pair it with required for fields that must always be present.
Version support and combinations
This keyword or pattern is commonly supported across modern JSON Schema workflows. Check your validator for Draft-04, Draft-07, 2019-09, and 2020-12 behavior before relying on newer composition or conditional features.
Common combination: pair this reference with type, required, and properties so validation errors are specific enough for API clients and form users.
Batch validation seed
Want to validate JSON Schema in bulk? Toolumina Pro can grow into batch validation for 100+ files, saved schemas, and repeatable API contract checks.