- Installing and updating
- Navigating Postman
- Sending your first request
- Managing your account
- Syncing your work
- Discovering templates
- Creating your first collection
- Creating a workspace
- Setting up Postman
- Importing and exporting data
- Troubleshooting app issues
- Building requests
- Authorizing requests
- Receiving responses
- Grouping requests in collections
- Using variables
- Managing environments
- Visualizing responses
- Specifying examples
- Using cookies
- Working with certificates
- Generating client code
- Troubleshooting requests
- Scripting in Postman
- Writing pre-request scripts
- Writing tests
- Using the Collection Runner
- Scheduling runs with monitors
- Building request workflows
- Importing data files
- Working with your team
- Defining roles
- Requesting access
- Sharing your work
- Your Private API Network
- Commenting on collections
- Versioning APIs
- Using version control
- Using the API Builder
- Managing and sharing APIs
- Validating APIs
- Monitoring your APIs
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Running Postman monitors using static IPs
- Troubleshooting monitors
- Monitoring FAQs
- Analyzing with reports
- Documenting your API
- Authoring your docs
- Publishing your docs
- Viewing documentation
- Using custom domains
- Publishing templates
- Publishing to the API Network
- Submission guidelines
- Managing your team
- Purchasing Postman
- Configuring team settings
- Utilizing audit logs
- Onboarding checklist
- Migrating data between teams
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Microsoft AD FS
- Custom SAML in Azure AD
- Custom SAML in Duo
- Custom SAML in GSuite
- Custom SAML in Okta
- Custom SAML in Onelogin
- Custom SAML in Ping Identity
- Migrating to the current version of Postman
- Developing with Postman utilities
- Postman API
- Echo API
- Collection SDK
- Postman Runtime library
- Code generator library
- Postman Collection conversion
Importing and exporting data
Postman can import and export Postman data, including collections, environments, data dumps, and globals. Postman can also import non-Postman data in the form of API schemas to help you consolidate your API development workflow.
- Next steps
You can import (e.g. collections) as well as your API specifications directly into Postman.
To import your data into Postman, click Import in the upper-left corner.
You can import your data via files, folders, links, raw text, or GitHub repositories.
You can import Postman data you previously exported, including collections, environments, data dumps, and globals.
To import Postman data, click Import. Select your file or folder, input your link, paste your raw text, or import from GitHub. Postman will automatically recognize Postman data, confirming the name, format, and what the file will import as. Click Import to bring your data into Postman.
Postman no longer supports the collection v1 format and will return an error if you attempt to import a collection in this format. You can convert your collection's format from v1 to v2 to import it into Postman.
You can take the following steps to convert the Postman collection format from v1 to v2.
- In the terminal of your choice, enter the following command to install the Postman collection transformer.
sudo npm install -g postman-collection-transformer
- You can retrieve a list of convert options by running it with the
postman-collection-transformer convert -h
||Outputs usage information|
||Returns a path to the input postman collection file|
||Returns the version of the input collection format standard (v1 or v2)|
||Returns a path to the output postman collection file|
||Returns the version of the output collection format standard (v1 or v2)|
||Prints the output in pretty format|
||Retains the request and folder IDs during conversion (collection ID is always retained)|
||Overwrites the output file if it exists|
- You can convert an individual Postman collection from v1 to v2 by entering the command below.
postman-collection-transformer convert -i <path to input Postman collection file> -o <path where the output Postman file will be downloaded> -j 1.0.0 -p 2.0.0 -P
The resulting collection will be in v2 format and downloaded to your target file path. Check out the Postman Collection Transformer to take a closer look at the collection conversion.
Postman supports the following API specification formats:
To import your API specifications into Postman, click Import. Select your file or folder, input your link, or paste your raw text. Confirm the name, format, and what you would like your data to import as, then click Import to bring your data into Postman.
You can configure your Import Settings, which will differ depending on your API specification.
You can import several API specification files at once. Select the workspace you'd like to import the APIs into, choose whether you want to generate collections from the APIs, configure the details, and click Import.
When importing into a team workspace, you can also choose to add the APIs to the Private API Network.
You must be signed in to a Postman account to use this feature.
You can import data in bulk from a GitHub repository by selecting Import > Code repository > Connect to GitHub.
Confirm your GitHub account and Authorize postmanlabs to access your repositories.
In Postman, select your GitHub organization, repository, and branch, then Continue.
Confirm the files you would like to import into Postman. You can also opt to Generate collection from imported APIs and select what you would like to link this collection as. Click Show advanced settings to control how Postman should generate collections based on your file types, then select Import.
You will receive a confirmation once the import has completed.
You can now view your newly imported files and generated collections in Postman.
You can export your Postman data, including collections, environments, data dumps, and globals, as JSON files. These files can be imported back into any Postman instance, or utilized by Newman, Postman's command-line collection runner.
You can export your collections from Postman by selecting the ... next to the collection, then Export.
You can then select the format you'd like your collection to export as. Click Export to download your newly generated JSON file.
The export to Collection v1 format is no longer supported in Postman.
Learn more about Postman's collection formats.
You can export your environments from Postman by selecting the gear icon in the upper-right corner to open Manage Environments. Click the download symbol next to your environment to download your newly generated JSON file.
You can export a data dump of all of your collections, environments, globals, and header presets in Postman. Select the wrench icon in the upper-right corner to open Settings. Click to open the Data tab, then Download to save the newly generated JSON file of your Postman data.