Import a Postman collection

If your requests already live in Postman, export the collection as JSON and import it into Collapy. Folders become collections, requests keep their URL, headers, params, body and auth, and collection variables can become an environment.

Before you start

• In Postman, export the collection as Collection v2.1 JSON.
• The file must be .json and no larger than 10 MB.
• Imported items are added to the workspace you have open. Switch workspaces first if needed. See Workspaces.

Import the file

1. In the EXPLORER header, click More actions → Import collection. The Import Collection dialog opens.

2. Click Select File and choose your .json export. Collapy detects the format automatically.

3. Review the preview:

   • the collection name and description
   • a count of requests, presets, folders and variables
   • a tree of what will be created
   • Warnings for anything Collapy can't import (see "What isn't imported" below)

4. Choose a Destination:

   Option	Result
   New collection	Creates a new top-level collection, named after the Postman collection by default. You can change the name in Collection name. Everything goes inside it.
   Workspace root	Folders become top-level collections. Requests that aren't in a folder go to the workspace root.
   Existing collection	Click Pick a collection… and choose where to put everything.

5. If the file has collection variables, leave Import N variable(s) as environment ticked to create an environment named <collection name> Variables. Untick it to skip variables.

6. Click Import.

When the import finishes, you see Import complete with a summary: Collections created, Requests created, Presets created (if any) and Environment created (if any). If some items failed, the title reads Import completed with errors and lists each one. Click Close to return to the workspace.

If the file isn't valid JSON or isn't a supported format, the dialog shows Unrecognized format. Supported: Postman v2.1, OpenAPI 3.x JSON. Click Try Again to pick another file.

How Postman items map to Collapy

In Postman	In Collapy
Collection	A collection named after it, when the destination is New collection
Folder (including nested folders)	Collection, nested the same way
Request	Request with method, URL, query params, path variables, headers, body and description
Disabled query params and headers	Imported, still disabled
Saved example (response)	A preset: a saved variant of the request with the example's method, URL, params, headers, auth and body. The example's response isn't imported.
Collection variables	Variables in a new environment, if you tick the option. Variables of type secret are marked Secret and their values are stored securely. See Secret variables.
{{variable}} references	Kept as they are. They resolve against your selected environment. See Variables.

Body

Postman body mode	Collapy body type
raw	Raw (JSON/Text)
form-data	Form Data (text fields)
x-www-form-urlencoded	URL Encoded
binary / file, GraphQL	Not imported; a warning is shown

Authentication

Postman auth	Collapy auth
Bearer Token	Bearer Token
Basic Auth	Basic Auth
API Key (header or query)	API Key
Request with no auth set, or No Auth	Inherit Auth from Parent
OAuth 2.0 and every other type	Skipped with a warning. A request gets Inherit Auth from Parent; a folder or the collection gets No Auth.

Collection-level auth from the file is applied only when you choose New collection. With Workspace root or Existing collection, it's dropped.

Check folder auth after importing

Folders that don't set their own auth in Postman are imported with No Auth, and that stops inheritance. If your Postman collection sets auth at the top level, open each imported sub-collection and set its Auth to Inherit Auth from Parent. Otherwise the requests inside it are sent without auth.

What isn't imported

Collapy shows a warning in the preview for each of these:

• Pre-request scripts and test scripts, at any level
• OAuth 2.0 and other unsupported auth types
• Binary/file and GraphQL bodies
• Saved example responses. Only the example's request becomes a preset.

FAQ

Can I import a Postman environment file?

No. Only collection files are supported. Collection-level variables can become an environment during import. For a separate Postman environment, create the environment in Collapy and add the variables yourself.

Can I import the same file twice?

Yes. Each import creates new items. Nothing is merged or replaced, so you may end up with duplicates.

Can I export back to Postman?

Not yet. Exporting collections isn't available.

Related

• Collections and the Explorer
• Import an OpenAPI spec
• Authentication
• Environments
• Secret variables