Validate OpenAPI specs and inspect every endpoint.
Paste or drop YAML or JSON OpenAPI 3.0/3.1 and Swagger 2.0 contracts to catch broken $ref pointers, duplicate operationIds, and missing path parameters—with interactive schema cards and instant cURL snippets.
StatusValid Spec
Spec VersionOAI 3.1.0
Quality Score100/100
Endpoints2
Schemas1
OpenAPI / Swagger Contract
100% client-side OAI 3.x & $ref linter
Contract InspectorDetected YAML
Ready. Paste an OpenAPI 3.0, 3.1, or Swagger 2.0 contract in YAML or JSON—or drop a file.
Sujon Edge APIv1.4.0
Client-side developer tool metadata and configuration validation endpoints.
https://sujon-dev-tools.pages.dev
List all client-side developer toolslistTools
Validate a tool configuration payloadvalidateToolConfig
THE DETAILS
OpenAPI 3.1 contract validation, $ref linting, and SDK readiness.
1. Drop, Lint & Inspect in Seconds
Paste or drag-and-drop any OpenAPI 3.0, OpenAPI 3.1, or Swagger 2.0 file in YAML or JSON. The inspector scores contract completeness, highlights structural errors with exact JSON paths, and lets you filter endpoints by HTTP method or keyword.
2. Deep Structural & $ref Pointer Checks
Beyond root openapi/swagger and info checks, the validator verifies every internal #/... JSON Pointer resolves to a real component, detects duplicate operationId values, and checks that every {param} in a path is declared as an in: path parameter.
3. Schema Models & Instant cURL Prototyping
Expand any operation to inspect parameters, request body MIME types, and response status descriptions—then copy a ready-to-run cURL command pre-filled with the first server URL. Switch to the Schemas tab to inspect properties and required fields at a glance.
4. Zero-Upload Privacy & Companion Tools
Internal microservices, unreleased endpoints, and proprietary models never leave your browser tab. Need to convert raw configs, generate TypeScript interfaces from a JSON payload, or translate cURL into fetch/Python? Try the YAML ↔ TOML ↔ JSON converter, JSON to TypeScript generator, and cURL to code converter.
OpenAPI 3.0 vs. OpenAPI 3.1 & CLI Linter Matrix
Specification Aspect
OpenAPI 3.0.x
OpenAPI 3.1.0
JSON Schema Dialect
Modified Draft 4/5 subset
Full JSON Schema Draft 2020-12
Nullable Properties
type: string, nullable: true
type: ["string", "null"]
Numeric HTTP Status Keys
Quoted strings ("200":)
Quoted strings ("200":)
CLI Linter Equivalent
swagger-cli validate openapi.yaml
spectral lint openapi.yaml
Common OpenAPI Pitfalls & Troubleshooting
Unquoted Numeric Status Codes in YAML
OpenAPI requires response status codes under responses to be string keys ("200", "404"). Always wrap numeric HTTP status codes in quotes inside YAML specifications.
Broken Internal $ref Pointers
Renaming a model in components.schemas without updating its $ref: "#/components/schemas/..." breaks SDK generation silently in some editors. Check the Diagnostics tab to catch unresolved pointers immediately.
Undeclared Path Template Parameters
If a route path contains /pets/{id}, every operation on that path (or the path item itself) should declare a matching parameter with name: id and in: path.
Duplicate operationId Collisions
Reusing the same operationId across two routes causes TypeScript, Go, and Python code generators to overwrite methods or fail builds. Keep every operationId globally unique.
Frequently Asked Questions
Can I validate internal or unpublished microservice OpenAPI specs privately?
Yes. All YAML and JSON contract parsing, $ref pointer resolution, and endpoint previewing execute 100% locally in your browser memory. Zero API paths, schemas, or server URLs ever leave your device.
Does this validator accept both YAML and JSON OpenAPI files?
Yes. Paste or drag-and-drop either YAML or JSON specs. You can convert directly between normalized YAML and canonical 2-space indented JSON in one click.
What is the difference between OpenAPI 3.0 and OpenAPI 3.1?
OpenAPI 3.1 aligns 100% with JSON Schema Draft 2020-12—replacing the custom nullable: true keyword from OpenAPI 3.0 with standard JSON Schema type arrays such as type: ["string", "null"] and supporting webhooks as a top-level object.
Why does the validator warn when an endpoint is missing an operationId?
Code generators (such as openapi-typescript, Orval, and OpenAPI Generator) use operationId as the generated function or hook name. Omitting or duplicating operationId causes brittle or colliding client SDK methods.
Does it check for broken $ref pointers and missing path parameters?
Yes. The linter walks every internal #/... JSON Pointer reference to confirm the target schema or component exists, and flags URL template parameters like {id} that lack a matching in: path parameter definition.