OpenAPI/Swagger Editor
NewEdit and validate OpenAPI specs with a live path/method summary and prettify tool.
Basic structural checks for OpenAPI 3.x documents.
No parsed document yet.
Frequently Asked Questions
Why does my YAML spec show a parse error here?
Because this editor only parses and validates JSON in-browser right now. It even detects YAML-looking input and shows a specific message telling you to paste JSON instead.
Does "Valid structure" mean my whole OpenAPI document is fully valid?
No. The checks are deliberately basic. This tool confirms the document is a JSON object with openapi, info.title, info.version, and a non-empty paths object that actually contains HTTP operations.
What does the Format / Prettify button do?
It re-parses the current JSON and writes it back as pretty-printed JSON with two-space indentation. It does not convert YAML to JSON, and it will refuse to run if the current input is not valid JSON.
Why does the summary say "No operationId" for some endpoints?
The editor still recognizes the HTTP method and path, but it simply reports when an operation object has no operationId field. That is a summary hint, not a parse failure by itself.
Does it validate responses, schemas, and components deeply?
No. Those parts are not deeply inspected here. The right-hand side is a structural sanity check plus a live path and method summary.