How do I convert OpenAPI to a Postman collection?

Paste your OpenAPI 2.x or 3.x spec. Specway generates a Postman v2.1 collection JSON with one request per operation, mapping methods, URLs, path parameters, query parameters, headers, and JSON request bodies. Click 'Download' to save as .json, then drag it into Postman to import.

How is this different from Postman's own importer?

Postman has a built-in OpenAPI importer that handles complex specs including auth schemes, examples, and references. This widget produces a clean v2.1 collection in seconds without round-tripping through Postman's UI — useful when you want to inspect the JSON or commit it to a repo. For full feature parity, use Postman's importer.

Are environment variables created?

Path and query parameters use {{name}} syntax so you can populate them via Postman environments. Headers from the spec also use {{name}}. After import, create an environment with values for each variable. The collection itself doesn't ship environment values for security reasons.

Does it convert auth schemes?

Auth schemes are not auto-applied to requests in this widget — Postman's auth model is request- or collection-scoped, and OpenAPI auth definitions don't always map cleanly. Configure auth in Postman after import. For full auth-scheme conversion, use Postman's official importer or the openapi-to-postmanv2 npm package.

Will the request bodies be pre-populated?

JSON bodies start as empty objects ({}). The widget doesn't auto-generate example payloads from schemas because schemas can be deeply nested with $refs that need resolution. To populate bodies, fill them in Postman after import — or use Specway's docs platform, which renders interactive examples directly from your spec.

Can I use this for Bruno / Insomnia / Hoppscotch?

Postman v2.1 is the most universal collection format — Insomnia and Bruno both import it. For Hoppscotch, save the collection and use their import option. For native Bruno (.bru files), use bruno-cli to convert from Postman. The Postman v2.1 format is effectively the lingua franca of API request collections.

How do I convert OpenAPI to a Postman collection?

Paste your OpenAPI 2.x or 3.x spec. Specway generates a Postman v2.1 collection JSON with one request per operation, mapping methods, URLs, path parameters, query parameters, headers, and JSON request bodies. Click 'Download' to save as .json, then drag it into Postman to import.

How is this different from Postman's own importer?

Postman has a built-in OpenAPI importer that handles complex specs including auth schemes, examples, and references. This widget produces a clean v2.1 collection in seconds without round-tripping through Postman's UI — useful when you want to inspect the JSON or commit it to a repo. For full feature parity, use Postman's importer.

Are environment variables created?

Path and query parameters use {{name}} syntax so you can populate them via Postman environments. Headers from the spec also use {{name}}. After import, create an environment with values for each variable. The collection itself doesn't ship environment values for security reasons.

Does it convert auth schemes?

Auth schemes are not auto-applied to requests in this widget — Postman's auth model is request- or collection-scoped, and OpenAPI auth definitions don't always map cleanly. Configure auth in Postman after import. For full auth-scheme conversion, use Postman's official importer or the openapi-to-postmanv2 npm package.

Will the request bodies be pre-populated?

JSON bodies start as empty objects ({}). The widget doesn't auto-generate example payloads from schemas because schemas can be deeply nested with $refs that need resolution. To populate bodies, fill them in Postman after import — or use Specway's docs platform, which renders interactive examples directly from your spec.

Can I use this for Bruno / Insomnia / Hoppscotch?

Postman v2.1 is the most universal collection format — Insomnia and Bruno both import it. For Hoppscotch, save the collection and use their import option. For native Bruno (.bru files), use bruno-cli to convert from Postman. The Postman v2.1 format is effectively the lingua franca of API request collections.

Free Tool

OpenAPI → Postman (2026)

Convert your OpenAPI / Swagger spec into a Postman v2.1 collection JSON. One request per operation, with path/query/header parameters as Postman variables. Download or copy the JSON.

OpenAPI / Swagger spec · 3 requests generated

{
  "info": {
    "name": "Pet Store",
    "description": "",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json",
    "_postman_id": "c68641aa-0ea5-4245-aa9b-7cc13a741243"
  },
  "item": [
    {
      "name": "List pets",
      "request": {
        "method": "GET",
        "header": [],
        "url": {
          "raw": "https://api.example.com/v1/pets",
          "protocol": "https",
          "host": [
            "api",
            "example",
            "com"
          ],
          "path": [
            "v1",
            "pets"
          ],
          "variable": []
        },
        "description": "List pets"
      }
    },
    {
      "name": "Create a pet",
      "request": {
        "method": "POST",
        "header": [],
        "url": {
          "raw": "https://api.example.com/v1/pets",
          "protocol": "https",
          "host": [
            "api",
            "example",
            "com"
          ],
          "path": [
            "v1",
            "pets"
          ],
          "variable": []
        },
        "description": "Create a pet",
        "body": {
          "mode": "raw",
          "raw": "{}",
          "options": {
            "raw": {
              "language": "json"
            }
          }
        }
      }
    },
    {
      "name": "Get a pet",
      "request": {
        "method": "GET",
        "header": [],
        "url": {
          "raw": "https://api.example.com/v1/pets/{id}",
          "protocol": "https",
          "host": [
            "api",
            "example",
            "com"
          ],
          "path": [
            "v1",
            "pets",
            ":id"
          ],
          "variable": [
            {
              "key": "id",
              "value": ""
            }
          ]
        },
        "description": "Get a pet"
      }
    }
  ]
}

Why convert OpenAPI to Postman

OpenAPI is the source of truth for your API contract; Postman is where teams actually click around testing. Conversion gives non-technical teammates (or QA, or support) a click-through view of every operation without learning OpenAPI syntax. Specway generates a clean Postman v2.1 collection in seconds.

What gets converted

One request per operation — every method/path pair in the spec.
Path parameters — converted to Postman :variable syntax with a placeholder value.
Query parameters — added to the URL with {{name}} placeholders.
Header parameters — added as Postman headers with {{name}} placeholders.
JSON request bodies — empty {} placeholder you fill in Postman.
Operation summary / description — preserved as the request name and description.

After import

Drag the downloaded JSON into Postman's left sidebar, or use File → Import.
Create an environment with values for every {{variable}} the collection uses (typically baseUrl + auth headers).
Set up auth on the collection or per-request (OpenAPI security schemes don't auto-translate to Postman auth — needs manual setup).

Ship API docs that stay this clean

Specway turns your OpenAPI spec into a branded developer portal — auto-synced, searchable, with built-in playground and code samples in every language. Free tier available.

Related tools

cURL → Code

Convert single requests to JS, Python, Go.

OpenAPI Validator

Validate the spec before exporting.

OpenAPI Viewer

Browse the operations the collection will contain.

OpenAPI → TypeScript

Generate TS types in parallel.

Frequently asked questions