Postman Collection to OpenAPI 3

Paste a Postman Collection (v2.0 or v2.1) and get an OpenAPI 3.0.3 document in YAML or JSON, with tags, parameters, request bodies, example responses and security schemes filled in.

Use the tool

Why this tool exists

Teams often document an API as a Postman collection because that is where the requests were first built. Later a client generator, a gateway or a documentation site asks for an OpenAPI file, and nobody wants to write one from scratch for fifty endpoints.

This converter produces a first draft from the collection you already have. Folders become tags, path variables and query parameters are listed, bodies become schemas inferred from your examples, and saved responses become examples. Because schemas are guessed from sample data, required fields and exact types need a human check. The collection may contain internal URLs and tokens, so it is useful that nothing leaves your browser.

How to use it

  1. Paste your Postman Collection JSON into the input box.
  2. Choose YAML or JSON as the output format.
  3. Read the generated OpenAPI document and check paths, parameters and security schemes.
  4. Copy it into your spec file, then review required fields and types before publishing.

Frequently asked questions

How accurate are the generated schemas?

They are inferred from the example values in your requests and responses, so a field that was empty in one example may get the wrong type. Review required fields, enums and formats before you trust the spec.

What happens to Postman variables?

Variables in curly braces and colon-style path parameters become OpenAPI path parameters. The base URL is not turned into a server entry for you in every case, so check the servers section.

Which authentication types are converted?

Bearer, basic and API key auth are turned into security schemes. Other Postman auth types, such as OAuth flows or AWS signatures, are not converted and need to be described by hand.