OpenAPI and JSON Schema fixtures

Petstore OpenAPI 3.1 (Valid JSON)

A valid OpenAPI 3.1 pet-store SAMPLE spec in JSON — list/create pets with paginated responses for schema-validator and codegen tests.

File: JSON · Schema
Use case: Schema / OpenAPI testingJSON parsing+1· Conversion set

Petstore OpenAPI 3.1 (Valid YAML)

YAML twin of the valid pet-store OpenAPI spec — for testing YAML spec parsers and JSON↔YAML conversion.

File: YAML · Schema
Use case: Schema / OpenAPI testingJSON parsing+1· Conversion set

Invalid OpenAPI — Openapi Missing Paths

OpenAPI document with paths set to null — intentionally invalid for negative schema tests.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling

Invalid OpenAPI — Openapi Broken Ref

OpenAPI with a response schema $ref pointing at a missing component — tests broken-reference detection.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling

Invalid OpenAPI — Openapi Wrong Version

OpenAPI with an unsupported openapi version string — negative case for version validators.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling

User JSON Schema (draft 2020-12)

Draft 2020-12 JSON Schema for a user object with email format and role enum — paired with valid/invalid instances.

File: JSON · Schema
Use case: Schema / OpenAPI testingJSON parsing· Conversion set

User Instance — Valid

JSON instance conforming to the Wave F user JSON Schema — positive validator test case.

File: JSON · Schema
Use case: Schema / OpenAPI testing· Paired fixture

User Instance — Invalid (5 violations)

User JSON deliberately violating the schema five ways — negative case for validator error reporting.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling· Paired fixture

Invoice JSON Schema

Draft-07 JSON Schema describing a SAMPLE invoice object for domain-specific validator tests.

File: JSON · Schema
Use case: Schema / OpenAPI testing

Event JSON Schema

Draft-07 JSON Schema describing a SAMPLE event object for domain-specific validator tests.

File: JSON · Schema
Use case: Schema / OpenAPI testing

Inventory Item JSON Schema

Draft-07 JSON Schema describing a SAMPLE inventory item object for domain-specific validator tests.

File: JSON · Schema
Use case: Schema / OpenAPI testing

Openapi Request Create Pet

Sample POST /pets request body matching the pet-store OpenAPI spec.

File: JSON · Schema
Use case: Schema / OpenAPI testingAPI testing

Openapi Response Pet Page

Sample paginated pet list response for mock-server and contract tests.

File: JSON · Schema
Use case: Schema / OpenAPI testingAPI testing

Openapi Response Not Found

Sample 404 problem response for OpenAPI error-handling tests.

File: JSON · Schema
Use case: Schema / OpenAPI testingAPI testing

Openapi Response Created

Sample 201 created pet response body for contract testing.

File: JSON · Schema
Use case: Schema / OpenAPI testingAPI testing

JSON Schema oneOf Union

JSON Schema with a oneOf union over string vs number tagged objects — for testing union validation.

File: JSON · Schema
Use case: Schema / OpenAPI testing

JSON Schema allOf Merge

JSON Schema allOf merging id and name requirements — tests composite schema validation.

File: JSON · Schema
Use case: Schema / OpenAPI testing

OpenAPI 3.1 Webhooks Section (YAML)

Minimal OpenAPI 3.1 document with a webhooks section — for testing webhook-aware spec parsers.

File: YAML · Schema
Use case: Schema / OpenAPI testingAPI testing

JSON Schema — Optional Properties without a Type Constraint

Omitting type is legal JSON Schema. The x property has an empty subschema, x is optional, and non-object instances are not rejected by properties.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling

Invalid JSON Schema — Json Schema Bad Ref

Intentionally invalid JSON Schema (json-schema-bad-ref) for negative validator tests.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling

JSON Schema — Empty Schema Accepts Any Instance

The empty schema is valid and accepts every instance. The old invalid label was incorrect; no type or required-property constraint exists.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling

Payment JSON Schema (draft-07)

Draft-07 JSON Schema for payment amount/currency validation in fintech API tests.

File: JSON · Schema
Use case: Schema / OpenAPI testing

Payment Instance — Valid

Valid payment JSON instance paired with the payment JSON Schema.

File: JSON · Schema
Use case: Schema / OpenAPI testing· Paired fixture

Payment Instance — Invalid

Invalid payment JSON (negative amount, short currency) for schema error reporting tests.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling· Paired fixture

OpenAPI Components-only Document (JSON)

OpenAPI document with empty paths but populated components — tests partial spec loaders.

File: JSON · Schema
Use case: Schema / OpenAPI testing

API Problem+JSON — Not Found (404)

RFC 7807 SAMPLE problem document for HTTP 404 (Not Found) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Unauthorized (401)

RFC 7807 SAMPLE problem document for HTTP 401 (Unauthorized) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Forbidden (403)

RFC 7807 SAMPLE problem document for HTTP 403 (Forbidden) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Conflict (409)

RFC 7807 SAMPLE problem document for HTTP 409 (Conflict) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Gone (410)

