OpenAPI Validator
Find broken references, path parameters that do not match, duplicate operation ids and other mistakes in an OpenAPI spec, and check a real response against it.
How to check an OpenAPI spec
Paste your spec
Paste an OpenAPI 3 or Swagger 2.0 file in YAML or JSON, or press Try an example.
Read the problems
Errors break tools that read the spec; warnings are good practice.
Optionally check a response
Paste a real response body, name the operation and status code, and see where it differs from the schema.
When to use OpenAPI Validator
A code generator, API gateway or docs tool refuses your spec and you need to find which part is wrong.
An API returns data that the front end cannot handle and you want proof of whether the response or the spec is at fault.
Tips for a better OpenAPI Validator result
Fix the errors before the warnings: broken references and mismatched path parameters stop tools from working, warnings do not.
For the response check, write the operation exactly as the table shows it, such as GET /pets/{petId}, and the status code as a number.
OpenAPI Validator: limits and what to check
Style rules such as naming conventions are not checked, so keep a linter like Spectral in your build for those.
A response that matches the schema can still be wrong in meaning, such as a total that does not add up, so test the values too.
About OpenAPI Validator
Find the mistakes that stop code generators, docs and gateways from reading a spec: references to schemas that do not exist, path parameters that are declared but not in the path (or the other way round), duplicate operation ids, invalid response codes and missing descriptions. A response check compares real JSON with the schema, including nullable fields.
FAQs
Is this a full OpenAPI schema validation?
It checks the structure and the mistakes that cause real trouble. For every last rule of the specification, also run a linter such as Spectral or Redocly in your build.
Why is a missing operationId a warning?
The spec allows it, but code generators then invent method names, which change when paths change.
How does the response check treat nullable?
A field marked nullable: true accepts null as well as its type, the way OpenAPI 3.0 defines it.