All tools

OpenAPI Validator

Validate OpenAPI and Swagger specs for structural errors, missing responses, and dead schemas.

0 errors2 warningsOpenAPI 3.0.3

warning · POST /users

Missing operationId. SDK generators and test reports rely on it.

warning · components.schemas.User

Schema "User" is never $ref'd. Dead schemas rot — delete it or wire it up.

What is the OpenAPI Validator?

The OpenAPI Validator checks your OpenAPI 3.x or Swagger 2.0 document for structural errors and contract smells: missing version fields, empty paths, operations without responses, missing operationIds, and dead schemas. Paste JSON or YAML and get a report you can paste straight into a PR review.

How to use it

Paste your openapi.json or openapi.yaml into the editor — validation runs live as you type. Errors break consumers and must be fixed; warnings are contract smells worth discussing. Use Copy report to share the full findings with your team.

Use cases

Contract testing prep: catch spec errors before they become Pact or consumer-driven test failures. API reviews: attach a validator report to every spec PR. SDK generation: missing operationIds and responses are the top reason generated clients come out wrong. QA handoff: confirm every endpoint documents a success response before writing test cases.

Related tools

Pair with the API Testing Checklist to turn a valid spec into test coverage, the JSON Formatter to inspect payloads, and the cURL Builder or Postman to cURL tools to exercise the endpoints you just validated.