Forking and Merging
Build APIs faster by working in parallel.
Shorten Development Time
Close gaps in development and speed up development time by working simultaneously on different forks of same collection.
View the Diff to Resolve Conflicts
View a summary of differences between a fork and its parent to resolve conflicts when conflicting changes are made to the same request, folder, or example at the same time.
Maintain a Single Source of Truth
Easily merge changes to a parent collection in order to maintain a single source of truth across your team or organization.
Gain visibility into your team's progress.
Easily Track Revisions
Create and track revisions made on a collection by you or anyone on your team by viewing the changelog.
Restore Previous Versions
Rollback changes you didn't intend by restoring a previous version of the collection using snapshots.
Review User Activity
View a summary of your team activity or an individual’s activity on the Postman Dashboard. Or dive deeper with team-level reports.
Maintain multiple versions of your APIs, collections, mocks, and monitors.
Work on multiple versions of your API elements in parallel so you can iterate on elements like your mocks, monitors, and tests faster.
Track Version-Specific Elements
Maintain versioning of your collections with a corresponding API version with version tags. Tag a collection to link it to a specific API version.
Stay in Sync
Easily manage changes across all API elements with version tags. Just create a new API version and Postman will tell you exactly what elements need to be updated to stay in sync with the new version.
Discover how Postman enables API-first development, automated testing, and developer onboarding.
Release reliable services by building your API before deploying code.
Automate manual tests and integrate them into your CI/CD pipeline to ensure that any code changes won't break the API in production.
Quickly get consumers up to speed on what your API can do and how it works.
Eliminate dependencies and reduce time to production by having front-end and back-end teams work in parallel.
Explore the API by sending it different kinds of data to see what values are returned.
Publish API documentation to help internal and external consumers adopt your APIs.