not JSON Schema Keyword JSON Schema

Composition

Schema template

JSON Schema

{
  "not": {
    "enum": [
      "root",
      "admin"
    ]
  }
}

Valid example JSON

"editor"

Invalid example JSON

"admin"

Fields

Field	Type	Required	Description
`not`	schema	Yes	The value is valid only when the nested schema does not match.

How to use this schema

Use not sparingly. It is useful for excluding known bad cases, but positive constraints usually produce clearer validation errors.

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.

not JSON Schema Keyword