OpenAPI / Swagger Explainer

How it works

The spec you paste is parsed with the js-yaml library (which also handles plain JSON, since JSON is valid YAML) directly in your browser; it then walks the resulting paths object for each of the seven standard HTTP methods (get, post, put, patch, delete, options, head) and pulls each operation's summary or description and parameter list into one flat, scannable list.

FAQ

Does it work with Swagger 2.0, not just OpenAPI 3.x?

Yes - both formats share the same paths/methods/parameters structure this tool reads, so a Swagger 2.0 document parses the same way an OpenAPI 3.x one does.

What if my spec uses $ref to reference shared parameters or schemas?

They won't be resolved - this tool reads the paths object as-is and doesn't follow $ref pointers, so referenced parameters may show up incomplete or missing from the list.