Which Postman export format is supported?

Postman Collection format v2.1, the default when you export a collection from Postman. The file must contain an info object and an item array; folders are walked recursively so nested requests are included.

How are path variables converted?

Postman path segments written as :id or {{id}} become OpenAPI path parameters {id}, each declared with in: path and required: true. Query parameters become optional query parameters and request headers become header parameters.

Does it infer a request body schema?

Yes. For POST, PUT, and PATCH requests with a raw JSON body, the tool parses the example and infers a JSON Schema (object properties, array items, and primitive types) under requestBody with application/json content.

Are my API keys exposed?

No. The entire conversion runs in your browser, including reading any file you load. Tokens, keys, and secrets stored in the collection never leave your device and are not written into the output.

Is the output valid OpenAPI 3.0?

It produces a well-formed OpenAPI 3.0.3 skeleton with info, paths, parameters, request bodies, and a default 200 response. You may want to refine response schemas and descriptions, but it imports cleanly into Swagger UI and Redoc.

Postman Collection to OpenAPI Converter

The Postman Collection to OpenAPI Converter turns an exported Postman collection into a clean OpenAPI 3.0 YAML specification. It is ideal when you have documented an API in Postman and now need a machine-readable spec for Swagger UI, Redoc, contract testing, or client/server code generation.

How it works

A Postman Collection v2.1 file is a JSON tree of folders and requests. The converter walks that tree recursively and, for each request, extracts the pieces OpenAPI needs:

Method and path. The HTTP method becomes an OpenAPI operation, and the URL path is normalized into an OpenAPI path. Postman path variables written as :id or {{id}} are rewritten to OpenAPI’s {id} syntax.
Parameters. Path variables become required path parameters, query keys become optional query parameters, and request headers (excluding Content-Type and Accept) become header parameters.
Request body. For POST, PUT, and PATCH requests with a raw JSON body, the example is parsed and a JSON Schema is inferred — objects with typed properties, arrays with item schemas, and the right primitive types.

Operations sharing the same path are grouped under a single path item, exactly as OpenAPI expects, and every operation gets a default 200 response so the document validates out of the box.

YAML safety

All string values — titles, summaries, parameter names, and object keys — are quoted whenever they contain characters that would otherwise break YAML (colons, hashes, brackets, quotes, leading whitespace). That means the output parses reliably in any standard OpenAPI tool.

Tips and notes

Treat the output as a strong starting point. The converter captures structure, parameters, and request-body shapes, but real response schemas, status codes beyond 200, and rich descriptions are things only your API knows — fill those in afterward. Because everything runs locally, you can safely convert collections that contain bearer tokens, API keys, or internal hostnames without anything leaving your browser.