Apidog Docs
🇺🇸 English
  • 🇺🇸 English
  • 🇯🇵 日本語
HomeLearning CenterSupport CenterAPI References
HomeLearning CenterSupport CenterAPI References
Discord Community
Slack Community
X / Twitter
🇺🇸 English
  • 🇺🇸 English
  • 🇯🇵 日本語
  1. Import from...
  • Apidog Learning Center
  • Get started
    • Introduce Apidog
    • Basic concepts in Apidog
    • Navigating Apidog
    • Quick Start
      • Overview
      • Specify a new endpoint
      • Make a request to the endpoint
      • Add an assertion
      • Create a test scenario
      • Share your API documentation
      • Explore more
      • Send a request and save as an endpoint
    • Migration
      • Overview
      • Manual import
      • Scheduled import
      • Import options
      • Export data
      • Import from...
        • Import from Postman
        • Import OpenAPI (Swagger) spec
        • Import cURL
        • Import Markdowns
        • Import from Insomnia
        • Import from apiDoc
        • Import .har file
        • Import WSDL
  • Design APIs
    • Overview
    • Create a new API project
    • Endpoint basics
    • Components
    • Common fields
    • Global parameters
    • Endpoint change history
    • Batch endpoint management
    • Configure multiple request body examples
    • Schemas
      • Generate Schemas from JSON etc.
      • Build a schema
      • Overview
      • Create a new schema
    • Security schemes
      • Overview
      • Create a security scheme
      • Use the security scheme
      • Security scheme in online documentation
    • Advanced features
      • Custom endpoint fields
      • Import endpoints as test steps
      • Endpoint status
      • Appearance of parameter lists
      • Endpoint unique idenfication
  • Develop and Debug APIs
    • Overview
    • Generate requests
    • Send requests
    • Endpoint cases
    • Dynamic values
    • Validate responses
    • Design-first Mode & Request-first Mode
    • Generate code
    • Environments & variables
      • Overview
      • Using variables
      • Environments & services
    • Vault secrets
      • Overview
      • HashiCorp Vault
      • Azure Key Vault
      • AWS Secrets Manager
    • Pre/Post processors
      • Overview
      • Assertion
      • Extract variable
      • Wait
      • Database operations
        • Overview
        • MongoDB
        • Redis
        • Oracle Client
      • Using scripts
        • Overview
        • Postman scripts reference
        • Pre processor scripts
        • Post processor scripts
        • Public scripts
        • Calling other programming languages
        • Using JS libraries
        • Visualizing responses
        • Script examples
          • Assertion scripts
          • Using variables in scripts
          • Using scripts to modify request messages
          • Other examples
    • Dynamic values Modules
  • Mock API data
    • Overview
    • Smart mock
    • Custom mock
    • Mock priority sequence
    • Mock scripts
    • Cloud mock
    • Self-hosted runner mock
    • Mock language (Locales)
  • Automated tests
    • Overview
    • Test reports
    • Test scenarios
      • Create a test scenario
      • Pass data between requests
      • Flow control conditions
      • Import endpoints/endpoint cases from other projects
      • Sync data from endpoints/endpoint cases
      • Export test scenarios
    • Run test scenarios
      • Run a test scenario
      • Data-driven testing
      • Run test scenarios in batch
      • Scheduled tasks
      • Manage the runtime environment of APIs from other projects
    • Test APIs
      • Integration testing
      • Performance testing
      • End-to-end testing
      • Regression testing
    • Apidog CLI
      • Overview
      • Installing and running Apidog CLI
      • Apidog CLI Options
    • CI/CD
      • Overview
      • Integrate with Jenkins
      • Integration with Gitlab
  • Publish API Docs
    • Overview
    • API Technologies Supported
    • Quick share
    • View the API documentation
    • Publish docs sites
    • Folder tree settings
    • Custom layouts
    • Visibility settings
    • Endpoint SEO settings
    • Custom domain
    • Embedding values in document URLs
    • Documentation Search
    • Integrating Google Analytics with Doc Sites
    • CORS Proxy
    • API Versions
      • Overview
      • Create API versions
      • Publish API versions
      • Share endpoints with API versions
  • Send requests
    • Overview
    • gRPC
    • Use request proxy agents for debugging
    • SOAP/WebService
    • GraphQL
    • WebSocket
    • Socket.IO
    • SSE debugging
    • Create requests
      • Request History
      • Request basics
      • Parameters and body
      • Request headers
      • Request settings
      • HTTP/2
    • Authentication and authorization
      • Overview
      • CA and client certificates
      • Authorization types supported by Apidog
      • Digest Auth
      • OAuth 1.0
      • OAuth 2.0
      • Hawk Authentication
      • Kerberos
      • NTLM
      • Akamai EdgeGrid
    • Response and cookies
      • Overview
      • API response in Apidog
      • Create and send cookies
      • Debug requests
      • Save the request as an endpoint
  • Branches
    • Overview
    • Create a new sprint branch
    • Test APIs in a branch
    • Design API in a branch
    • Merge sprint branches
    • Manage sprint branches
  • Apidog MCP Server
    • Overview
    • Conntect API Specification within Apidog Project to AI via Apidog MCP Server
    • Conntect Online API Documentation Published by Apidog to AI via Apidog MCP Server
    • Conntect OpenAPI Files to AI via Apidog MCP Server
  • Best practices
    • How to handle API signatures
    • How to access OAuth 2.0 protected APIs
    • Apidog collaboration workflow
    • Managing authentication state in Apidog
  • Administration
    • Onboarding Checklist
      • Basic Concepts
      • Onboarding Guide
    • Managing Teams
      • Managing Teams
      • Managing Team Members
      • Member Roles & Permission Settings
      • Team Activities
      • Team Resources
        • General Runner
        • Team Variables
        • Request Proxy Agent
      • Real-time Collaborations
        • Team Collaboration
    • Managing Projects
      • Managing Projects
      • Managing Project Members
      • Notification Settings
      • Project Resources
        • Database Connection
    • Managing Organizations
      • Single Sign-On (SSO)
        • SSO Overview
        • Configure Microsoft Entra ID
        • Configure Okta
        • Configure SSO for an Organization
        • Managing user accounts
        • Mapping Groups to Teams
      • SCIM Provisioning
        • Intro to SCIM Provisioning
        • Microsoft Entra ID
        • Okta
      • Organization Resources
        • Self-hosted Runner
  • Billing
    • Overview
    • Credits
    • Unable to use credit cards?
    • Managing subscriptions
    • Upgrade plan
  • Add-ons
    • API Hub
    • Apidog Intellij IDEA plugin
    • Browser Extension
      • Chrome
      • Microsoft Edge
    • Request Proxy
      • Request proxy in Apidog web
      • Request proxy in shared docs
      • Request proxy in Apidog client
  • Account & preferences
    • Language settings
    • Data backup
    • Network proxy configuration
    • Hot keys
    • Updating Apidog
    • Generate OpenAPI access token
    • Deleting account
    • Account settings
  • References
    • API-Design First Approach
    • Apidog OpenAPI Specificaiton Extensions
    • JSONPath
    • XPath
    • Regular Expressions
    • JSON Schema
    • CSV File Format
    • Install Java Environment
    • Runner deployment environment
    • Apidog flavored Markdown
  • Apidog Europe
    • Apidog Europe
  • Support Center
  1. Import from...

