json2.5 KB

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.

Schema / OpenAPI testing JSON parsing API testing

Preview, first 50 linesjson

{
  "openapi": "3.1.0",
  "info": {
    "title": "Novus Petstore SAMPLE API",
    "version": "1.0.0",
    "description": "Tiny OpenAPI fixture for Wave F schema testing."
  },
  "paths": {
    "/pets": {
      "get": {
        "operationId": "listPets",
        "responses": {
          "200": {
            "description": "OK",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/PetPage"
                }
              }
            }
          }
        }
      },
      "post": {
        "operationId": "createPet",
        "requestBody": {
          "required": true,
          "content": {
            "application/json": {
              "schema": {
                "$ref": "#/components/schemas/PetCreate"
              }
            }
          }
        },
        "responses": {
          "201": {
            "description": "Created"
          }
        }
      }
    },
    "/pets/{petId}": {
      "get": {
        "parameters": [
          {
            "name": "petId",
            "in": "path",
            "required": true,

… 120 lines total: download for the full file.

Specifications

Format: OpenAPI 3.1
Paths: 2
Schemas: 3
Valid: true
Seed: 42042

Testing contract

Expected to pass

Scenario: Exercise Petstore OpenAPI 3.1 (Valid JSON) in its schema workflow. A valid OpenAPI 3.1 pet-store SAMPLE spec in JSON — list/create pets with paginated responses for schema-validator and codegen tests.
Expected result: top-level keys are openapi, info, paths, components; selected values: {"openapi": "3.1.0"}. Declared feature checks: paths=2; schemas=3; valid=True.

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“Petstore OpenAPI 3.1 (Valid JSON)” is a deterministic Novus Examples fixture for Schema / OpenAPI testing, JSON parsing, API testing. Valid and intentionally invalid OpenAPI/JSON Schema documents plus request/response examples for schema validators and API tooling.

Documented properties for this file: seed 42042 · OpenAPI 3.1. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Valid and intentionally invalid siblings are labelled in title and description. Assert parsers accept the valid twin and fail loudly on the invalid one; for time series, check DST gaps and duplicate keys against the spec table.

Code examples

import json

with open("petstore-openapi.json") as f:
    data = json.load(f)
print(type(data), len(data))

Generated by generation/data_wave_f.py. Free for any use, no attribution required, license.