OpenAPI → Postman Collection Exporter

How to use the OpenAPI → Postman Collection Exporter

Convert an OpenAPI 3.x or Swagger 2.0 spec into a Postman Collection v2.1 JSON file. Folders are grouped by tag, every operation becomes a request with the right method, URL, parameters, headers, auth scheme, and example body. Import the file into Postman or run it with Newman in CI. Useful for onboarding teams to a new API, generating a baseline test suite, and producing importable docs samples. Spec is parsed locally; nothing is uploaded.

What it does

• Reads OpenAPI 3.x or Swagger 2.0 (JSON or YAML).
• Emits a Postman Collection v2.1 JSON.
• Folders grouped by tag; one request per operation.
• Pre-fills parameters (path, query, header, cookie), request body from examples or schemas, and auth.
• Configures variables from servers entries so base URL is a Postman variable.
• Supports Bearer / Basic / API key / OAuth2 security schemes.
• Optionally adds simple test scripts (status code, JSON schema sanity).

When to use it

• Onboard a team to a new API without hand-building the Postman collection.
• Generate a baseline integration test suite to run with Newman in CI.
• Produce importable Postman samples for developer documentation.
• Audit endpoints by clicking through them in Postman after import.
• Bootstrap a contract-testing workflow.
• Migrate a Swagger 2.0 spec to a usable Postman collection.

How to use it

1. Paste or load your OpenAPI / Swagger spec (JSON or YAML).
2. Review options: folders, request bodies, test scripts, and response examples.
3. Read the verdict, then copy or download the Postman collection JSON.
4. In Postman, click Import and select the downloaded file — the collection appears with folders, requests, and variables.
5. Open the Environment tab to import matching variables (base URL, auth token) and run the requests.
6. For per-operation snippets in code, use the OpenAPI → Code Snippets tool.

Tips & pitfalls

• If the spec lacks examples, the exporter uses sensible placeholders — replace before running.
• OpenAPI servers become Postman environment variables — set the right one before running.
• OAuth2 flows require token acquisition outside Postman — pre-populate {{access_token}} in the environment.
• Large specs produce large collections — split by tag if Postman performance suffers.
• Sample bodies may include placeholder strings — replace before invoking destructive operations (DELETE).
• The exported file is Postman v2.1 — compatible with Postman, Newman, and most modern Postman-compatible tools.

FAQ

• How do I convert OpenAPI to Postman? Paste the spec, read the verdict, download the JSON, import into Postman.
• Does it work with Swagger 2.0? Yes — Swagger 2.0 is converted with parameter style adjustments.
• How do I set the base URL? The first servers entry becomes a Postman environment variable. Override it in the Postman environment dialog.
• Can I run the collection in CI? Yes — use Newman, Postman's CLI, to run the exported file in a pipeline.
• Is my spec uploaded? No. Conversion runs in your browser.
• How does this differ from OpenAPI → Code Snippets? Code snippets give per-operation code in a language. This tool produces a multi-request Postman collection.

Runs locally in your browser. No uploads. Exported collection is Postman v2.1 compatible with Postman and Newman.

Related guides

• Export OpenAPI to a Postman collection