Rate limits & usage

Check Settings > Developers > Usage & limits for your account's allowances,
consumption and reset times. There is no single limit shared by every plan.

Rate limits and retries

RateLimit-Limit: effective request-unit limit for the current minute.

RateLimit-Remaining: request units remaining.

RateLimit-Reset: seconds until the current minute resets.

Retry-After: seconds to wait before retrying a 429 or temporary 503.

Respect Retry-After. For other transient failures, retry safe read requests
with exponential backoff and jitter, with a bounded number of attempts.

API capacity add-ons

Capacity add-ons have account-wide per-minute, daily, monthly and concurrent
request limits. Creating additional credentials does not multiply these limits.
Each admitted request consumes one request from both daily and monthly
allowances, regardless of how many records it returns. Requests rejected by
authentication, scope or capacity checks do not consume those allowances;
validation errors and other failures after admission do. A retried request,
including an idempotent replay, is a new request for usage accounting.

For these accounts, RateLimit-Limit and RateLimit-Remaining describe requests
in the sliding minute window. Daily and monthly allowance headers are:

X-API-Daily-Limit, X-API-Daily-Remaining, X-API-Daily-Reset.

X-API-Monthly-Limit, X-API-Monthly-Remaining, X-API-Monthly-Reset.

Daily allowances reset at midnight UTC. Monthly allowances follow the API
add-on's anniversary, including annual purchases, with shorter-month dates
clamped to the last day. Reset headers contain UTC timestamps. Unused included
requests do not roll over. Upgrades preserve usage already consumed; extra
request packs increase only the current month's allowance.

Quota or concurrency exhaustion returns 429; follow Retry-After rather
than repeatedly retrying. Shared infrastructure protections still apply, so
an account allowance does not guarantee uninterrupted throughput. Existing
included API plans remain on their current policy until capacity is configured.

Which headers should I read?

Headers	Meaning
`RateLimit-Limit`, `RateLimit-Remaining`	Effective current minute allowance and remainder
`RateLimit-Reset`	Seconds until the minute window resets
`X-API-Daily-Limit`, `X-API-Daily-Remaining`	Daily allowance and remainder, when metered
`X-API-Daily-Reset`	Daily reset timestamp in UTC
`X-API-Monthly-Limit`, `X-API-Monthly-Remaining`	Monthly allowance and remainder, when metered
`X-API-Monthly-Reset`	Monthly reset timestamp in UTC
`Retry-After`	Seconds to wait before retrying when supplied

Shared header definitions remain in each endpoint's reference for tooling.
For retry behavior, see Safe retries & idempotency.

Rate limits and retries#

API capacity add-ons#

Which headers should I read?#

Rate limits and retries

API capacity add-ons

Which headers should I read?