Skip to content

Get started

Rate limits

Burst and steady limits per endpoint, the headers, and what to do after a 429.

Tiers

Each endpoint belongs to one of five tiers. A tier sets two limits that apply at the same time: a burst limit per second and a steady limit per minute. A few write endpoints also have a daily limit. Every reference page shows its own numbers.

TierBurst (per second)Steady (per minute)Endpoints here
XS11539
S360158
M10150116
L7575078
XL3503,50038
PUSH1501,4001

What is counted

  • A private key counts on its own, per endpoint. Two keys for the same account do not share a limit.
  • A person using the app counts per person, with four times the limits, because one page in the app makes several calls.
  • Client endpoints count per account, by public key.

Windows are fixed and follow the clock: every second, every minute and, for daily limits, every UTC day starts a new count.

Rate limit headers

Successful responses tell you where you stand:

http
RateLimit-Limit: 75, 75;w=1, 750;w=60
RateLimit-Remaining: 74
RateLimit-Reset: 1
HeaderMeaning
RateLimit-LimitThe limit, then each window with its length in seconds (w=1, w=60, and w=86400 for a daily limit)
RateLimit-RemainingRequests left in the tightest window
RateLimit-ResetSeconds until that window resets

When you go over

The request is refused with 429 throttled and a Retry-After header in seconds. Wait at least that long before you retry. For bulk work, retry with exponential backoff and some random jitter so parallel workers do not retry at the same moment.