OpenAPI validator
Paste an OpenAPI 3 JSON document and check its structure before you publish API docs.
What this checks
openapi version, info.title/version, paths object, operations (summary, responses), and basic component refs. For full linting use Spectral in CI; this tool is a fast first pass.
What an OpenAPI validator checks
Structure before publishing
API references built from an OpenAPI file break quietly when the file is malformed: missing paths, operations without responses, or references to components that don't exist. Checking the structure first saves a confusing docs build.
What this validator looks at
It checks the OpenAPI version, the info block, paths and their operations, response objects, and component references in the JSON you paste. It runs in your browser.
Keeping API docs current
A valid spec can still describe last month's API. Regenerate the reference when endpoints change, and keep error codes and examples in step with the code.
FAQ
Which OpenAPI versions does it support?
OpenAPI 3.x documents in JSON.
Is my spec uploaded anywhere?
No. Validation runs in your browser.
Does a valid spec mean my API docs are correct?
No. Validation checks structure; it can't tell whether the spec matches what your API does today.
API docs drift fastest. usedocs imports OpenAPI files as articles and proposes edits when merged pull requests change what they describe.
Start a 7 day free trial