Learn how to create and manage Postman Collections, use collections in development workflows, apply collection templates, and save multi-protocol requests into collections.
There are several ways to create a new collection:
Select Collections in the sidebar, then select +.
Select New, then select Collection.
With Collections open in the left sidebar, select +.
In an empty workspace, select Create Collection.
You can also create a collection from a template.
To customize and configure a new collection, do the following:
You can turn on autosave to automatically save your changes to collections, requests, and environments. Learn more about autosave.
There are several ways to add existing and new requests to a collection.
To move an existing request to a different collection, do the following:
Alternatively, open the request and select Save As, then choose the collection you want to copy it to.
To move more than one request to a different collection, do the following:
Select the more actions icon next to the collection name.
Select Add Request from the actions menu.
Select the collection, then select Add a request.
Select History in the sidebar.
Select the more actions icon next to the request you want to save.
Select Save request.
Choose the collection to add the request to, then select Save.
Alternatively, select + next to the request.
From the list of collections in your workspace, you can:
You can also add sub-folders to create extra levels of nesting for the collection's requests and examples.
You can also select the collection and press Delete on your keyboard.
If a deleted collection is larger than 30 MB, you won't be able to recover it. To avoid this, you can split the collection into smaller pieces before deleting it, or back up the collection first.
Select the more actions icon next to the collection search bar.
Select Open Trash.
Alternatively, select Trash from the Postman footer.
In the Trash page, select the restore icon next to the collection you want to recover.
Deleted collections that are larger than 30 MB can't be recovered.
Recovery options depend on your Postman plan:
If a collection that you expected to be in the Trash isn't there, it may have been removed from a workspace rather than deleted. If the collection appears in another workspace, you can move it by selecting Share.
To share a collection with other users, you can:
Tagging collections is available on Postman Enterprise plans. You can apply shared tags to workspaces, collections, and APIs. Tags must be between two and 64 alphanumeric characters, starting with an alphabetic character, and contain only dashes and no spaces. You can add up to five tags.
Adding shared tags to collections enables you to organize and search for collections.
Once you add tags to the collection, you can select a tag to open search results associated with the tag in a new tab.
To learn more about searching using tag names in Postman, see Search Postman. You can also search using tag names in the Private API Network when searching elements in the network, elements to add to the network, and elements to request to add to the network.
To add tags to a collection, do the following:
Select Collections in the sidebar.
Select a collection.
Select the Tags section to edit it.
Select an existing tag or enter a new tag. If you're adding a new tag, enter the new tag name and then select Create "tag-name".
Select the area outside of the Tags section to save your changes.
To remove tags from a collection, do the following:
Select Collections in the sidebar.
Select a collection.
Select the Tags section to edit it.
Select the close icon next to a tag.
Select the area outside of the Tags section to save your changes.
When you watch a collection, Postman notifies you when a workspace team member makes changes to the collection, including adding a new request, modifying the existing requests, adding or updating variables, editing pre-request scripts or tests, and adding or deleting a folder. You can watch a collection that you own, as well as collections in any public workspace.
To watch a collection, do the following:
To view notifications about what has changed in a collection you watch, do the following:
Select the notifications icon in the Postman header to view the notification. Select View changelog to view the collection's changelog.
You will also receive an email with the information regarding who made the change, what the change was, and when it was made. Select View changelog in the email to access the full changelog in Postman.
If you create a collection and change it from the same Postman account, you won't receive notifications for any changes you make to that collection.
You can fork collections in your own workspace to develop collection versions.
Alternatively, select the fork icon from the collection overview.
To learn more about using comments to collaborate on collections and requests, go to Comment on collections, folders, and requests.
To revert your collection to an earlier state, do the following:
Select the changelog icon on the right.
Select a session to expand it.
Select the more actions icon next to the change you'd like to restore your collection to, then select Restore to this change.
Restoring a collection from the changelog reverts it to the point immediately after your selected change occurred.
From the right sidebar:
Collections can power various parts of your API development, testing, and publishing workflows.
Not sure where to start when creating a collection? Instead of starting from scratch, you can create a collection from a template. Several collection templates are available for getting started with integrations, API documentation, conditional workflows, or data visualization.
There are several ways to create a collection from a template:
You can also save multi-protocol requests, such as WebSocket and gRPC requests, into collections.
Because multi-protocol requests have different features than HTTP requests, when they're saved to a collection, it causes the collection to be in a "beta" state with certain limitations.
When in this state, a collection can only contain WebSocket or gRPC requests, and not HTTP requests. Some features related to collections also aren't supported.
Last modified: 2023/04/10
Additional resources
Videos
Blog posts