OpenAPI Structural Validator

Paste an OpenAPI 3 or Swagger 2 document in JSON or YAML and get a list of errors and warnings about its structure, parameters, responses and references.

Use the tool

Why this tool exists

A spec with a missing description, a path parameter that is not declared or two operations sharing an operationId may look fine in an editor and then break code generation, mock servers or documentation builds. These errors are tedious to find by reading a long file.

This validator runs the structural checks that catch most mistakes: required info fields, response codes and descriptions, path template variables versus declared parameters, required true on path parameters, duplicate operationIds and $refs that point nowhere. It also warns about unused schemas and missing summaries. It does not validate against the full OpenAPI meta-schema, so run a dedicated linter such as Spectral for style rules.

How to use it

  1. Paste your OpenAPI or Swagger document, in JSON or YAML.
  2. Read the error and warning counts followed by each finding.
  3. Fix the spec and run it again until it reports no errors.

Frequently asked questions

Is this a full OpenAPI validation?

No. It checks a defined set of structural rules, and says so in its output. A document can pass here and still fail the official meta-schema or a strict linter.

What does a path parameter error mean?

Either the path contains something like {id} that is not declared in parameters, a declared path parameter is not in the path, or it lacks required: true, which is mandatory for path parameters.

Does it resolve external $refs?

No. Only references starting with a hash and pointing inside the same document are checked. External file or URL references are not followed.

Which versions are accepted?

OpenAPI 3.0 and 3.1, and Swagger 2.0. An unusual version string produces a warning rather than an error.