OpenAPI Spec Viewer
Paste an OpenAPI 3 or Swagger 2 spec in YAML or JSON to list every operation with its parameters, body types and responses, and catch the mistakes that break code generators.
Free · No sign-up · Your inputs stay in your browser
Input
View and check an OpenAPI spec
Output
4 operations
| Title | Orders API |
|---|---|
| Version | 2.3.0 |
| Spec | 3.1.0 |
| Servers | https://api.example.com/v2 |
| Schemas | Order |
| Method | Path | Summary | Parameters | Body | Responses |
|---|---|---|---|---|---|
| GET | /orders | List orders | status (query), page (query) | - | 200 |
| POST | /orders | Create an order | - | application/json | 201 422 |
| GET | /orders/{id} | Get one order | id* (path) | - | 200 404 |
| DELETE | /orders/{id} | deleteOrder | - | - | 204 |
GET /orders/{id} has no operationId, so generated clients name it themselves. DELETE /orders/{id} does not declare the path parameter {id}.
Markdown summary
# Orders API 2.3.0 Server: `https://api.example.com/v2` | Method | Path | Summary | | --- | --- | --- | | GET | `/orders` | List orders | | POST | `/orders` | Create an order | | GET | `/orders/{id}` | Get one order | | DELETE | `/orders/{id}` | deleteOrder |
Lists every operation with its parameters (* marks required), request body types and response codes, and flags what breaks code generators: missing or duplicate operationIds, undeclared path parameters, operations without responses. Full schema validation needs the official JSON Schema for your OpenAPI version.
Runs in this browser. Nothing you paste is sent to a server.
About this tool
Method, assumptions, practical next steps, and limits.
Problems generators trip on
Client generators name methods after operationId, so a missing one produces names like getUsersIdPosts and a duplicate one produces a compile error. A path parameter that is not declared breaks request building. These are quick to fix in the spec and painful to work around in generated code. The OpenAPI 3.1 specification defines each object.
Rendering docs
Swagger UI, Redoc and Scalar render interactive documentation from the same file; Spectral lints it against style rules in CI.