Postman monitoring pricing: what Postman API monitors cost per endpoint
Postman bills monitors by the request, and collection size, regions, auth calls, retries and interval all multiply it. Enter your schedule and the calculator prices the seats and the 50,000 request blocks together.
Postman monitoring cost calculator
LiveList prices in USD from Postman's own pricing page, 30 day month. Paid usage is priced in whole $20 blocks of 50,000 requests. Solo and Free are single user plans, so the seat count is ignored there.
How much does Postman monitoring cost?
Postman monitoring is billed by request, not by monitor. Every paid plan, from the $9 Solo seat to Enterprise at $49 per user, includes the same 10,000 monitoring requests per team per month, and usage above that costs $20 per 50,000 requests, which is $0.40 per 1,000. Ten thousand requests is enough for exactly one endpoint checked every five minutes from one region. The second endpoint pushes you into paid usage, and at one-minute checks, which only Enterprise allows, each endpoint consumes roughly one $20 block a month on its own.
So the Postman bill has two parts that behave in opposite ways. The seat line scales with people and ignores how much you monitor. The monitoring line scales with requests and ignores how many people you have. Most pricing write-ups quote only the seat line, which is why a team can budget $19 a user and still be surprised by the invoice once monitors go from hourly to every five minutes.
Postman plans and monitoring allowance
| Plan | Annual | Monthly | Requests |
|---|---|---|---|
| Free | $0 | $0 | 1,000 |
| Solo | $9 | $12 | 10,000 |
| Team | $19 per user | $23 per user | 10,000 |
| Enterprise | $49 per user | $59 per user | 10,000 |
Requests are per team per month and expire at the end of the billing period. Beyond them: $20 per 50,000.
Postman's 10,000 requests cover exactly one endpoint at five-minute checks
A 30 day month has 43,200 minutes. A monitor that runs every five minutes runs 8,640 times, and if the collection holds one request and runs from one region, that is 8,640 requests. It fits inside the 10,000 allowance with 1,360 to spare. Even a 31 day month, at 8,928, still fits.
The second endpoint does not. Two single request monitors at five minutes need 17,280 requests, which is 7,280 over the allowance and triggers the first $20 block. That block then carries you a long way, up to roughly six endpoints at five minutes, so the real shape of Postman's monitoring bill is a step every time you add about six endpoints, not a smooth per endpoint rate.
Slowing the schedule stretches the allowance proportionally. At every 15 minutes three endpoints fit, and at hourly checks thirteen do. That is why teams who treat Postman monitors as scheduled contract tests rarely pay for monitoring at all, while teams who try to use them as an outage alarm pay from the second endpoint onward.
Endpoints that fit, one region, one request each
| Interval | Per endpoint | Inside 10,000 |
|---|---|---|
| 1 minute | 43,200 | None |
| 5 minutes | 8,640 | 1 |
| 10 minutes | 4,320 | 2 |
| 15 minutes | 2,880 | 3 |
| 30 minutes | 1,440 | 6 |
| 1 hour | 720 | 13 |
On Free the allowance is 1,000, which fits one hourly endpoint and nothing faster.
What counts as a request in a Postman monitor
Postman's documentation counts one request in one region as one monitoring call, then applies every multiplier below on top. They stack, so a realistic monitor is rarely one request per run.
| Multiplier | How Postman counts it | Effect |
|---|---|---|
| Each request in the collection | A collection of 5 requests is 5 requests per run, not one | x5 for a 5 request collection |
| Each region | Running the same monitor from 3 regions triples every run | x3 for 3 regions |
| Authorization requests | A token request before each check is billed like the check itself | x2 on a single endpoint |
| Retries | A retried request counts again. Postman's own example: 3 requests, first one retried, bills as 4 | +1 per retry |
| Frequency | Five minutes is 8,640 runs a month. One minute is 43,200 | x5 moving from 5 to 1 minute |
The authorization line is the one that surprises people. If each run fetches a token before calling the endpoint, a single endpoint monitor is two requests per run, and five of them at five minutes go from 43,200 requests (one block) to 86,400 (two blocks). Reusing a long-lived token from an environment variable halves that line. The same logic applies to setup requests that seed data before the real assertion: they are billed exactly like the check you care about.
Postman monitor cost for eleven common schedules
The monitoring line only, after the 10,000 included requests, in whole $20 blocks. Add your seats on top. Every row was computed from the counting rules above, 30 day month.
| Schedule | Requests a month | $20 blocks | Monitoring line |
|---|---|---|---|
| 1 endpoint, every 5 min, 1 region | 8,640 | 0 | $0 |
| 2 endpoints, every 5 min, 1 region | 17,280 | 1 | $20 |
| 5 endpoints, every 5 min, 1 region | 43,200 | 1 | $20 |
| 10 endpoints, every 5 min, 1 region | 86,400 | 2 | $40 |
| 10 endpoints, every 5 min, 3 regions | 259,200 | 5 | $100 |
| One 5 request collection, every 5 min, 3 regions | 129,600 | 3 | $60 |
| Ten 5 request collections, every 5 min, 1 region | 432,000 | 9 | $180 |
| Ten 5 request collections, every 5 min, 3 regions | 1,296,000 | 26 | $520 |
| 1 endpoint, every minute, 1 region (Enterprise) | 43,200 | 1 | $20 |
| 20 endpoints, every minute, 1 region (Enterprise) | 864,000 | 18 | $360 |
| 20 endpoints, every minute, 3 regions (Enterprise) | 2,592,000 | 52 | $1,040 |
At one-minute checks the arithmetic becomes simple: one endpoint in one region is 43,200 requests, and a $20 block is 50,000, so each endpoint costs close to one block. Twenty endpoints come to 18 blocks rather than 20 only because the 10,000 included requests and the rounding absorb a little. Add two more regions and the same twenty endpoints need 52 blocks, $1,040 a month, before a single Enterprise seat.
The allowance is per team, so it shrinks per seat as you grow
Postman's pricing table lists API monitoring as "per team, per month". The number is 10,000 on Solo, Team and Enterprise alike. A single developer paying $9 a month and a 50 person Enterprise organization paying $2,450 a month receive the identical monitoring allowance.
Spread across seats, that works out to 400 requests per paid seat on a 25 person Team plan. A single endpoint at five minutes burns 288 requests a day, so each seat's share covers under a day and a half of one check. Upgrading to Enterprise for SSO, governance or the one-minute interval buys no monitoring capacity at all.
None of this is hidden. It simply means you cannot reason about Postman monitoring from the seat price, and a growing team should expect the monitoring line to grow independently of headcount. If your seat count is set by the developers who build in Postman, but the monitoring need is set by production, the two will drift apart.
Same 10,000 requests, very different seat bills
| Team | Annual | Monthly | Per seat |
|---|---|---|---|
| Solo, 1 person | $9 | $12 | 10,000 |
| Team, 5 people | $95 | $115 | 2,000 |
| Team, 10 people | $190 | $230 | 1,000 |
| Team, 25 people | $475 | $575 | 400 |
| Enterprise, 50 people | $2,450 | $2,950 | 200 |
Seat cost per month. "Per seat" is the monitoring requests each paid seat's share works out to.
Why pricing guides quote $0.75, $200 and $20 for the same thing
Search for Postman monitoring pricing and you will find three different numbers, often in the same article. They come from two eras. In July 2018 Postman announced that its monitoring block would shrink from 500,000 requests for $200 to 50,000 requests for $20. Both are $0.40 per 1,000, so the rate did not change, only the size of the commitment. The same announcement described a pay as you go rate of $0.75 per 1,000.
Postman's current pricing page prints one monitoring price: $20 per 50,000 requests per team per month. The $200 block no longer appears anywhere, and the $0.75 rate is not printed on the page today. We price everything here in $20 blocks and show the 2018 rate only as a sensitivity. If your invoice shows the higher rate, buying blocks in advance is what brings you back to $0.40.
Postman's older documentation also gives a worked example that settles how the allowance is applied: two 500,000 blocks and 1,200,000 requests billed as $542.50. That total only reconciles if the 10,000 included requests are deducted first, leaving 190,000 at $0.75. Our calculator applies the allowance the same way. Priced at today's $20 blocks, the same month would be 24 blocks, $480.
The three numbers, reconciled
| Figure | Per 1,000 | Status |
|---|---|---|
| $200 per 500,000 | $0.40 | Retired in 2018 |
| $20 per 50,000 | $0.40 | Current pricing page |
| $0.75 per 1,000 | $0.75 | 2018 pay as you go, not printed today |
At $0.75 the ten collection example above would cost $316.50 instead of $180, which is why the distinction matters.
Postman monitors compared with a dedicated uptime monitor
These are not the same product, and the table says where each one wins. The point is the billing unit: Postman charges for every request a schedule makes, and we charge for the monitor regardless of how often it runs.
| Postman monitors | Uptimehub | |
|---|---|---|
| What a check is | A full collection run with JavaScript test scripts and chained requests | One HTTP request with status code, body keyword and latency assertions |
| Billing unit | Requests, multiplied by collection size, regions, auth calls and retries | Monitors. Frequency and regions do not change the price |
| Fastest interval | Every 5 minutes, every minute on Enterprise only | Every minute on Starter, every 30 seconds on Pro and above |
| Regions | Chosen per monitor, each one billed | 6 regions on every monitor with cross-region retry |
| Seats | Per user on Team and Enterprise | Not metered |
| Status page | Not included | Branded status page on every plan |
| 20 endpoints every minute | Enterprise seat plus 18 blocks: $419 a month on one seat, monthly billing | Starter, $12 a month billed monthly |
| Where it wins | Contract tests you already wrote, multi-step flows, response schema checks | Always-on outage detection and alerting at a flat price |
Keep Postman monitors for
Contract and regression checks your team already wrote as collections. Run them hourly or every few hours, where the included 10,000 requests go a long way, and let them catch a changed response schema or a broken multi-step flow.
Use a flat priced monitor for
Knowing within a minute that an endpoint is down or slow, from several regions, with alerts routed to the person on call. That is the schedule Postman bills most heavily, and the one a per monitor price absorbs for nothing extra.
Where we are not the answer
We check one request per monitor with status code, body keyword, latency and header assertions. If you need chained requests with scripted tests every minute, look at a code based check tool, and compare it in our API monitoring tools comparison.
If the job is outage detection on your API, our API endpoint monitoring checks every minute on Starter and every 30 seconds on Pro, from 6 regions, and 20 monitors cost $12 a month on monthly billing. The same schedule priced as Postman monitors is 18 blocks plus an Enterprise seat, $419 a month. You can see the whole ladder on plans and pricing.
Where these numbers come from
Seat prices, the per team monitoring allowance and the $20 per 50,000 rate were read from postman.com/pricing in USD, with annual and monthly billing both checked. The counting rules come from Postman's documentation on monitor usage, and the interval limits and retry behavior from its monitor setup documentation. The 2018 block change is from Postman's own blog. The arithmetic is ours and reproduces from those inputs.
Three things are deliberately not asserted. Postman does not publish whether usage beyond the allowance is billed in whole 50,000 blocks or prorated, so the tables use whole blocks, which is the upper bound, and a prorated bill would be at most $20 lower. Enterprise buyers can negotiate, so the $49 and $59 seat figures are list, not what large accounts pay. And we do not claim the $0.75 rate is dead, only that the current pricing page does not print it.
Postman monitoring pricing questions
How much does Postman monitoring cost?
Postman monitoring costs $20 per 50,000 requests per team per month once you use up the included allowance, which is 10,000 requests on every paid plan and 1,000 on Free. That is $0.40 per 1,000 requests. You also pay for at least one Postman seat: $9 a month on Solo, $19 per user on Team and $49 per user on Enterprise, billed annually.
How many monitoring requests does Postman include?
1,000 requests per month on the Free plan and 10,000 per month on Solo, Team and Enterprise. The allowance is per team, not per user, so a 50 person Enterprise team gets the same 10,000 requests as one person on Solo. Unused requests do not roll over to the next month.
What counts as a request in a Postman monitor?
Every request in the collection, in every region the monitor runs from, on every scheduled run. Requests needed for authorization count too, and a request that is retried after a failure counts again. A 5 request collection run every 5 minutes from 3 regions uses 129,600 requests a month, which is 3 blocks, or $60.
What happens when you run out of Postman monitoring requests?
On the Free plan your monitors pause for the rest of the billing period, so you lose monitoring without a warning at the moment you most need it. On paid plans overage is switched on by default and additional usage is billed. If your Billing Admin switches pay as you go off, paid monitors stop on schedule too.
Can Postman monitors run every minute?
Only on Enterprise. Every other plan has a minimum interval of five minutes. One endpoint checked every minute from one region uses 43,200 requests a month, so on Enterprise each endpoint effectively costs about one $20 block a month, plus the $49 or $59 per user seat the interval requires.
Is the $0.75 per 1,000 Postman overage rate still current?
It is not printed on Postman's current pricing page. The figure comes from Postman's 2018 announcement, which described $0.75 per 1,000 as pay as you go and $0.40 per 1,000 as the block rate. Today the pricing page publishes one monitoring rate, $20 per 50,000 requests. Check your own billing dashboard to see which applies to your account.
Is Postman monitoring a good uptime monitor?
It works, but it is an expensive way to do it. Postman meters every request, region and retry, and the included 10,000 requests cover one endpoint at five minute checks. A dedicated uptime monitor charges per monitor instead, so checking 20 endpoints every minute costs $12 a month here, against 18 blocks plus an Enterprise seat at Postman.
Should I use Postman monitors or a separate uptime monitoring tool?
Use both if you have contract tests worth running, and keep them apart. Postman monitors are strong at running the collections your team already maintains on a slow schedule. Outage detection needs a fast interval, several regions and alert routing, which is the combination Postman bills most heavily. Most teams run the collection hourly and let a flat priced monitor catch outages.
Does the Postman free plan include API monitoring?
Yes, 1,000 requests a month, which fits one endpoint checked hourly from one region (720 requests) and nothing faster. A check every 30 minutes needs 1,440, so the monitor pauses around day 21 of the month. Free is also limited to one user, so nobody else on your team sees the results.
Check every endpoint every minute without counting requests
Each monitor is one flat unit, checked from 6 regions, with retries, alerts and a branded status page included and no charge per seat. 20 monitors is $12 a month, 100 is $39.
Related breakdowns
Postman Team pricing by team size
What 5, 10 and 25 person teams pay for seats, SSO and monitoring, monthly and annual.
Best API monitoring tools
Uptime tools, code first tools and observability suites compared on price and fit.
Synthetic monitoring pricing
Per run pricing across Datadog, Checkly, New Relic and others, and how frequency multiplies it.
Grafana Cloud synthetic monitoring pricing
Another execution metered model, where 59 to 61 seconds of run time doubles a bill.
API endpoint monitoring
Status code, body and latency assertions on every endpoint, every minute, from 6 regions.
Uptime monitoring pricing compared
The wider market side by side, where the billing model matters more than the headline number.