QiLing Tools

🛎️OpenAPI & Swagger Viewer - Browse, Validate, Export API Docs

Got an openapi.yaml or swagger.json and don’t want to deploy Swagger UI just to read it? Paste the document or open a local file, and it’s turned into readable API docs right in your browser: title, version, description, servers and security schemes at the top; every endpoint grouped by tag on the left with colored method badges and search across paths, summaries, operationIds and tags; and the selected operation’s parameters, request body and responses on the right. Every $ref is resolved into a schema tree you can expand level by level, showing types, required fields, enums, ranges, readOnly and other constraints. Circular references are marked with “↻” instead of expanding forever, and example JSON is generated from each schema (request examples skip read-only fields). Swagger 2.0 body / formData parameters and definitions are converted to the same structure as OpenAPI 3. The Try it panel lets you choose a server, fill in parameters and tokens, and builds curl and fetch code as you type; after you opt in, it can also send the request straight from your browser (the API must allow CORS). Validation warnings flag unresolved references, missing or duplicate operationIds, paths that differ only by parameter name and mismatched path parameters. Finally, export a standalone static HTML page to share with your team. Your document is processed locally and never uploaded.

Free · No sign-up · Runs in your browserLast updated:

Loading tool...

How to use OpenAPI Viewer

  1. 1Paste OpenAPI / Swagger JSON or YAML, or open a local file (or click Sample spec to try it)
  2. 2Browse endpoints by tag or search, and inspect parameters, request bodies, response schemas and example JSON
  3. 3Build curl / fetch code in the Try it panel, or export static HTML docs

FAQ

How is this different from Swagger UI or Redoc?
It shows much the same information, but there’s nothing to deploy and nothing is uploaded to a third-party site — paste and read, all parsed locally in your browser. It also adds validation warnings and exports a script-free static HTML page you can email or drop into an internal wiki.
Are external file references ($ref: other.yaml#/...) supported?
No. To avoid making network requests, only references inside the same document (JSON Pointers starting with #) are resolved. External references are listed in the warnings; bundle multi-file specs first with swagger-cli bundle or redocly bundle and paste the result.
Why did “Send request” fail?
The request goes directly from your browser to the API — this site doesn’t proxy it. If the server doesn’t return CORS headers that allow this origin, the browser blocks the response and the request shows as failed. Copy the generated curl command and run it in a terminal instead; the result is the same.
How are recursive schemas displayed?
When, say, Category.parent points back to Category, the tree shows “↻ circular reference” at the point where the schema repeats and stops there, and the example JSON is cut off at the same place, so even deeply recursive models never hang the page.