OpenAPI to Postman Converter

OpenAPI 3.0.x and Swagger 2.0, both as JSON. YAML inputs are parsed with a minimal inline parser — for complex YAML with anchors, arrays of request bodies, or $ref resolution, convert to JSON first using a tool like js-yaml.

The generated collection includes: all HTTP endpoints (GET, POST, PUT, PATCH, DELETE), request headers (Content-Type, Accept, auth headers), sample request bodies derived from schema properties, bearer token and API key auth from OpenAPI security schemes, and a collection-level info block with a UUID.

Download the .json file. In Postman, click 'Import' → 'Upload Files' → select the file. The collection appears in your sidebar with all endpoints ready to test. Set environment variables like {{token}} or {{apiKey}} in a Postman environment.

This tool handles the core fields from spec paths: methods, summaries, request body schemas, and security schemes. Deeply nested $ref pointers, allOf/oneOf schema composition, and multi-file specs are not resolved. For full fidelity, use the official openapi-to-postmanv2 npm package locally.

No. All conversion runs entirely in your browser using JavaScript. Your spec — which may contain endpoint paths, auth schemes, and internal service names — never leaves your machine.

Swagger 2.0 is the predecessor to OpenAPI 3.0. The OpenAPI Initiative adopted and renamed the spec starting with version 3.0. Structurally: Swagger uses 'host' + 'basePath' for the base URL, while OpenAPI 3.0 uses a 'servers' array. OpenAPI 3.0 also separates request body from parameters and adds a richer component/schema system.