Developer Tools
Turn an OpenAPI spec or Postman collection into API docs
Paste or upload an OpenAPI spec, Postman collection or HAR file. You get readable docs grouped by tag as Markdown or HTML, or PDF via your browser’s print dialog.
or drop it here
- OpenAPI 3.x, Postman, HAR supported
- Markdown, HTML or PDF export
petstore-api.yaml 12 KB Format: OpenAPI 3.0.3 Endpoints: 14 Tags: Pets, Store, Users Auth: OAuth2 + API key
API Reference: Petstore API v1.0.0
Authentication
OAuth2 (implicit): /oauth/authorize
API Key: X-API-Key header
Pets (5 endpoints)
GET /pets List all pets
POST /pets Create a pet
GET /pets/{id} Get pet by ID
PUT /pets/{id} Update a pet
DELETE /pets/{id} Delete a pet
Example: GET /pets/{id}
curl -H "X-API-Key: ..." \
https://api.example.com/pets/42
200 Response:
{ "id": 42, "name": "Max",
"status": "available" }
Error Codes
400 Bad Request — invalid parameters
401 Unauthorized — missing or invalid key
404 Not Found — resource does not exist
429 Rate Limited — retry after header
Export: Markdown + HTML + PDF (12 pages)One clear job, from upload to export
- 1
Upload your API spec or collection
Drop an OpenAPI 3.x file (JSON or YAML), a Postman collection export, or a HAR file from your browser dev tools. Swagger 2.0 files are automatically converted. The tool parses endpoints, schemas, authentication methods, and example values.
- 2
Review generated documentation structure
Endpoints are grouped by tag with request parameters, response schemas, and code examples in cURL, Python, JavaScript, and Go. Authentication flows, error code tables, and data model references are generated automatically from your spec.
- 3
Export as Markdown, HTML or PDF
Download the documentation in the format that fits your workflow. Markdown integrates into GitBook, Docusaurus, or any docs platform. HTML is self-contained and ready to host. PDF is formatted for sharing with stakeholders or external partners.
From an API spec file to documentation you can share
What you can load
You upload or paste an OpenAPI 3.0 or 3.1 spec in JSON or YAML, a Postman collection in v2.0 or v2.1, or a HAR file from your browser's developer tools. Swagger 2.0 files are converted to OpenAPI 3.0 first. The tool runs in your browser, with no account and no job limit. If you load several spec files, each one gets its own documentation set.
What the docs contain
Endpoints are grouped by tag, with parameters, response schemas, authentication and error codes. Each endpoint gets request examples in cURL, Python, JavaScript and Go. Where your spec has example values, those are used. You export Markdown, a self-contained HTML file, or a PDF through the browser's print dialog. If your spec is sparse, the output shows where descriptions are missing, so read it before you publish.
Formats, styling and your spec
Pick the format by where the docs will live. Markdown fits GitBook, Docusaurus, MkDocs and similar platforms. The HTML output uses a neutral stylesheet that you can replace with your own. Custom logos, colors and headers are not supported yet. A Postman collection or HAR file may not cover every endpoint. The docs are only as accurate as the source, so regenerate them whenever the spec changes.
Questions before you run it
Which API spec formats are supported?
The tool accepts OpenAPI 3.0 and 3.1 specs in JSON or YAML, Postman Collection v2.0 and v2.1 exports, and HAR (HTTP Archive) files recorded from browser dev tools or proxy tools. Swagger 2.0 files are automatically converted to OpenAPI 3.0 before processing.
Does it support older OpenAPI and Swagger versions?
Swagger 2.0 specs are automatically upgraded to OpenAPI 3.0 during import. OpenAPI 3.0 and 3.1 are both fully supported. If your spec uses custom extensions (x- prefixed fields), those are preserved in the output as additional notes where relevant.
Are code examples included in the generated docs?
Yes. The generator produces request examples in cURL, Python (requests), JavaScript (fetch), and Go (net/http) for each endpoint. Response examples are derived from the schema definitions in your spec, including nested objects, arrays, and enum values. If your spec includes example values, those are used instead of generated placeholders.
Can I apply custom branding to the output?
The HTML output includes a neutral stylesheet that you can replace with your own. The Markdown output is plain and integrates into any documentation platform (GitBook, Docusaurus, MkDocs, Notion, Confluence). The PDF output uses clean typography suitable for sharing directly. Custom logos, colors, and headers are not yet supported in the generated output.
Can I generate docs for multiple APIs in one batch?
Yes. Upload multiple spec files and the tool generates a separate documentation set for each. Each set is packaged in the output archive with its own folder. Batch generation is useful for microservice architectures where each service has its own spec file.