Export OpenAPI to a Postman Collection

Open this example in OpenAPI to Postman

Open the tool, then paste the sample input below. Everything runs locally in your browser.

Open this example in OpenAPI to Postman →

The problem

Recreating every endpoint in Postman by hand is slow and drifts from the spec. Exporting the OpenAPI spec to a Postman collection gives you all the requests, grouped and parameterized, in one import — and it stays consistent with the contract.

Sample input

OpenAPI (excerpt)

servers: [ { url: https://api.example.com } ]
paths:
  /orders: { get: { summary: List orders } }

Expected output

Postman collection (excerpt)

{
  "info": { "name": "Example API" },
  "variable": [ { "key": "baseUrl", "value": "https://api.example.com" } ],
  "item": [ { "name": "List orders",
              "request": { "method": "GET", "url": "{{baseUrl}}/orders" } } ]
}

The server URL becomes a {{baseUrl}} collection variable and each operation becomes a named request, so switching environments only changes the variable.

How to do it

Paste the OpenAPI spec.
Convert it to a Postman collection.
Check the folders, requests, and the base-URL variable.
Download the collection JSON.
Import it into Postman.

Common mistakes

Hard-coding the base URL instead of using a collection variable.
Losing auth settings that are not expressed in the spec.
Expecting example response bodies the spec does not define.
Importing into the wrong workspace.
Not re-exporting after the spec changes, so the collection drifts.

Related tools

Related guides

Generate API client code from OpenAPI

FAQ

How do I turn an OpenAPI spec into a Postman collection?

Paste the spec and export it. Each path becomes a request grouped into folders, and the server URL becomes a collection variable you can import into Postman.

Does the base URL become a variable?

Yes. The server URL is stored as a collection variable such as {{baseUrl}}, so switching environments only means changing one value.

Is authentication included?

Auth that the spec describes is mapped where possible, but credentials and schemes not expressed in the spec must be set in Postman after import.

Will example responses be included?

Only if the spec defines example bodies. Otherwise the collection contains the requests without saved example responses.

Is my spec uploaded?

No. The conversion runs locally in your browser. Your spec is not sent to a server.

The Postman collection is built locally in your browser. Your spec is not uploaded.

Explore more JSON and API contract tools

Export to Postman, generate clients, validate schemas and query payloads — grouped in one place.

View the JSON & API contract toolkit →

Export OpenAPI to a Postman collection