Read an OpenAPI document as endpoints, parameters, responses and security schemes, with unsupported features and unresolved references listed, not ignored.
Waiting for a document
OpenAPI 3 or Swagger 2, as YAML or JSON.
Waiting for a document
Paste an OpenAPI or Swagger document.
OpenAPI Inspector runs entirely on your device — nothing is uploaded, and no external reference is fetched.
You’re on the Free plan. Compare plans
An OpenAPI document is long, deeply nested and mostly not what you came to read. This turns one into the views people actually want: the endpoints, what each takes, what each returns, and how it is secured.
What it cannot interpret, it lists. XML mapping, callbacks, links, 3.1 webhooks and path-level `$ref`s each appear in an unsupported list with a note saying what was skipped. That is the difference between a tool you can trust and one that quietly shows you less than the document says.
Nothing is fetched, so an external `$ref` is reported as unresolved rather than followed. A document split across files has to be bundled before its full shape is visible here, and the tool says which references it could not follow rather than rendering an incomplete picture as a complete one.
Swagger 2.0 is read as far as the shapes overlap. The big moves are handled — `definitions` became `components.schemas`, body parameters became `requestBody`, `host` plus `basePath` became `servers` — and anything 2.0-specific beyond that is listed as unsupported rather than guessed at.
Both JSON and YAML are accepted, parsed with the project's own parsers, and no part of the document is sent anywhere.
No. Nothing is fetched, so a reference to another file or a URL is listed as unresolved. Bundle the document first if you need the whole shape in one view.
As far as the shapes overlap, and it says where they stop. The major renames are handled; anything 2.0-specific beyond them appears in the unsupported list rather than being guessed at.
It reports structural problems it finds while reading — missing required fields, references that go nowhere, duplicated operation ids. It is not a full specification validator, and it does not claim to be one.
3.0 and 3.1 fully, 2.0 partially. 3.1's JSON Schema alignment means some schema keywords behave differently from 3.0, and where that matters it is noted on the schema rather than glossed over.
No. It is parsed in your browser, which matters when the document names internal hosts, unreleased endpoints or your security schemes.