Rate limits & usage

Open Settings → Integrations & Tools → Developers and select Usage & limits. Request allowances are shared across your account's API credentials; there is no single limit shared by every plan.

If the tab shows Included API access, the account uses its existing API limits. Daily and monthly request tracking appears when a capacity add-on is assigned. Where capacity tracking is available, review the displayed allowances, consumption and reset times. Use Refresh to reload the displayed information.

Rate limits and retries

• RateLimit-Limit: current minute allowance.

• RateLimit-Remaining: current minute allowance remaining.

• RateLimit-Reset: the server-reported reset interval in seconds.

• Retry-After: seconds to wait before retrying when supplied.

RateLimit-Limit and RateLimit-Remaining count requests for capacity add-ons. Included API access can count request units, with some endpoints using several units per call. Check the endpoint reference and your account policy.

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 original anniversary date and time in UTC, 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. Shared infrastructure restrictions also apply. Included API plans keep their existing policy until capacity is configured.

Which headers should I read?

Read these headers when present. Requests rejected before account-capacity admission can omit account usage headers. Shared infrastructure restrictions can apply even when your account has allowance remaining.

For retry behavior, see Safe retries & idempotency.