Postman Tutorial
- 1. Introduction to Postman
- 2. Sending Requests & Body Types
- 3. Environments & Variable Scopes
- 4. Collections & Folders
- 5. Writing API Tests & Assertions
- 6. Automated Collection Runner
- 7. Postman CLI: Newman
- 8. Integration with CI/CD Pipelines
- 9. Mock Servers
- 10. API Monitoring & Uptime Alerting
- 11. Collaborative Workspaces
- 12. Generating API Documentation
- 13. Designing APIs (OpenAPI / Swagger)
- 14. Advanced Authorization
- 15. Postman Flows & Best Practices
11. Collaborative Workspaces
API development is rarely a solo endeavor. Frontend engineers, backend developers, security auditors, and product managers all need access to the same API endpoints. Postman **Workspaces** provide a secure, organized collaborative hub to share collections, environments, mocks, and schemas in real-time.
Categories of Postman Workspaces
When creating a workspace, you define its access visibility and collaborative tier:
- Personal Workspace: Accessible strictly to you. Perfect for private learning, playground tests, and individual API exploration.
- Team Workspace: A collaborative directory for your organization. Invited team members can view, edit, and run collections collectively depending on their permissions (Viewer, Editor, or Admin).
- Partner Workspace: A secure bridge allowing external clients, partners, or vendors to collaborate on private collections.
- Public Workspace: Open to the world. Perfect for developer portfolios, public libraries, or open-source developer toolkits.
Version Control in Collections: Forking & Merging
When multiple developers edit the same collection simultaneously, they run the risk of overwriting each other's changes. To solve this, Postman includes built-in version control features inspired by Git:
1. Forking a Collection
If you want to edit a shared collection without affecting the production version, you create a **Fork**:
- Click the three dots next to the collection name and select **Create a fork**.
- Provide a label for the fork (e.g. `feature-payment-updates`) and select the workspace.
- Postman creates a isolated copy of the collection linked back to the original parent.
2. Merging Changes (Pull Request)
Once you have added new requests or updated test scripts inside your fork, you merge those modifications back to the master collection:
- Click the three dots next to your forked collection and select **Merge changes** (or **Create pull request**).
- Postman will compare the files and present a **Visual Diff** showing exactly what was added, modified, or deleted.
- Invite team members to review the changes and post comments.
- Click **Merge All Changes** to update the parent collection in real-time!
Real-Time Presence
Just like Google Docs, when multiple developers are active inside a Team Workspace, Postman displays active user icons in the top navigation bar. You can see who is currently viewing which collection or editing which endpoint, preventing conflicting modifications.