Importing Postman Collections, Insomnia Workspaces, and OpenAPI Specs

Switching tools shouldn't mean starting over. If your requests already exist somewhere else, AlleForge can bring them in directly instead of asking you to recreate every folder, request, and variable by hand.

What you can import

• A Postman export (a collection .json file, or an exported workspace).
• An Insomnia workspace export.
• An OpenAPI/Swagger spec.

Drag any of these in and AlleForge rebuilds your folders, requests, and variables from it automatically.

What actually carries over

• Folder structure — your existing organization is preserved, not flattened into one list.
• Requests — method, URL, headers, body, and query parameters come across as they were.
• Variables — collection- and environment-level variables map onto AlleForge's own Environments, so {{baseUrl}}-style requests keep working without edits.

An OpenAPI/Swagger spec works a little differently from a Postman or Insomnia export: instead of importing already-built requests, AlleForge generates a request per operation defined in the spec — useful for getting a full API's surface into a collection quickly, even if you've never manually built a request against it before.

After importing

Once a collection is in AlleForge, it behaves exactly like one built natively — same roles and permissions, same real-time sharing described on Collaboration, same inherited authentication if the import included auth configuration.

Exporting back out

The same relationship works in reverse — you can export a collection out of AlleForge at any time, so bringing your work in isn't a one-way door.