Postman Collection Import

Bring your Postman collections in and keep your tests.

Try It FreeSee a Demo

What It Does

Postman Collection Import removes the biggest barrier to switching platforms: the fear of losing existing work. Upload a Postman collection and the platform creates its features, endpoints and tests inside the project you import into, mapping requests, authentication and assertions so they run right away. From there you can enhance the migrated tests with AI test generation, coverage analysis, scheduling and CI/CD, capabilities that plain collections do not offer. Two things stay behind: pre-request scripts are not imported, and Postman environment files are not read, so recreate those values as environments and variables. You can also paste any cURL command (bash, cmd or PowerShell) to get an endpoint plus a test that sends exactly that request.

A Postman collection with OAuth 2.0 auth and pm.test scripts is imported: each pm.test and pm.expect check becomes a native assertion, auth becomes an inherited OAuth 2.0 profile, and every request becomes a test with nothing left out

Overview

Import existing Postman collections (v2.0 and v2.1) into the project you choose, to migrate onto the platform without starting from scratch. Each request with checks becomes its own test, with its body, parameters, headers and checks (bare requests too, with one switch); pm.test assertions are converted, checks the translator cannot map are compiled from the collection script itself, and variable captures become extractions. Authentication is mapped into reusable profiles (API Key, Basic, Bearer, Digest, NTLM, Hawk, JWT Bearer, OAuth 1.0 and OAuth 2.0), with collection and folder auth inherited as in Postman. Form bodies import as real forms, and file parts arrive ready for you to attach the file. Pre-request scripts and Postman environment files are not imported. It is the fastest on-ramp for teams moving from script-based collections to spec-driven, AI-assisted testing.

Key Capabilities

Each request with checks becomes its own test; the import summary lists anything left out
pm.test assertions converted; unmappable checks compiled from the collection script
Auth mapped into profiles: OAuth 2.0 (incl. PKCE), NTLM, Digest, Hawk, JWT Bearer, OAuth 1.0 and more
Collection → folder → request auth inheritance, exactly as in Postman
Variable captures become extractions; form bodies and file parts come across
Re-import after the collection changes without duplicates; paste any cURL command too

How It Works

  1. 1

    Export your collection from Postman

  2. 2

    Upload the collection file to a project

  3. 3

    The platform creates features, endpoints and tests, with auth mapped into profiles

  4. 4

    Collection assertions are translated into platform assertions

  5. 5

    Recreate environment values, then run, schedule and extend the imported tests with AI

Available on

All Plans

Included in the free trial — no credit card required.

Start Free TrialView Pricing
Included in all plans
See pricing →

Documentation

Step-by-step guides for setting up and using Postman Import.

Go deeper

Guides and playbooks that show this capability in practice.

Migrate From Postman to Spec-Driven API Testing (2026)

Read the guide

6 Best Postman Alternatives for Automated API Testing in 2026

Read the guide

Why Postman Collections Are Not Enough for CI/CD Pipelines (2026)

Read the guide

Related Features

Auth Profiles

OAuth 2.0, NTLM, JWT Bearer, Hawk, Digest, AWS SigV4 and more, configured once per environment.

Learn more

Assertions

Validate every aspect of API responses with 100+ built-in assertions.

Learn more

File Uploads & Forms

Test multipart uploads, url-encoded forms and raw file bodies, sent the same way everywhere a test runs.

Learn more

Try Postman Import Today

Start your 15-day free trial — no credit card required.

Start Free TrialBook a Demo