- Introduction
- Installing and updating
- Navigating Postman
- Sending your first request
- Managing your account
- Syncing your work
- Discovering templates
- Creating your first collection
- Creating a workspace
- Setting up your Postman app
- Importing and exporting data
- Troubleshooting app issues
- Building requests
- Authorizing requests
- Receiving responses
- Grouping requests in collections
- Using variables
- Managing environments
- Visualizing responses
- Specifying examples
- Using cookies
- Working with certificates
- Generating client code
- Troubleshooting requests
- Using the Collection Runner
- Scheduling runs with monitors
- Building request workflows
- Importing data files
- Working with your team
- Defining roles
- Requesting access
- Sharing your work
- Your Private API Network
- Commenting on collections
- Versioning APIs
- Using version control
- Using the API Builder
- Managing and sharing APIs
- Validating APIs
- Monitoring your APIs
- 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
- Monitoring FAQs
- Analyzing with reports
- Documenting your API
- Authoring your docs
- Publishing your docs
- Viewing documentation
- Using custom domains
- Publishing templates
- Publishing to the API Network
- Submission guidelines
- Managing your team
- Purchasing Postman
- Billing
- Configuring team settings
- Utilizing audit logs
- Onboarding checklist
- Migrating data between teams
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Microsoft AD FS
- Custom SAML in Azure AD
- Custom SAML in Duo
- Custom SAML in GSuite
- Custom SAML in Okta
- Custom SAML in Onelogin
- Custom SAML in Ping Identity
- Migrating to the current version of Postman
GitLab
Integrations are available on Postman Team, Business, and Enterprise plans.
Back up your Postman Collections to GitLab, an open source Git repository manager, with the Postman to GitLab integration.
Setting up a GitLab integration requires you to get a GitLab Personal Access Token and configure how you would like to back up your collections.
Generating a GitLab Personal Access Token
Log in to GitLab.
If you don’t already have a Personal Access Token from GitLab, generate a new one.
Save the generated token to use later.


Configuring a backup for Postman Collections in GitLab
- In the Integrations tab for your workspace, select GitLab from the list of third party integrations.

-
Click View Details to see information about GitLab and how it can back up your Postman Collections to your GitLab projects or self-hosted domains.
Note: You can also click the Configured Integrations tab to set up other integrations, view available integrations for Gitlab, or view all integrations.
The above screen provides you the following two options:
Backup your Postman Collections to GitLab
- Click the Add Integration button to enter your Gitlab token to start the integration.

- Enter your GitLab Personal Access Token and click Proceed.
- In the Backup your Postman Collections page, choose an existing Postman Collection and your GitLab Project, enter a filename for your backup.
-
Click the Add Integration button. Your Collection is pushed to your GitLab project under the filename that you specified and saved as a single JSON file.
Now every change that is saved to your Postman Collection automatically commits changes to your GitLab project in real time. Your Collections and code can exist in the same repository.
In "Advanced Options" you can enter a custom directory name or leave "Postman Collections" as the default. You can specify a branch for commit or the default branch of the repository will be used.
Backup your Postman Collections to GitLab on a custom domain

- Click Add Integration to enter your GitLab token to start the integration.
-
Enter your GitLab Personal Access Token, specify your Gitlab custom/self-hosted domain and click Proceed.
Static IP Support
If your network is behind a firewall that requires whitelisted IP addresses, you will need to use a static IP address to enable collection backups to GitLab on custom domains.
Contact your IT team to whitelist the following static IP in your firewall to enable collection backups GitLab:
- US East:
3.212.102.200
Once you whitelist this IP address, calls for this integration will be able to connect to your network and allow the integration to work as expected.
- US East:
- In the Backup your Postman Collections page, choose an existing Postman Collection and your GitLab Project, enter a filename for your backup.
- Click Add Integration. Your Collection is pushed to your GitLab project under the directory that you specified and saved as a single JSON file. This is illustrated in the following screen:

Now every change that is saved to your Postman Collection automatically commits changes to your GitLab project in real time. Your Collections and code can exist in the same repository.

In "Advanced Options" you can enter a custom directory name or leave "Postman Collections" as the default. You can specify a branch for commit or the default branch of the repository will be used. Make sure you have write access to the branch you are trying to push your changes.
Note that the branch you want to back up your collection to must already exist.

Click Add Integrations.
Now, you can go to your Gitlab domain and view your backed-up collections, as illustrated in the screen below:
