required JSON Schema Keyword JSON Schema

Object

Schema template

JSON Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    },
    "name": {
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}

Valid example JSON

{
  "id": "item_1"
}

Invalid example JSON

{
  "name": "Missing id"
}

Fields

Field	Type	Required	Description
`required`	string[]	Yes	Lists property names that must exist on the object. It does not define their type; use properties for that.

How to use this schema

Use required for identifiers, required form fields, and API contract fields that clients must send. Keep optional fields out of the list.

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.

required JSON Schema Keyword