Is this a lossless, full-fidelity conversion?

No, it's a best-effort conversion covering the fields most specs actually use: paths, methods, parameters, and a single JSON request body example per operation. $ref pointers aren't followed, and OAuth2 security schemes aren't translated into Postman's auth blocks.

How does the {{baseUrl}} variable get its value?

It's set from the first entry in the spec's top-level servers array (or Swagger 2.0's host/basePath, if you're converting a 2.0 document). If no server is declared, requests still use {{baseUrl}} in their URL, but you'll need to set the variable's value yourself in Postman.

How are operations grouped into folders?

By each operation's first tag. Operations sharing a tag land in one folder named after that tag; operations with no tags at all stay at the collection's top level instead of being grouped.

OpenAPI to Postman Converter - Spec to Postman Collection

Overview

Introduction

An OpenAPI spec is great for documentation and codegen, but exploring an API by hand is usually easier in a request client like Postman than by reading YAML.

This tool converts an OpenAPI or Swagger document into a ready-to-import Postman Collection, grouped into folders by tag, entirely in your browser.

What Is OpenAPI to Postman Converter?

A one-direction converter from OpenAPI 3.x or Swagger 2.0 (JSON or YAML) to Postman Collection v2.1 JSON, built on the same shared conversion core as its Postman-to-OpenAPI counterpart.

It's part of this site's API Tools collection and runs entirely client-side.

How OpenAPI to Postman Converter Works

Every operation under every path is extracted along with its method, parameters, first tag, and (if present) a JSON request body example.

Each operation becomes a Postman request: {param} path segments become :param, query and header parameters become their Postman equivalents, and operations sharing a tag are grouped into one named folder.

When To Use OpenAPI to Postman Converter

Use it when your team maintains an OpenAPI spec as the source of truth but wants a Postman collection for manual exploration or QA testing.

It's also a quick way to try out a third-party API's published OpenAPI spec inside Postman without hand-building each request.

Often used alongside Postman to OpenAPI Converter.

Features

Advantages

Groups requests into folders by tag automatically, mirroring how the spec's own documentation is organized.
Carries the first server URL over as a reusable {{baseUrl}} collection variable instead of hardcoding it into every request.

Limitations

$ref pointers inside the spec aren't resolved, so parameters or schemas defined only by reference won't be reflected in the output.
OAuth2 and API-key security scheme definitions aren't translated into Postman's own auth configuration; you'll need to set that up manually after import.

Examples

Converting a tagged operation

Input

"/users/{id}": {"get": {"tags": ["Users"], "parameters": [{"name": "id", "in": "path"}]}}

Output

{"name": "Users", "item": [{"name": "...", "request": {"url": {"path": [":id"] ...}}}]}

The Users tag becomes a folder, and the {id} path parameter becomes Postman's :id path-segment style.

Picking up a base URL

Input

"servers": [{"url": "https://api.example.com/v1"}]

Output

"variable": [{"key": "baseUrl", "value": "https://api.example.com/v1"}]

The first declared server becomes the collection's baseUrl variable, so every request's {{baseUrl}} resolves to it after import.

Best Practices & Notes

Best Practices

Set up any required auth manually in Postman after import; security scheme definitions from the spec aren't translated automatically.
Check the collection's variable value if your spec declares multiple servers; only the first one is used.
Run the Postman Collection Analyzer on the result to confirm the folder and method breakdown matches what you expect from the source spec.

Developer Notes

Request body examples are read from an operation's requestBody.content, preferring an application/json entry when multiple content types are declared, and pulled from either an explicit `example` field or a schema's own `example` property, matching where real-world specs most commonly put sample payloads.

OpenAPI to Postman Converter Use Cases

Generating a Postman collection for manual QA testing from an existing OpenAPI spec
Trying out a third-party API's published OpenAPI/Swagger document inside Postman without hand-building requests
Keeping a Postman collection in sync with a spec that's the actual source of truth for a team

Common Mistakes

Expecting OAuth2 or API-key auth to be pre-configured in the resulting collection; it needs to be set up manually in Postman.
Converting a spec with multiple servers and being surprised only the first one became the baseUrl variable.

Tips

If your spec has no servers array at all, set the {{baseUrl}} collection variable's value yourself in Postman right after importing.

OpenAPI to Postman Converter