API Toolkit

OpenAPI → Postman

All tools

Get a Postman collection skeleton from a spec in one paste.

How it works

Four simple steps

1

Paste the spec

Use an OpenAPI 3 document in JSON.

2

Requests are created

One request per operation, named by operationId.

3

Variables are set

Paths use {{baseUrl}} and :param placeholders.

4

Import into Postman

Copy the JSON or download and rename it.

OpenAPI → Postman

About OpenAPI → Postman

A new teammate wants to try the API in Postman, and the only artifact you have is the OpenAPI JSON your build produces. Converting it gives them a collection with every endpoint in place, so they can start sending requests without recreating them one by one.

Paste an OpenAPI 3 document in JSON format. For each path and each HTTP method (GET, POST, PUT, PATCH, DELETE, OPTIONS and HEAD) the converter adds a request named after its operationId, or after the method and path when there is none. URLs are written as {{baseUrl}} followed by the path, with OpenAPI path templates like {orderId} turned into Postman path variables such as :orderId. The baseUrl variable comes from the first entry in servers, and the collection takes its name from info.title.

Think of the result as a draft rather than a full import. Requests have no headers, query parameters or bodies, and they are listed flat instead of grouped into folders by tag. Download saves the JSON as output.txt, so rename it to something like collection.json before importing it into Postman. If your spec is YAML, convert it first with YAML to JSON. When you need example bodies, validation and type generation, the OpenAPI Studio is the more complete tool.

The spec is converted inside your browser, and neither it nor the collection is uploaded.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

The converter only maps paths, methods and names. Add request bodies, auth and headers in Postman after importing, or use a fuller generator that reads examples.

The baseUrl variable defaults to https://api.example.com. Change it in the collection variables after importing.

Only partly. Swagger 2.0 also has a paths object, so requests are created, but host and basePath are ignored and baseUrl falls back to the placeholder. Convert to OpenAPI 3 for better results.

View more FAQs

Related tools

View all

Webhook HMAC Signer

Sign and verify GitHub, Stripe, and Slack webhook signatures locally.

Open

Webhook Replay Diff Lab

Compare webhook payload timelines, re-check HMAC digests, and spot idempotency gaps locally.

Open

JSONPath Playground

Query JSON with JSONPath and JMESPath-style paths side by side.

Open

GraphQL Studio

Format, validate, and cost-estimate GraphQL documents with cURL export.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools