OpenAPI to Postman Converter — Free Swagger Collection
OpenAPI to Postman Collection Converter
Convert OpenAPI/Swagger specs to Postman Collection v2.1 JSON.
Free online OpenAPI to Postman converter. Paste your OpenAPI 2.0 (Swagger) or OpenAPI 3.x JSON/YAML specification and instantly generate a Postman Collection v2.1 with all endpoints organized by tags or paths. Auto-detects authentication schemes (Bearer, API Key, Basic Auth), generates example request bodies from schemas, and includes path/query parameters. Download the .postman_collection.json and import directly into Postman or Newman.
Keywords: openapi to postman, swagger to postman, openapi to postman collection, swagger to postman collection, convert openapi to postman, postman collection generator, openapi postman converter online, swagger postman export, api collection generator, openapi 3 to postman, swagger 2 to postman, postman collection from openapi
Tags: openapi, swagger, postman, api, collection, converter
Popular Developer Tools tools
- JWT DecoderDecode, inspect, and validate JWT tokens with claim analysis.
- Cron ParserParse, validate, and build cron expressions with human-readable explanations.
- Regex TesterTest, debug, and explain regular expressions with real-time match highlighting.
- Regex ExplainerBreak down any regex into plain English, token by token.
- JSON to TypeScript & Schema GeneratorGenerate TypeScript interfaces, Zod schemas, and Valibot schemas from JSON.
How to OpenAPI to Postman Collection Converter Online
Paste your OpenAPI specification (JSON or YAML format) into the input panel, or upload the spec file.
Configure collection options: grouping strategy (by tags or by path segments), and whether to include example request bodies.
Select the authentication type to pre-configure — Bearer token, API Key header, Basic Auth, or None.
Click "Convert" to generate the Postman Collection v2.1 JSON.
Download the collection as a .postman_collection.json file, then import it directly into Postman via File → Import.
OpenAPI to Postman Collection Converter Features
Supports OpenAPI 2.0 (Swagger) and OpenAPI 3.0/3.1 specification formats
Outputs Postman Collection format v2.1 — the current standard supported by all Postman clients
Groups requests by API tags or by URL path hierarchy for organised collections
Detects and maps authentication schemes: Bearer token, API Key (header/query), Basic Auth, and OAuth2
Generates example request bodies from OpenAPI schema definitions and inline examples
Maps path parameters, query parameters, and header parameters to Postman variable syntax ({{variable}})
Supports JSON and YAML OpenAPI input with automatic format detection
Resolves local $ref references within the specification for accurate schema expansion
Generates collection-level variables for base URL and authentication tokens
Produces downloadable .postman_collection.json ready for direct Postman import
Handles multi-server OpenAPI 3.0 specs by using the first server as the base URL
AI-powered analysis explains generated collection structure and authentication setup
Frequently Asked Questions
- Which OpenAPI versions are supported?
- The converter supports OpenAPI 2.0 (also known as Swagger), OpenAPI 3.0.x, and OpenAPI 3.1.x. Both JSON and YAML input formats are accepted. The output is always Postman Collection v2.1 format, regardless of the input version.
- What is Postman Collection v2.1?
- Postman Collection v2.1 is the current JSON schema for Postman API collections. It supports folders, request items, variables, authentication configs, and pre-request scripts. It is the format exported by Postman and accepted for import by Postman, Newman (CLI runner), and other API testing tools.
- How is authentication mapped from OpenAPI to Postman?
- OpenAPI security schemes are mapped to Postman auth configurations: `http: bearer` becomes Bearer Token auth, `apiKey` becomes API Key header/query auth, `http: basic` becomes Basic Auth, and `oauth2` becomes OAuth 2.0 auth. Collection-level variables are created for token values.
- Can I import a YAML OpenAPI spec?
- Yes. The converter automatically detects whether input is JSON or YAML and parses accordingly. Both `openapi:` (YAML) and `{"openapi":` (JSON) OpenAPI 3.x formats are supported, as well as `swagger: "2.0"` Swagger specifications.
- How do I import the collection into Postman?
- Download the .postman_collection.json file, then open Postman and go to File → Import (or press Ctrl+O / Cmd+O). Select the downloaded file and Postman will create the collection with all folders and requests populated.
- What about $ref references in my spec?
- Local $ref references (within the same file, e.g., `#/components/schemas/User`) are resolved and inlined. External $ref references pointing to separate files or URLs are not resolved — consolidate your spec into a single file first if it uses external references.
- What is the difference between Swagger and OpenAPI?
- Swagger was the original name of the specification. In 2016, Swagger 2.0 was donated to the OpenAPI Initiative and renamed OpenAPI Specification 2.0. OpenAPI 3.0 introduced significant improvements including better request body handling, multiple servers, and enhanced schema support. OpenAPI 3.1 aligns with JSON Schema 2020-12.
- Is my API spec data safe?
- OpenAPI specs are processed on our server for format conversion. Do not include production API keys or secrets in your spec. Public API descriptions and schema definitions are safe to convert — only include sensitive values in Postman environment variables after import.
Related Developer Tools
- OpenAPI ValidatorValidate, format, and summarize OpenAPI/Swagger specifications.
- cURL to Code ConverterConvert cURL commands to code in 12+ programming languages instantly.
- API Request BuilderBuild and test HTTP API requests with headers, body, auth, and response visualization.
- HAR to Postman Collection ConverterConvert HAR files to Postman Collection v2.1 JSON for API testing.
- HAR Analyzer & Request ReplayAnalyze HAR files, inspect slow/failed requests, generate replayable curl/fetch code.