RFC 7807 SAMPLE problem document for HTTP 410 (Gone) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Too Many Requests (429)

RFC 7807 SAMPLE problem document for HTTP 429 (Too Many Requests) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Unprocessable Entity (422)

RFC 7807 SAMPLE problem document for HTTP 422 (Unprocessable Entity) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Bad Request (400)

RFC 7807 SAMPLE problem document for HTTP 400 (Bad Request) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Unsupported Media Type (415)

RFC 7807 SAMPLE problem document for HTTP 415 (Unsupported Media Type) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Not Acceptable (406)

RFC 7807 SAMPLE problem document for HTTP 406 (Not Acceptable) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Service Unavailable (503)

RFC 7807 SAMPLE problem document for HTTP 503 (Service Unavailable) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Internal Server Error (500)

RFC 7807 SAMPLE problem document for HTTP 500 (Internal Server Error) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

JSON Schema Edge — Additional Properties False

Minimal JSON Schema SAMPLE focusing on additional properties false constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — One Of Status

Minimal JSON Schema SAMPLE focusing on one of status constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Enum Currency

Minimal JSON Schema SAMPLE focusing on enum currency constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Pattern Sku

Minimal JSON Schema SAMPLE focusing on pattern sku constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Nullable Optional

Minimal JSON Schema SAMPLE focusing on nullable optional constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Array Unique Items

Minimal JSON Schema SAMPLE focusing on array unique items constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Dependent Required

Minimal JSON Schema SAMPLE focusing on dependent required constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Format Uri Email

Minimal JSON Schema SAMPLE focusing on format uri email constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Schema Evolution - Baseline

The baseline member of a JSON Schema 2020-12 customer contract. Reference contract: id and name are required strings.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

JSON Schema Schema Evolution - Backward-Compatible

The compatible member of a JSON Schema 2020-12 customer contract. Backward compatible: existing instances remain valid because email is optional.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

JSON Schema Schema Evolution - Breaking

The breaking member of a JSON Schema 2020-12 customer contract. Breaking relative to baseline: id changes from string to integer and tenantId becomes required.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

OpenAPI Schema Evolution - Baseline

The baseline member of a complete OpenAPI 3.1 ticket endpoint contract. Reference API: string ticket IDs and required id/summary response properties.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

OpenAPI Schema Evolution - Backward-Compatible

The compatible member of a complete OpenAPI 3.1 ticket endpoint contract. Backward compatible: an optional priority response property is added and existing operations stay unchanged.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

OpenAPI Schema Evolution - Breaking

The breaking member of a complete OpenAPI 3.1 ticket endpoint contract. Breaking relative to baseline: ticket id becomes integer and status becomes a required response property.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

Protocol Buffers Schema Evolution - Baseline

The baseline proto3 Customer message for field-number and wire-compatibility testing. Reference wire contract: field 1 is string id and field 2 is string name.

File: PROTO · Schema · 3 fields
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

Protocol Buffers Schema Evolution - Backward-Compatible

The compatible proto3 Customer message for field-number and wire-compatibility testing. Backward compatible: existing field numbers/types are retained and optional email uses new field number 3.

File: PROTO · Schema · 4 fields
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

Protocol Buffers Schema Evolution - Breaking

The breaking proto3 Customer message for field-number and wire-compatibility testing. Breaking relative to baseline: field number 2 is reused with a different name and wire type.

File: PROTO · Schema · 3 fields
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

Avro Schema Evolution - Baseline

The baseline Avro record schema for reader/writer compatibility tests. Reference writer schema: id and name are strings.

File: JSON · Schema · 2 fields
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

Avro Schema Evolution - Backward-Compatible

The compatible Avro record schema for reader/writer compatibility tests. Backward compatible for old records: nullable email is added with a null default.

File: JSON · Schema · 3 fields
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

Avro Schema Evolution - Breaking

The breaking Avro record schema for reader/writer compatibility tests. Breaking relative to baseline: id changes to long and tenantId has no default.

File: JSON · Schema · 3 fields
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

Convert v2 Protobuf Creator Record

Valid Protobuf wire record with string, uint32, and string fields for schema-guided decoding. Stable P8 artifact p8-convert-protobuf-source.

File: PB · P8 Convert · 3 fields
Use case: Conversion testingSerialization testing+1· Conversion set

Convert v2 Protobuf Schema Companion

Proto3 schema companion declaring the three fields used by the binary creator record. Stable P8 artifact p8-convert-protobuf-schema.

File: PROTO · P8 Convert · 3 fields
Use case: Conversion testingSerialization testing+1· Conversion set

Convert v2 Protobuf Expected JSON

Expected JSON semantic result for the schema-guided Protobuf decode. Stable P8 artifact p8-convert-protobuf-expected.

File: JSON · P8 Convert · 3 fields
Use case: Conversion testingSerialization testing+1· Conversion set

Convert v2 Protobuf Missing-Schema Controlled Failure

Valid wire bytes intentionally supplied without a matching schema so tools must preserve unknown field 15. Stable P8 artifact p8-convert-protobuf-missing-schema.