- 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 your Postman app
- 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
Grouping requests in collections
You can group your Postman requests into collections to keep your workspace organized, to collaborate with teammates, to generate API documentation / test suites, and to automate request runs.
Postman lists your collections in the left sidebar, in the Collections tab.
You can open and close collections by clicking them, and favorite (★) to move a collection to the top of the list. You can add sub-folders to create an extra level of nesting with your requests. Use the search text-field to filter through your collections.
You can create a new collection by clicking + New Collection in the left sidebar, the New button > Collection, or the Launchpad that appears when you first launch Postman.
Give your new collection a name—you can click Create straight away if you don't want to specify collection details until later.
You can optionally specify a description for your collection (which will appear in its documentation), authorization config, pre-request and test script code, and any variables you want to share across all requests in the collection.
To see an overview of a collection, open it from the sidebar by clicking ►. You can edit your collection description inline by hovering over the text and clicking the pencil icon.
You can use markdown in your collection descriptions.
You can edit details for your collections at any time using the menu ... > Edit from the sidebar or collection overview.
You can duplicate a collection—however you can alternatively fork it to develop collection versions.
You can add existing requests to collections and can create new requests inside collections. If you have a request open in Postman, click Save (or Save As if you want to move it from another collection). Choose (or create) a collection and click Save.
To add a new request to a collection, in Collections on the left of Postman, open the collection ... menu and choose Add Request. Alternatively open the collection overview, click ..., and create the request from there.
You can also create a request by clicking New > Request.
Give your request a name and optional description, then Save it to the selected collection.
You can also create and save requests from the Launchpad when you have no open requests.
To save a request from your history, select its ... menu in History on the left of Postman, and choose Save Request. Choose a collection and Save.
You can select multiple requests to save from your history by clicking the + button next to the date.
To add a folder to your collection, open its ... menu in Collections on the left of Postman, and choose Add Folder. You can then add requests to the folder either by dragging them over it or using its menu and choosing Add Request.
You can reorder the requests and folders inside a collection by clicking and dragging them.
To delete a collection, in Collections click ... to open its menu and select Delete.
You can recover deleted collections in Postman using Trash. Click
...near the collection search bar and select Open Trash. You can restore the deleted collections or permanently delete them. You can alternatively open the trash from the bottom right corner in Postman.
Recovery options depend on your Postman plan:
- With a free account you can recover collections up to one day old.
- Team accounts can recover collections up to 30 days.
- With Postman Business and Enterprise you can recover collections up to 90 days.
If you are not able to recover a deleted collection, it may have been removed from a workspace rather than deleted. In the web dashboard, select View all collections. If it appears in the list, click Share to move it to a workspace.
If you'd like to revert your collection to a previous state, you can use the activity feed.
You can share your collections to a workspace, by publishing a Run in Postman button on a web page, or by sharing a public link.
You can use collections to power various parts of your API development, testing, and publishing workflows.
- The Collection Runner allows you to run all requests in a collection and build testing workflows into your runs.
- You can define scripts in your collection, and they will run for each request inside it.
- Collection variables allow you to define values to use throughout the requests in the collection.
- You can generate API documentation from a collection and share it publicly as well as adding it to the Postman API Network.
- Attaching a monitor to a collection lets you schedule collection runs.
- If you add examples to your requests, you can use mock servers to return sample data during testing and development.
You can generate collections from API specifications using the Postman API Builder.