Skip to content
Postman

Limits and quotas ​

Each plan has credits per month and request limits per minute, per hour and per day, counted per organization.

Reading the plans…

Over a limit ​

A request over a request limit gets 429, at no charge. Wait the seconds of the Retry-After header before sending it again; the answer's body says the same number in retryAfter. A limit per day resets at midnight UTC.

When the plan's credits for the month run out, extractions use purchased credits; with no balance, the answer is 402 NOT_ENOUGH_CREDITS and nothing runs.

The X-RateLimit headers ​

Every extraction answer, once the API key is accepted, says how many requests are left before a request limit refuses one, for the limit closest to refusing:

HeaderWhat it says
X-RateLimit-LimitThe size of that limit: per minute, per hour or per day.
X-RateLimit-RemainingThe requests left in it now.
X-RateLimit-ResetThe seconds until X-RateLimit-Remaining goes up; 0 when nothing is counted.

On a 429 they name the limit that refused: X-RateLimit-Remaining is 0 and X-RateLimit-Reset equals Retry-After. A browser can read them on a call from another domain.

The X-Quota headers ​

When the plan's credits for the month pass 80%, the extraction's 201 and 422 answers carry these headers:

HeaderWhat it says
X-Quota-Warninglow from 80% of the plan's credits for the month; high from 90%.
X-Quota-LimitThe plan's credits per month.
X-Quota-UsedThe plan's credits used this month.
X-Quota-RemainingThe plan's credits left this month.
X-Quota-PercentThe share used, with one decimal.

Below 80%, they are not sent. A browser can read them on a call from another domain.