JSON Schema won API schemas by making validation a vocabulary

API tooling had a painful near-miss: OpenAPI used JSON-like schema objects, but they were not fully JSON Schema. Validators, code generators and documentation tools had to learn subtle differences, so the same API contract could mean different things in different stacks.

The elegant move was not to create another API-only language. JSON Schema made the schema itself a JSON media type, with vocabularies and meta-schemas that declare which keywords and behaviors are in play. OpenAPI 3.1 could then say: use JSON Schema draft 2020-12, not a lookalike.

The result was a standard that won by becoming the grammar beneath other standards. OpenAPI called its 3.1 release 100% compatible with the latest JSON Schema draft, while JSON Schema got a stable extension model for validation, code generation, UI and documentation.

Make schemas extensible vocabularies

The schema stayed ordinary JSON, so developers could read, diff and generate it with existing tools.

Vocabularies gave extensions names and boundaries instead of making every platform invent private keywords.

OpenAPI adoption pulled JSON Schema into API documentation, validation and code generation workflows at once.

Draft 2020-12 gave implementers a stable target, including dialects and meta-schemas.

A format spreads when extensions are first-class and testable, not hidden in prose or vendor conventions.

OpenAPI 3.1 shipped on February 18, 2021 with full JSON Schema draft 2020-12 compatibility. That made JSON Schema the shared contract layer for a large API tooling ecosystem rather than just a standalone validator format.