How to Fork and Merge Workflows for Partner API Collaboration

Quick Overview

Postman Partner Workspaces facilitate secure, cross-company API collaboration by allowing API publishers to invite external partners with specific roles (Manager, Lead, Partner) to shared workspaces, ensuring controlled access and enabling collaborative development, testing, and communication through features like integrated commenting and API contract testing snippets.

Key Points: Partner Workspaces are designed for cross-company collaboration, enabling multiple stakeholders from different organizations to work together on APIs within a single shared Postman workspace (0:03). Key benefits include faster integrations via shared collections/examples, a single source of truth for API schema and documentation, and safer handoffs through role-based access control (0:50, 0:59, 1:07). Three primary roles govern access: Partner Manager (admin-like rights for external partners), Partner Lead (admin on the partner's side who can add other Partners), and Partner (the standard invited member) (3:19, 3:31, 3:41). API publishers invite partners via email, and upon accepting, partners select an existing team or create a new one to collaborate within (7:09). Collaboration is enhanced through in-line commenting on specific requests or scripts, allowing for direct feedback, such as suggesting contract tests (4:08, 5:43). The multi-partner mode restricts partners from seeing each other's work, ensuring privacy when collaborating with multiple organizations in one workspace (8:13). API publishers can keep partners informed of changes via the 'Updates' tab, linking specific resources like requests or schemas to the announcement (8:21, 8:50).

Context: This video tutorial, presented by Gbadebo Bello, a Developer Advocate at Postman, explains how to leverage Postman's Partner Workspaces feature to manage secure and transparent collaboration between an API publisher (like 'Company A') and external partners (like 'John Doe' from 'Company B'). The core focus is on setting up these workspaces, defining access roles, and using communication tools to keep all collaborating parties synchronized on API development and changes.