Import from Postman

For a detailed feature-by-feature comparison of Apidog and Postman, see Apidog vs. Postman.

Video Tutorial

What You Can Import from Postman

Conceptual Map

Import Methods

Apidog supports two ways to migrate Postman data.

Import via the Postman API

Import using files

Import via the Postman API

Use this method when you want to migrate data directly from your Postman account by using the Postman API key.

This is recommended when:

You need to migrate multiple workspaces or collections.

You want Apidog to fetch collections and environments automatically.

You want to create Apidog projects from selected Postman workspaces.

Postman API import may be affected by Postman's official API rate limits. If you are importing many collections, the process may take longer.

Choose an entry point based on where you want to import the Postman data.

Goal	Entry Point	Import Methods
Create your first project	Empty team page > Import Postman collection	Upload files/folder, Postman API
Create a new project	Team Page > Import Project > Postman	Upload files/folder, Postman API

Create a New Project

After selecting Postman

choose the Postman API method

Enter a Postman API key,

then select Workspaces, Collections, and Environments to import.

To create a Postman API key, open Postman and go to Settings > API Keys.

Import Using Files

If you are importing using files, export your data from Postman first.

Export a Collection

Open Collections in the Postman sidebar.

Click the ... icon next to the collection.

Select Export under More.

Choose Collection v2.1. This format is recommended.

Save the JSON file.

Batch Export Multiple Collections
You can also export multiple Postman collections in one package.

Click your account avatar in the top-right corner of Postman.

Select Settings.

Under Account Settings, click Export Data.

Create a new export request.

Select Collections and Environments as needed.

Download the exported file from the email Postman sends you.

Export an Environment (Optional but Recommended)
If your collection uses environment variables, export the related environment too.

Open Environments in the Postman sidebar.

Click the ... icon next to the environment.

Select Export.

Save the JSON file.

Import into Apidog

Open Settings > Import Data in your Apidog project or click on Import Project button on the Team Page.

Select Postman and upload your Collection JSON file (or folder, if you have both collection and environment files). If you have many files, you can upload the containing folder to Apidog.

Match the Environment Variables
If you imported an Environment JSON along with the Collection:

On the Import Preview screen, choose whether or not baseURL should be included with endpoint urls.

If baseURL is not included in endpoint urls, make sure the environment baseURL is set properly.

Import Options

During import, Apidog may show options that control how your Postman data is converted and merged.

Keep or Remove Base URLs

You can choose whether Apidog should keep the full request URL or remove the base URL from endpoints.

Import using Files	Import via Postman API

Keep full URLs: Apidog keeps the original request URL as much as possible. Use this if you want the imported endpoints to stay close to the original Postman requests.

Remove base URLs: Apidog tries to detect the base URL from Postman URLs and variables, then stores it in environment or base URL settings. Use this if you want cleaner endpoint paths such as /users instead of https://api.example.com/users.

For long-term API management, removing base URLs is usually easier to maintain. It lets you switch environments without changing endpoint paths.

Other Import Options

Option	Description
Environments	If your requests use variables, import the related Postman environments. For example, if your request URL is `{{baseUrl}}/users`, Apidog needs the environment, collection variable, or global variable that defines `baseUrl`.
Examples or API Cases	Postman saved examples and responses can be imported as response examples or API cases in Apidog. Enable this option if you want to preserve example responses for documentation, testing, or debugging.
Overwrite Existing Data	Common choices include: Overwrite existing data, Merge with existing data, Keep existing data, Create new resources
Sync Folder Structure	Enable folder sync if you want Apidog to preserve or update the folder structure from your Postman collection. This is useful when your Postman folders represent product areas, services, or API groups.
Authorization Settings	Apidog can map supported Postman authorization settings from the collection, folder, or request level. After import, review inherited auth settings to make sure they match your expected request behavior.

How Apidog Handles Base URLs

Base URL handling is one of the most important parts of a Postman migration.

In Postman, requests often use URLs such as:

https://api.example.com/v1/users
{{baseUrl}}/v1/users
{{host}}/users

In Apidog, API endpoints are easier to manage when the endpoint path and environment base URL are separated.

For example:

Postman URL	Possible Apidog Result
`https://api.example.com/v1/users`	Base URL: `https://api.example.com`, endpoint path: `/v1/users`
`{{baseUrl}}/users`	Base URL variable from environment/collection, endpoint path: `/users`
`/users`	Endpoint path: `/users`

For best results:

Import collections together with their environments and globals.

Make sure variables such as baseUrl, host, token, or api_url exist in the imported files.

Review the import preview before confirming.

After import, select the correct Apidog environment and send a test request.

If Apidog cannot determine the base URL confidently, it may keep more of the original URL in the endpoint path. You can adjust the endpoint path or environment base URL after import.

Verify the Migration

After the import is complete, review the imported project before using it in production workflows.

Recommended checks:

Confirm that collections, folders, and requests were imported.

Select the correct environment in Apidog.

Check that variables such as {{baseUrl}} and {{token}} resolve correctly.

Review request methods, paths, parameters, headers, and bodies.

Check authorization settings at the project, module, folder, and endpoint levels.

Review imported examples or API cases.

Run important requests to confirm they work as expected.

Review pre-processors and post-processors if your Postman collection uses scripts.

Postman import is designed to preserve as much useful API data as possible, but some items may require manual review after migration.

FAQ

Why are my endpoint URLs different after import?

Apidog may remove the base URL from endpoint paths and store it in environment or base URL settings. This makes endpoints easier to reuse across environments.

If you want to preserve the original full URLs, choose the option to keep full endpoint URLs during import.

Why are some variables unresolved?

Should I import Postman environments and globals?

Can I import multiple collections at once?

Are Postman scripts fully supported?

Why did my import fail?

Detailed Guide

For a deeper dive into complex migration scenarios, see How to Migrate Postman Collections to Apidog.

Import Methods#

Import via the Postman API#

Import Using Files#

Import Options#

Keep or Remove Base URLs#

Other Import Options#

How Apidog Handles Base URLs#

Verify the Migration#

FAQ#

Import Methods

Import via the Postman API

Import Using Files

Import Options

Keep or Remove Base URLs

Other Import Options

How Apidog Handles Base URLs

Verify the Migration

FAQ