Feature

Strict OpenAPI 3 validation, with errors you can act on

A documentation tool that silently accepts a broken spec is worse than no tool at all. Apidex refuses to ship docs from a spec that won't parse, and tells you exactly where the problem is.

Validation that respects your time

When you upload an OpenAPI 3 file, apidex parses it strictly — version, info block, paths, parameters, responses, schemas, security schemes, the whole tree. If something is off, you see a focused list of issues with the path that triggered each one, so you can fix and re-upload in seconds.

What we check

Structural integrity

OpenAPI version, info block, paths object — the basics that have to be right for anything else to make sense.

References resolve

Every $ref points somewhere real. Broken references are caught before they become broken docs.

Schemas are coherent

Required fields, types, and nested objects are validated so the playground knows what to send.

Security schemes match

Auth references on operations actually map to defined security schemes — no silent mismatches.

JSON or YAML, you choose

apidex accepts both formats and detects which one you uploaded automatically. Pasting works too, for those moments when you just want to drop a snippet from another tool.

Validate a spec nowExplore other features