What is API Versioning?
Keep your team up to date with version control
Easily manage multiple versions of your API, speed up development time, and maintain a single source of true.
Bifurcation and fusion
Create APIs faster by working in parallel.
Shorten development time
- Close gaps in development and speed up development time by working simultaneously on different forks in the same collection.
See the difference to resolve conflicts
- See a summary of the 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 true.
- Easily merge changes into a parent collection to maintain a single true source in your team or organization.
Review History
Gain visibility into your team's progress.
Easily track reviews
- Create and track revisions made to a collection by you or anyone on your team by viewing the change log.
Restore previous versions
- Reversal changes that you did not intend to restore an earlier version of the collection using snapshots.
Review user activity
- See a summary of your team's activity or an individual's activity in the Postman Dashboard, or dive deeper with team-level reports.
Version marking
Keep multiple versions of your APIs, collections, simulators, and monitoring.
Iteating faster
- Work on multiple versions of API elements in parallel so you can interact with elements such as mockery, monitors, and testing faster.
Track version-specific elements
- Keep version control of your collections with a corresponding API version with version tags. Mark a collection to link it to a specific version of the API.
Stay in sync
- Easily manage changes across all API elements with version tags. Simply create a new version of the API and Postman will tell you exactly which elements need to be updated to remain synchronized with the new version.
Use Cases
Find out how Postman enables first API development, automated testing, and developer integration.
First API development
- Release trusted services by creating your API before deploying code.
Exploratory Testing
- Explore the API by sending different types of data to see what values are returned.
Application development
- Eliminate dependencies and reduce production time by making front-end and back-end teams work in parallel.
Developer integration
- Quickly keep consumers up to date on what your API can do and how it works.
Automated testing
- Automate manual tests and integrate them into your CI/CD channel to ensure that any code changes do not interrupt the API in production.
Developer portals
- Publish API documentation to help internal and external consumers adopt their APIs.
System requirements:
- OSX (x64) / Windows (x86 or x64) / Linux (x86 or x64).
