- Introduction
- Installation and updates
- Sending your first request
- Creating the first collection
- Navigating Postman
- Keyboard Shortcuts
- Postman account
- Syncing
- Settings
- New button
- Collaboration
- Troubleshooting In-app Issues
- Customizing Postman
- Find and Replace
- Requests
- Responses
- History
- Troubleshooting API requests
- Debugging and logs
- Authorizing requests
- Cookies
- Certificates
- Capturing HTTP requests
- Interceptor extension
- Proxy
- Generate code snippets
- Making SOAP requests
- Working with Tabs
- Using GraphQL
- Visualize API responses
- Intro to collections
- Creating collections
- Sharing collections
- Managing collections
- Requesting access
- Using Markdown for descriptions
- Examples
- Data formats
- Working with OpenAPI
- Commenting on collections
- Version Control for Collections
- 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
- Working with data files
- Running multiple iterations
- Building workflows
- Sharing a collection run
- Debugging a collection run
- Command line integration with Newman
- Integration with Jenkins
- Integration with Travis CI
- Newman with Docker
- Documenting your API
- Viewing documentation
- Authoring your documentation
- Publishing your docs
- Custom documentation domains
- Intro to Monitoring
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Pricing for monitors
- Troubleshooting monitors
- FAQs for monitors
- Intro to mock servers
- Setting up a mock server
- Mocking with examples
- Mocking with the Postman API
- Matching algorithm
- Notifications
- Introduction to APIs
- Managing APIs
- Sharing APIs and managing roles
- The API Workflow
- Versioning APIs
- Reporting FAQs
- Viewing and analyzing APIs
- What is Postman Pro
- Intro to Enterprise
- Purchasing Postman Enterprise
- Running Postman monitors using static IPs
- 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
- Audit logs
GitLab
Back up and synchronize your Postman Collections on GitLab (an open source Git repository manager) and on any of your custom domains. Your Collections are all tucked in safe and sound with our latest Postman Pro 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 page, find GitLab from Postman's list of 3rd party Integrations for Postman Pro/Enterprise.
-
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 also can 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 the Add Integration button 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.
- 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.
Click Add Integrations.
Now, you can go to your Gitlab domain and view your backed-up collections, as illustrated in the screen below:









