- 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
- The API Workflow
- Managing and Sharing APIs
- Versioning APIs
- Viewing and analyzing APIs
- Validating Elements Against Schema
- 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
Setting up a monitor
Postman Monitoring offers a number of configuration options when creating a monitor, allowing you to seamlessly integrate it into your team's API development workflow.
- Next steps
You can create a Postman monitor using a number of flows both in and outside of the Postman app:
Launchpad is automatically enabled in the Postman app (to disable, click the wrench icon > Settings). To create a monitor, select ... View More > Create a monitor.
- ▶ button: In the Postman app, hover over your collection and click the arrow button ▶ > Monitors > Create a monitor or + Add monitor (if you have an existing monitor).
- ... button: In the Postman app, hover over your collection and select ... > Monitor Collection.
In the Postman app, select History, hover over your request, click ... > Monitor Request.
- Workspace: In your web dashboard, click into your workspace > Monitors > Monitor a collection.
- Collection: In your web dashboard, click into your workspace > Collections > select your collection > ... > Monitor Collection. Alternatively, you can click to open your collection > Monitors > Add Monitor.
You can create a monitor with a POST request to the Postman API. Visit the API docs > Monitors > Create Monitor to learn how to do so.
You will need to give your new monitor a name and designate the collection you would like it to run, as well as the version. You can also add an environment here if you would like your monitor to use one.
From here, you can determine how you'd like to configure your monitor.
You can utilize a number of custom configuration options provided by Postman monitoring.
You can configure your monitor to run as often as you would like, automatically. This could be up to every five minutes for a status page or a basic check once a week on your endpoints.
Frequency affects how quickly your monitoring usage compounds. To learn more about usage limits and overages, see Pricing.
You can allow Postman to auto-select a region for your monitor or you can opt to select your regions manually. Postman offers multiple regions to choose from, enabling you to accurately track uptime and reliability on a global scale, without the need to procure your own regional servers.
Servers in each selected region will run your monitor according to your schedule, counting towards your monitoring usage.
Static IPs are available on Postman Business and Enterprise plans. This option allows you to securely monitor private APIs using a direct channel to Postman.
You will receive daily and weekly summaries of your active monitors in the app and via email.
You can opt out of daily and/or weekly summaries by navigating to your web dashboard, selecting your avatar in the upper-right corner, and clicking Notification Preferences.
When creating a monitor, you can choose to receive email notifications for run failures and errors and define up to five recipients under Show Additional Preferences.
You'll be notified of run failures up to three consecutive times. After three, Postman will wait until your run succeeds to notify you.
You can find detailed information on your monitor results by navigating to your web dashboard, selecting a workspace > Monitors.
You have the option to Retry if run fails. If this is enabled and a failure occurs during a run, Postman will automatically re-run the failed request to avoid false alarms due to transient issues. Postman will still log the initial failure, but will only notify you if the run continues to fail.
If you choose to enable this option, it will affect your monitoring usage and the resulting billing. For example, if a collection of three requests fails on the first request, but retries successfully, the run will count as four total requests.
You can configure a Request timeout if you'd like to make sure all of your requests run within a certain amount of time. By default, requests do not have a timeout value, however each monitor run has a timeout of five minutes. It is not possible to configure this at the request level.
Request timeout may not exceed five minutes (300000ms).
You can add a Delay between requests to your monitor. This will insert a delay between all requests in your collection. To configure this for individual requests, you can add a delay in your pre-request or test scripts with setTimeout().
Delay between requests may not exceed five minutes (300000 ms), however note that five minutes is also the maximum run time for a monitor.
You can use Don't follow redirects to reject URL redirection for requests run via a monitor.
You can Disable SSL validation if you are using self-signed certicates to stop validations of SSL certificates. For more information, see Certificates. To troubleshoot, see Troubleshooting Self-signed SSL Certificate Issues.