Importing

Bring existing work into Impostor by importing Postman collections and environments, OpenAPI/Swagger API specifications, or by pasting a cURL command.

Postman compatibility

Impostor provides first-class support for importing Postman v2.1 collections. The importer accurately maps folders, requests, headers, body modes (including binary file bodies), and scripts. It also correctly handles Postman’s authentication and script inheritance, ensuring your setup remains intact.

You can import Postman environments directly; any variables marked as secret will be securely migrated to Impostor’s encrypted secret storage. The Environments section’s ⋮ menu offers Import from Postman as a shortcut, with the environment kind pre-selected.

Importing several files at once

The import dialog accepts multiple files in one batch — Postman JSON exports or OpenAPI/Swagger specs — browse for several files (or add paths one by one) and each is auto-detected. Files are imported independently, so a problem with one file never aborts the rest of the batch.

After an import, each file gets its own result row with counts and warnings for any features that couldn’t be mapped.

OpenAPI & Swagger

Impostor imports OpenAPI 3.0/3.1 specifications, with best-effort support for Swagger 2.0. Specs can be either JSON or YAML — the format is detected automatically.

Each spec becomes a collection folder named after the API’s title. Operations are grouped into sub-folders by their first tag (the Swagger-UI convention); untagged operations land at the collection root. The importer maps:

• Servers → a baseUrl variable every request is built on ({{baseUrl}}/path). Server-URL template variables (and Swagger 2.0’s host/basePath/schemes) are resolved into folder variables you can point at different environments.
• Path/query/header parameters — path templating like /users/{id} becomes {{id}}, and required parameters are imported enabled.
• Request bodies — a representative JSON body is generated from the operation’s schema (using declared examples where present), with local $refs resolved. Form and multipart bodies map to their field lists.
• Security schemes — http bearer/basic, apiKey (header/query), and oauth2 flows map to the matching auth type. Because a spec never contains credentials, these are imported as empty placeholders for you to fill in. Spec-wide security becomes the collection’s auth; per-operation security overrides it.

Known limitations

External or remote $refs (to other files or URLs) are skipped, oneOf/anyOf compositions import using their first option, and response examples aren’t imported. Anything that couldn’t be mapped is listed in the import’s warnings.

cURL commands

For quick ad-hoc requests, you can import a request directly by pasting a cURL command. Impostor will parse the command and populate a new tab with the corresponding URL, method, headers, and body.