Rate limits
API v2 has two kinds of limit. A token bucket counts requests and units per minute. A concurrency limit counts the jobs that run at the same time. The Limits page of Dash shows your tier and the current use.
Tiers
Live and test each have their own buckets and concurrency slots, so a test job never uses a live slot.
Units are the metered amounts of a job, for example pages. They are the values in usage.units.
Test keys always have the test tier limits, but their jobs use real paperwork credits.
A key with a rate cap, or a trust with a requests limit, has its own requests bucket inside the organization limits.
Headers
Every admitted or refused answer has these headers:
The units headers are absent when the units limit does not apply. A 404 tenant_not_found has no rate-limit headers.
Refusals
A refused request does not use rate budget. A job in needs_input holds no slot.
A units bucket needs a positive balance to admit a job. The job takes its real units from the bucket when it ends.
Concurrency classes
How the limits work
The buckets live in memory, one per organization and environment. A deploy can refill a bucket. Do not treat a refill as a higher limit.
Your plan sets the tier. To ask for higher limits, contact CloudRaker from the Limits page.