What this tool does
Paste, upload, or load an example OpenAPI (3.x) or Swagger (2.0) document — JSON or YAML — and browse it as a readable list of endpoints instead of a wall of nested JSON. Pick an endpoint to see its parameters, request body, and response schemas broken out into a readable tree, with $ref references resolved automatically.
What gets parsed
- Info and servers. Title, version, description, and the base URL(s) the API is served from.
- Every operation under every path — grouped by tag, with method, summary, description, and
operationId. - Parameters, grouped by location (path, query, header, cookie), each with its type and whether it's required.
- Request and response bodies, rendered as a property tree — objects expand into their properties, arrays show their item type, and enums list their allowed values.
Both OpenAPI 3.x's requestBody.content shape and Swagger 2.0's in: body parameter style are supported, since a lot of specs still in active use are written against the older format.
How $ref resolution works
OpenAPI documents reuse schemas by reference — {"$ref": "#/components/schemas/Pet"} — rather than repeating the same object shape everywhere. This tool follows those references automatically as it builds the property tree, including references nested inside other references. If a schema references itself (directly or through a chain of other schemas), that's detected and shown as a circular reference instead of recursing forever.
FAQ
Does this call the API?
No — this is a read-only document viewer. It doesn't send any requests to the servers listed in the spec, so there's no "Try it out" execution step.
Is my spec uploaded anywhere?
No — parsing happens entirely in your browser, whether you paste it, type it, or upload a file. Nothing is sent to a server.
What if my spec doesn't have tags?
Endpoints without a tag are grouped under "Other" in the sidebar.