- Installation and updates
- Sending your first request
- Navigating Postman
- New button
- Creating the first collection
- Postman account
- Keyboard Shortcuts
- Troubleshooting In-app Issues
- Authorizing requests
- Working with Tabs
- Visualize API responses
- Validating Requests Against Schema
- Generate code snippets
- Using GraphQL
- Making SOAP requests
- Capturing HTTP requests
- Debugging and logs
- Troubleshooting API requests
- Intro to collections
- Creating collections
- Sharing collections
- Commenting on collections
- Managing collections
- Version Control for Collections
- Using Markdown for descriptions
- Data formats
- Working with OpenAPI
- Collaborating in Postman
- Roles and permissions
- Managing your team
- Requesting access
- Team Settings
- Audit logs
- Intro to scripts
- Pre-request scripts
- Test scripts
- Test examples
- Branching and looping
- Postman Sandbox
- Postman Sandbox API reference
- Intro to collection runs
- Starting a collection run
- Using environments in collection runs
- Building workflows
- Running multiple iterations
- Sharing a collection run
- Working with data files
- Debugging a collection run
- Command line integration with Newman
- Integration with Jenkins
- Integration with Travis CI
- Newman with Docker
- Documenting your API
- Authoring your documentation
- Publishing your docs
- Viewing documentation
- Custom documentation domains
- Intro to mock servers
- Setting up a mock server
- Mocking with examples
- Mocking with the Postman API
- Matching algorithm
- Intro to Monitoring
- 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
- FAQs for monitors
- Intro to Workspaces
- Creating Workspaces
- Using Workspaces
- Managing Workspaces
- Viewing changelogs and restoring collections
- The API Workflow
- Managing and Sharing APIs
- Versioning APIs
- Viewing and analyzing APIs
- Validating Elements Against Schema
- Customizing Postman
- Find and Replace
- Purchasing Postman
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Configuring Microsoft AD FS with Postman SSO
- Setting a custom SAML in Azure AD
- Setting up custom SAML in Duo
- Setting up custom SAML in GSuite
- Setting up custom SAML in Okta
- Setting up custom SAML in Onelogin
- Setting up custom SAML in Ping Identity
- Intro to Integrations
- Custom Webhooks
- Microsoft Flow
- Microsoft Teams
- Publishing API documentation
Activity Feed and restoring collections
This page is deprecated. Team Library is only available for versions 5.0 and below.
An activity feed is a list of events that displays updates to Postman data in an interactive interface. You can use the activity feed to keep track of changes to your private and team collections by different users across the team.
The activity feed also lets you rollback a collection and restore it to any previous point in time.
Postman tracks changes to collections and teams.
To review the activity feed at the collection level, expand the arrow (▸) next to the collection to view details.
Under the Activity tab, review a chronological list of activities about the collection.
The activity feed displays who updated the collection, what the updates were, and when they were completed.
Consecutive updates on the same session to the same entity are collated for readability.
To review the activity feed at team level, click the Team Library view and then select the Activity Feed tab.
You can review a chronological list of activities about all collections shared with the team. Similar to the feed at the collection level, the team activity feed displays who updated the collection, what the updates were, and when they were completed.
You can also review the activity feed from the Dashboard.
To see the activity feed, click a collection. Then under the header bar, click "Activity".
The activity feed presents a list of changes to collections that you own and are subscribed to.
The activity feed captures different updates to collections.
These updates include CUD (Create, Update, Delete) operations on collections, folders, and requests.
A consolidated update to a request as seen below provides a diffs view to pinpoint the exact changes.
Note: Postman users with paid plans can view diffs. Other users can track the "who" and "when" in the activity feeds, but not the "what" at this level of detail.
In the collection-level activity feed, Postman users with paid plans can restore their collections to a point in time.
Hovering over the activity displays a Restore link.
Click the Restore link to restore the collection to the point right after this change was applied.
At the top of the activity feed a confirmation indicates the collection has been restored.
Postman users with paid plans can pipe the team's activity feed to a communication channel of your choice with the following integrations: