Skip to content
TextArray1.41.0
100% local

OpenAPI endpoint lister

List every endpoint from an OpenAPI or Swagger document as a readable table.

Input
Output
Related tools
JSONPath extractorDeveloper tools
YAML ⇄ JSON converterDeveloper tools
HTTP status code lookupDeveloper tools
i18n key diffDeveloper tools
TOML to JSON converterDeveloper tools
SQL to JSONDeveloper tools
OpenAPI endpoint lister
Paste an OpenAPI or Swagger document — JSON or YAML, OpenAPI 3 or Swagger 2 — and this tool extracts every endpoint into a readable list. It is built for the moment you get handed a spec file and need a quick overview before diving into the details: which routes exist, what they need, and what they return.
Filter the list by HTTP method or by tag to focus on one part of the API. Toggle path and query parameters, the request body's content type, response codes and whether an endpoint requires authentication — the tool reads security requirements per operation, falling back to the document's global security when an operation doesn't override it. Turn on "Skip deprecated endpoints" to hide routes marked deprecated in the spec, and include each endpoint's summary field for extra context without opening the source file.
Sort the result by path or by tag, and choose an output format to match what you need next: a plain list for a quick scan, a Markdown table to paste into documentation or a pull request, or CSV to open in a spreadsheet. Parameters that are defined with $ref rather than inline are skipped rather than guessed at, since resolving a reference correctly needs the rest of the document.
Everything runs locally in your browser — the API specification never leaves your device, which matters when it describes an internal or unreleased service. Copy the result, download it as a .txt file, or send it straight into another tool to keep working.
FAQ
Does it support both OpenAPI 3 and Swagger 2?
Yes. Both formats keep endpoints under a "paths" section with the same shape, so the same reader handles either version.
How does it decide whether an endpoint needs authentication?
It checks the operation's own "security" field first. An empty array there means that endpoint explicitly disables auth; if the field is missing, the tool falls back to the document's global "security" setting.
Can it resolve $ref references?
Not for parameters — a parameter defined with $ref has no inline name, so it is skipped rather than resolved, since that would require reading the rest of the document.
What happens with an invalid or unrelated document?
You'll see a clear message: one for text that isn't valid JSON or YAML, and another when the document parses fine but has no "paths" section.
Is my API specification uploaded anywhere?
No. Parsing and formatting happen entirely in your browser — the document you paste never leaves your device.