OpenAPI Viewer

How to use it

1. Paste a spec into the left panel — JSON or YAML, both are accepted.
2. Click Parse spec. The right panel fills with a summary: title, version, servers, then every path.
3. Each operation line shows the method, path, summary, parameters with their location and required flag, the request body content type, and response codes with a one-level schema type summary.
4. If the document is invalid, the error line says exactly which field is missing or what failed to parse.
5. Copy or download the summary for a ticket, a review or a README.

Common use cases

• Reviewing a spec before implementing — read every endpoint, its inputs and its responses without opening an editor.
• Sharing an API overview — paste the summary into a chat or ticket instead of the whole document.
• Checking a generated spec — confirm that paths, parameters and response codes came out the way you expected.
• Learning the OpenAPI shape — see how info, servers, paths and components fit together on a real example.

Why it stays private

The document is parsed in your browser with js-yaml. Nothing is uploaded, and no request is ever made to the servers listed inside the spec — the tool only reads the text you paste.

FAQ

Q: Which spec versions are supported? A: OpenAPI 3.x and Swagger 2.0. The version field is required, and the error message says so when it is missing.

Q: How deep does the schema summary go? A: One level. Object properties are listed by name with their types, and nested objects appear as a reference name or a short type note. It is a map of the API, not a full schema browser.

Q: What happens with $ref pointers? A: They are shown by their target name, for example ref:Book. The tool does not resolve them against components, because the summary stays readable that way.

Q: My YAML fails to parse — why? A: The error line includes the js-yaml message, which usually points at the offending line. Tabs in indentation and unclosed quotes are the common causes.