Skip to content
TextArray1.41.0
100% local

OpenAPI to Postman collection

Convert an OpenAPI or Swagger document into a ready-to-import Postman v2.1 collection.

Input
Output
Related tools
OpenAPI endpoint listernewDeveloper tools
cURL to code converterDeveloper tools
JSON formatter & validatorText formatting
i18n key diffDeveloper tools
TOML to JSON converterDeveloper tools
SQL to JSONDeveloper tools
OpenAPI to Postman collection
Paste an OpenAPI 3 or Swagger 2 document — JSON or YAML — and this tool builds a Postman v2.1 collection you can import straight into Postman, Insomnia or any client that reads the format. Every operation in the spec becomes a request, organized into folders so a large API stays navigable instead of landing as one flat list.
Group requests by tag or by the first path segment, whichever matches how your team already thinks about the API. Turn on "Insert base URL as an environment variable" to swap the server URL for a {{baseUrl}} variable, so switching between staging and production is a single environment change instead of editing every request. "Add auth headers from the security scheme" reads the spec's bearer, API-key or OAuth2 definitions and adds the matching Authorization or key header as a placeholder. "Generate sample request bodies from schemas" builds a JSON example for each request from its schema, following $ref references within the document, so POST and PUT requests arrive pre-filled instead of empty. Query parameters can be included with their descriptions, deprecated endpoints can be skipped entirely, and a basic test script checking for a successful status code can be added to every request.
Path parameters like {id} become Postman's :id path variables automatically, and CRLF and LF line endings in a pasted document are treated the same. Large specs with hundreds of operations convert in one pass; if the collection would exceed the output limit, it says so instead of freezing the tab.
Everything happens locally in your browser — the document you paste, including any internal API details it contains, is never uploaded anywhere. When the collection is ready, copy it, download it as a file, or send it to another tool's input to keep working on it.
FAQ
Does it support both OpenAPI 3 and Swagger 2 documents?
Yes. It reads OpenAPI 3's "servers" and "components.securitySchemes" as well as Swagger 2's "host"/"basePath"/"schemes" and "securityDefinitions", and accepts either JSON or YAML.
Which security schemes does it recognize?
HTTP bearer and basic auth, API keys in a header, query parameter or cookie, and OAuth2/OpenID Connect — each maps to the matching placeholder header or query parameter.
How are sample request bodies generated?
From the request schema's own "example" or "default" values where present, falling back to a type-appropriate placeholder — $ref references are resolved within the same document.
What happens to $ref that point outside the document?
They resolve to null in the generated example rather than being followed anywhere — nothing in this tool ever makes a network request.
Is my API document uploaded anywhere?
No. The conversion runs entirely in your browser — the document and everything in it stay on your device.