Postman CollectionsMonitor collections

Monitor health and performance of your APIs in Postman

View as Markdown

Postman Monitors enable you to continuously check the health and performance of your APIs. You can create monitors that run requests in selected collections. Requests can run API test scripts, chain together multiple requests, and more. You can also schedule how often Postman runs monitored collections.

You’ll be alerted to any test failures once the monitor is running, so you can identify and address issues before your API’s consumers are affected.

About Postman Monitors

You can set up monitors, enabling you to run a series of requests from the Postman cloud based on a schedule. When creating a monitor, you choose a collection with the requests you want to run. You can learn more about use cases for monitors.

With Private API Monitoring, you can use runners and the Postman CLI to monitor and test your organization’s APIs from your internal network, without publicly exposing your endpoints. Once set up, monitors run in your internal network and the runner sends the results to the Postman cloud. You can also configure monitors to run from static IPs to monitor APIs that are behind a restricted firewall.

You can view results for monitors to learn more about the monitors you’re running. You can also manage your team’s monitor usage, enabling you to track your team’s resource usage and purchase more blocks of monitoring calls.

If you experience a problem with monitors, you can troubleshoot monitors in Postman.

Monitor use cases

Monitors run Postman requests and scripts, enabling you to monitor APIs in a variety of ways. Common use cases include:

  • Detect issues during and after deployments - Run monitors on a schedule or trigger them using the Postman CLI to catch failures or performance regressions early, helping you resolve issues before they impact users.

  • Ensure API health and reliability over time - Continuously check that your APIs are available and responding within acceptable time thresholds across environments.

  • Test critical user workflows - Simulate real-world scenarios by chaining requests together to validate multi-step flows and ensure different parts of your API work together correctly.

  • Run tests across environments and regions - Ensure your APIs behave consistently by running monitors in different environments and geographic regions. (Manually selecting multiple regions requires a paid Postman plan.)

  • Identify potential security issues - Continuously test your APIs for common vulnerabilities by running security checks.

  • Track performance trends over time - Use monitor results to observe changes in response times and reliability, helping you identify patterns and diagnose issues.

For more examples of monitors in action, visit the Postman API Monitoring Examples public workspace to find example collections for some common monitoring use cases. You can collaborate on the collections in the workspace by creating a fork, or customize the collections for your team’s use by exporting and importing them into your internal workspace.

Monitor FAQs

To learn more about configuring monitors in Postman, see the Monitor FAQs.