OpenAPI Endpoint Explorer
Browse and explore all endpoints, parameters, and schemas in OpenAPI specifications
Enter an OpenAPI 3.x or Swagger 2.0 specification in JSON or YAML format
Type to filter endpoints by path, HTTP method, tag name, or summary
What is the OpenAPI Endpoint Explorer?
The OpenAPI Endpoint Explorer parses an OpenAPI 3.x or Swagger 2.0 specification and presents all endpoints in a browsable, structured format. You can inspect each endpoint's parameters, request bodies, response schemas, and metadata without needing to read through raw YAML or JSON. All processing happens in your browser — your API specifications never leave your device.
How to Use
- Paste your OpenAPI specification (JSON or YAML) in the input area
- Click "Explore Endpoints" or wait for automatic processing
- Review the statistics summary showing total endpoints, methods, and tags
- Browse individual endpoints with their parameters and schemas
- Use the filter field to search by path, method, tag, or summary text
Example: Exploring a Pet Store API
Consider a standard Pet Store API specification:
openapi: '3.0.3'
info:
title: Pet Store API
version: '1.0.0'
paths:
/pets:
get:
summary: List all pets
tags: [pets]
parameters:
- name: limit
in: query
required: false
schema:
type: integer
responses:
'200':
description: A list of pets
post:
summary: Create a pet
tags: [pets]
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
name:
type: string
tag:
type: string The explorer shows 2 endpoints (GET /pets, POST /pets), a method breakdown of 1 GET and 1 POST, the "pets" tag with 2 endpoints, and detailed parameter/schema information for each.
What Information Is Displayed?
- Statistics — Total endpoints, paths, methods breakdown, tags, parameters, and schemas
- Endpoint details — HTTP method, path, summary, description, operation ID
- Parameters — Name, location (path/query/header/cookie), type, required status
- Request body — Content types, schema structure, required status
- Responses — Status codes, descriptions, response schemas
- Tags — Tag names with endpoint counts and descriptions
Filtering and Search
The filter field lets you quickly find specific endpoints in large specifications. Type a path fragment like "/users", an HTTP method like "POST", a tag name, or part of a summary. The filter updates in real time, showing only matching endpoints.
Supported Formats
Both JSON and YAML formats are supported. The tool accepts OpenAPI 3.0, 3.1, and Swagger 2.0 specifications. Paste the full specification content directly — URLs are not supported.
Use Cases
- API onboarding — Quickly understand a new API's endpoints and structure
- Code review — Inspect OpenAPI spec changes in a readable format
- Documentation check — Verify all endpoints have proper descriptions and parameters
- Client development — Identify required parameters and response formats
- API audit — Review endpoint coverage, consistency, and deprecation status
Privacy and Security
All parsing and exploration happens entirely in your browser using JavaScript. Your API specifications — which may contain internal endpoints, authentication details, and business logic — never leave your device. No data is stored, logged, or transmitted.
Frequently Asked Questions
What OpenAPI formats are supported?
The tool supports OpenAPI 3.x and Swagger 2.0 specifications in both JSON and YAML formats. Paste the full spec content directly into the input area — the format is detected automatically.
What information does the Endpoint Explorer show for each endpoint?
For each endpoint, the tool displays the HTTP method, path, summary, description, operation ID, tags, deprecation status, all parameters (path, query, header, cookie) with their types and requirements, request body schemas, and response schemas for each status code.
Can I search or filter endpoints?
Yes. Use the search field to filter endpoints by path, HTTP method, summary text, or tag name. The filter updates in real time as you type, showing only matching endpoints.
Is my API specification sent to any server?
No. All parsing and exploration happens entirely in your browser using JavaScript. Your API specifications — which may contain internal endpoints, authentication details, and business logic — never leave your device. No data is stored, logged, or transmitted.
How does the tool handle large specifications?
The tool processes specifications up to 5MB. For specs larger than 500KB, a warning is shown that processing may be slow. All processing happens on the main thread since the explorer presents data without heavy computation.
What statistics does the tool provide?
The statistics section shows total endpoints, total paths, HTTP method breakdown (how many GET, POST, PUT, DELETE, etc.), total unique tags, total parameters across all endpoints, and total schemas defined in the specification.
How is this different from the OpenAPI Diff Analyzer?
The Endpoint Explorer parses a single specification and presents its contents in a browsable format. The Diff Analyzer compares two versions of a specification to detect changes between them. Use the Explorer to understand an API; use the Diff Analyzer to track API evolution.
Does the tool resolve $ref references?
The tool displays $ref references as-is, showing the reference path. Full inline resolution of deeply nested $ref chains is not performed to keep the display readable and avoid circular reference issues.