For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Postman
PricingEnterprise
Contact SalesSign InSign Up for Free
HomeDocs
HomeDocs
      • Overview
      • Schemas
        • Overview
        • Set up a monitor
        • View monitor results
        • Manage monitors
        • Run monitors using static IPs
        • Troubleshoot monitors
        • Monitoring FAQ
Postman API Platform

Product

  • Postman Overview
  • Enterprise
  • Spec Hub
  • Flows
  • Agent Mode
  • API Catalog
  • Fern
  • Postman CLI
  • Integrations
  • Workspaces
  • Plans and pricing

API Network

  • App Security
  • Artificial Intelligence
  • Communication
  • Data Analytics
  • Database
  • Developer Productivity
  • DevOps
  • Ecommerce
  • eSignature
  • Financial Services
  • Payments
  • Travel

Resources

  • Postman Docs
  • Academy
  • Community
  • Templates
  • Intergalactic
  • Videos
  • MCP Servers

Legal and Security

  • Legal Terms Hub
  • Terms of Service
  • Postman Product Terms
  • Security
  • Website Terms of Use

Company

  • About
  • Careers and culture
  • Contact us
  • Partner program
  • Customer stories
  • Student programs
  • Press and media
Twitter iconLinkedIn iconGithub iconYouTube iconInstagram iconDiscord icon
Download Postman
Privacy Policy

© 2026 Postman, Inc.

On this page
  • About Postman Monitors
  • Monitor use cases
  • Monitor FAQs
Postman CollectionsMonitor collections

Monitor health and performance of your APIs in Postman

||View as Markdown|
Was this page helpful?
Previous

Run Postman CLI commands in your CI/CD workflows using GitHub Actions

Next

Set up a monitor in Postman

Built with

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

Postman Monitors enable you to automatically run a collection of API requests from the Postman cloud on a schedule or when triggered by the Postman CLI. You can set up a monitor by selecting a collection and defining how it’ll run. For common scenarios, see monitor use cases.

Configure where and how monitors run

By default, monitors run from the Postman cloud. For more options:

  • Use Private API Monitoring to run monitors from your internal network using runners and the Postman CLI, without exposing your endpoints publicly.
  • Run monitors from static IPs to access APIs behind restricted firewalls.

View and manage monitor activity

After your monitors run, you can view monitor results to analyze performance and debug issues. You can also publish monitor reports to share read-only results with stakeholders outside your workspace. To manage usage, see monitor usage.

For Enterprise teams, you can also get a unified view of your monitors alongside other API health metrics in the API Catalog, which provides centralized monitoring and governance across your organization’s APIs. To learn more about connecting your monitors to the API Catalog, see Set up a monitor.

If you run into issues, see how to 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.