Import from Postman

Video Tutorial#

Conceptual Mapping#

Understanding the conceptual correlation between Postman and Apidog can help prevent data inconsistencies during import.
In Postman, a Collection corresponds to a Project in Apidog. Thus, variables within a Postman Collection are equivalent to global variables in an Apidog project.
The Postman API uses variables to store the front URL (usually a domain name), while the front URL of Apidog is stored independently in the Service in Environment Management.

Example#

Suppose you have a Collection named Apidog Echo, which contains two variables:
baseUrl: defines the service address
name: used as a query parameter
This Collection has a GET request:
Now it's time to export the Collection and import it into Apidog.
If you already have a Collection in Postman, feel free to use that instead — no need to start from scratch.

How to Export Data from Postman?#

Exporting a Collection#

Follow these steps to export a collection from Postman:
1
Open Collections on the left sidebar of Postman
2
Mouse over the collection to export, click the ... icon, and select Export
3
In the pop-up window, choose the export format as Collection v2.1.
4
Click Export, then save the file to your computer as a .json file.

Exporting an Environment (Optional)#

1
Open the Environments tab from the left sidebar.
2
Locate the environment you want to export, click ···, then select Export.
3
Save the environment as a .json file.

Exporting Workspace Data (Data Dump) – Optional#

Postman also offers a Data Dump feature to export your entire workspace. This includes all your Collections, Environments, and Global variables in one .json file.
Here’s how:
1
Select your avatar in the Postman header, then select Settings.
2
Select the Account tab.
3
Select Export Data, then select the data types you want to export (like collections, environments,etc.)
4
Select Request Data Export.
5
When the export is ready, you'll get an email with a link to download the bulk data file. The download will be available for two days, after which it expires.
Note
Data Dumps are mainly used for backups and internal Postman recovery. They’re not recommended for migrating to Apidog. For best results, export Collections and Environments individually.

How to Import Postman Data into Apidog?#

Importing a Collection#

Open the Project Settings panel in Apidog, click Import Data, select Postman, and upload your file.
importing-postman-data.png
You can view all the endpoints under the Collection on the import preview page. To seamlessly migrate, you need to check the environment with the same name as the Collection on the Environment tab, and then click the Confirm button.
After the importing process is completed, you can see the name parameter on the API documentation and the link address in baseUrl in Environment Management section.
When debugging an endpoint, select the corresponding environment. The prefix URL will automatically be appended to the path, just like in Postman.

Importing an Environment (Optional)#

1
In Apidog, go to your Project Settings → Import Data.
2
Choose Postman, then upload the exported Postman Environment .json file.
3
After importing, you can switch to the corresponding environment during endpoint debugging.

Importing Workspace Data/Data Dumps (Optional)#

1
In Apidog, go to your Project Settings → Import Data.
2
Choose Postman, then upload the extracted files or folders.
3
After importing, you can switch to the corresponding environment during endpoint debugging. (Currently, Collection only supports selecting one.)
4
Using Data Dump for data migration is currently not recommended. Instead, we suggest importing the following separately:
Collection: Corresponds to the project and endpoint structure in Apidog
Environment: Corresponds to the environment configuration in Apidog
For a more detailed guide, check out this best practice article: How to Migrate Postman Collections/Environments to Apidog
Modified at 2025-04-18 07:53:08
Previous
Export data
Next
Import OpenAPI (Swagger) spec
Built with