- 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
GitHub
Back up and synchronize your Postman Collections on GitHub (the largest host of source code in the world) and on any of your custom GitHub domains. Your Collections are all tucked in safe and sound with our latest Postman Pro to GitHub Integration.
Setting up a GitHub integration requires you to get a GitHub Personal Access Token and configure how you would like to back up your collections.
Generating a GitHub Personal Access Token
Log in to GitHub.
If you don’t already have a Personal Access Token from GitHub, generate a new one.
We need the repo and the user scope in order to successfully configure the integration.
Once that token is generated, copy it and save it somewhere for future use.

Configuring GitHub Integration
- In the Integrations page, find Github from a list of Postman's 3rd party Integrations for Postman Pro users.
-
Click View Details to see information about Github and how it can back up your Postman Collections to your designated repositories.
You also can click the Configured Integrations tab to set up other integrations, view available integrations for Github, or view all integrations.
The above screen provides you the following two options:
* [Backup your Postman Collections to GitHub](#backup-collections-to-gitHub)
* [Backup your Postman Collections to GitHub on a custom domain](#backup-collections-to-gitHub-on-custom-domain)
Backup Collections to GitHub
- Click the Add Integration button to authorize a backup of your Postman collections.
- Enter your GitHub Personal Access Token and click the Proceed button.
- Once the token is verified, you will be shown the configuration page to configure the integration.
* Select a collection to back up.
* Select the repository.
* Enter the directory where the collection will be pushed. If the directory does not exist, it will be created for you. If you do not specify anything, the default directory will be `Postman Collections`.
* Enter the file name of the collection in the repository.
* Enter the branch where the collection will be pushed. This branch should already exist in your repository. If you do not specify anything, it will be pushed to the default branch of the repository.
-
Click the Add Integration button.
Every change saved to your Postman Collection automatically commits changes to your GitHub repo in real time. Your Collections and code can live together in perfect harmony in the same repository.
Backup Collections to GitHub on custom domain
- Enter your GitHub Personal Access Token, specify your GitHub custom domain and click Proceed.
- In the Backup your Postman Collections page, choose an existing Postman Collection, your GitHub repository, specify a file name for your backup and enter the name of the branch.
- Click Add Integration. Your Collection is pushed to your GitHub 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 GitHub repository in real time. Your Collections and code can exist in the same repository.
You can navigate to your GitHub repository and view your collections, as illustrated in the screen below:









