- 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
- Introduction to APIs
- The API Workflow
- Managing APIs
- Sharing APIs and managing roles
- Versioning APIs
- Viewing and analyzing APIs
- Validating Elements Against Schema
- Reporting FAQs
- 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
Collaborating in Postman
Postman allows all users to collaborate with their teams through Team Workspaces. Using this feature, you can easily collaborate and share your collections, environments, integrations, history, mocks, monitors, and more.
Free collaboration is available in version 6.2 and above.
- Next steps
Create a Team Workspace by inviting a team member to join a personal workspace or create one using the app or web dashboard.
In the app, select Invite.
Enter the email address of the individual you’d like to invite to your team workspace, click Add > Invite to team.
The individual will be added to the team once they accept their invitation.
"My Workspace" is a default workspace created by Postman. This workspace is different from other personal workspaces as it cannot be shared with anyone. When you invite a teammate to join another personal workspace, Postman converts it into a team workspace.
Select your current workspace in the app to open the workspace menu, then click Create New.
Specify a name, a summary, and select Team for type, then invite members to your newly created shared workspace.
Enabling team discovery encourages collaboration and eases the onboarding process by allowing users accessing Postman with their company email address to request to join pre-existing teams within their organization.
You can enable team discovery in the web dashboard by selecting Team > Settings, or in the app by selecting Team > Team Settings.
When you log in to the Postman web dashboard using a verified email address for your company or organization, you can see available teams to join by selecting your avatar > Your Team.
You will see a list of available teams within your org. Select any team, then Request to join.
The team administrator will receive a notification that you’ve asked to join the team. Once they approve your request, you will be able to access the team and collaborate on API projects within it.
You can check your usage limits within the Postman app as well as in the web dashboard. Free users can select the drop-down menu to the right of Upgrade in the app. Paid users can access the menu by selecting a team name.
The usage menu allows you to review limits for APIs, shared requests and history, mocks, monitors, and public documentation. Click Resource Usage to view your usage period.
Postman archives collections when a free team's collaboration exceeds usage limits. Archived collections cannot be collaborated on, however they are still accessible to users. You will receive an in-app notification when a collection is archived.
Postman chooses which collection(s) to archive based on last edit date. The collections that have gone the longest without a revision will be archived in order to bring your team within usage limits.
Postman indicates the number of archived collections at the bottom of the left sidebar.
To recover archived collections, select Archived Collections.
You will then be able to select Download to retrieve your archived data.
Alternatively, you can download your archived data directly within the Postman App. To learn how, refer to Settings.
For a more in-depth introduction to workspaces and how they can help organize your API development, check out Intro to Workspaces.