OpenAPI Viewer & Structural Validator
Inspect OpenAPI JSON or YAML, browse endpoints and find core structural or local-reference errors.
About the OpenAPI Viewer & Structural Validator
Open a UTF-8 OpenAPI 3.0.x or 3.1.x document in JSON or YAML and browse its declared path operations. Filter by method, path, summary, operation ID or tag, then expand an endpoint to inspect parameters, request-body presence and responses. Descriptions are displayed as text, not executable HTML.
Structural checks cover required API information, path shapes, operation IDs, path parameters, response declarations and supported local references. Local path-item, parameter, request-body and response references are expanded. Schema references are checked in supported schema locations, while external references are reported and never fetched.
This is a focused inspector, not complete OpenAPI or JSON Schema conformance certification. Schema keywords, security flows, examples and server behavior are not fully validated. Callback and webhook operations are not listed. Swagger 2 and OpenAPI versions other than 3.0 or 3.1 are rejected. Limits are 5 MiB, 100,000 values, 10 million expanded text characters, 64 levels, 5,000 operations and bounded expanded inspection.
Key features
- JSON and YAML input
- Core structural findings with document locations
- Local reference inspection without network access
- Endpoint filtering and 25-operation pagination
- Parameter and response inspection
- Plain-text descriptions and explicit validation scope
How to use
- 1Open a JSON/YAML file or paste an OpenAPI 3.0 or 3.1 specification.
- 2Run inspection and read structural errors and warnings.
- 3Filter endpoints by method or search terms, then expand an operation.
- 4Use an official schema validator and integration tests for complete conformance and runtime behavior.
Examples
OpenAPI 3.1 with GET /items/{id}, an ID parameter and 200/404 responsesA browsable endpoint and core structural findings.Frequently asked questions
- Will it contact the servers in my specification?
- No. Specifications stay in your browser. Declared servers are shown as text and no API requests or external-reference fetches are made.
- Does zero structural errors prove the API is valid?
- No. Only the stated checks are performed. Complete schema conformance, authorization flows and actual server behavior need separate validation and tests.
- Are YAML aliases supported?
- Acyclic JSON-compatible aliases are allowed within document-complexity limits. Cyclic YAML object graphs are rejected; recursive OpenAPI $ref strings are a separate feature and supported schema references are not recursively expanded.
Continue your workflow
Open a related tool to prepare your files or refine the finished result.
- Featured toolDeveloper ToolsYAML Formatter & Validator
Format and validate YAML, and catch syntax errors.
Open tool - Featured toolDeveloper ToolsJSON Formatter
Format, validate and minify JSON instantly.
Open tool - Developer ToolsHAR Network Analyzer
Analyze HAR requests, timings, HTTP errors and known transfer sizes locally with URL-value redaction.
Open tool
