Checking one endpoint tells you that endpoint answered. It does not tell you a user can actually sign in and then read their data, which is the thing that breaks. Configure two requests, pick a method and auth for each, and this provisions a real monitor that runs them in order: the token step 1 returns is captured into a collection variable and sent as step 2 authorization. The first run is triggered immediately, then it runs every minute — sign up to keep it running continuously and get alerted on failures.

A multi-step monitor chains two or more API requests into a single test. Instead of checking one endpoint in isolation, it validates a full user journey (like sign in, then fetch data) and reports on whether the whole path works end to end.

Add authentication to the first request. The token from the Step 1 response is stored as a variable and automatically passed to Step 2's Authorization header. No manual copying required.

Yes. Any value in the Step 1 response (auth tokens, IDs, timestamps) can be extracted and used in Step 2's URL, headers, or body. Step 2 updates automatically when Step 1 changes.

A single-endpoint check tells you whether one URL is up. A multi-step monitor tells you whether your actual user flow works. If sign-in succeeds but fetching data fails, a single check misses it; a multi-step monitor catches it.

This tool runs in the current session only, to monitor your APIs continuously and get alerted on failures, you can use Postman Monitors.

Not supported in this tool. Postman Monitors gives you assertions on response headers, body content, response time thresholds, and custom Postman scripts.

Not supported here. Postman Monitors sends alerts via email, Slack, PagerDuty, and custom webhooks when any step of a monitored workflow fails.

No signup, no credit card. First result runs in seconds. Sign in only if you want to save the monitor, schedule it, or receive alerts.