Rate limits and concurrency

The API has three separate limits, all applied per account. Each one covers a different group of endpoints:

• A per-minute limit on the Aggregation and Current Visitors endpoints (the ones you tend to poll often). Every paid tier is a multiple of 60, so it divides cleanly into requests per second if you want to pace your client (for example, 120 per minute is 2 per second). The limit is still measured per minute, so a full minute's allowance is available within any 60-second window.
• A per-hour limit on the Account, Sites, Events and Milestones endpoints, the management endpoints you call less often.
• A concurrency limit: how many requests you can have in flight at the same time, across all endpoints.

The per-minute and per-hour limits apply to different endpoints, so they're counted separately. A tier's per-hour figure is its own budget for the management endpoints, not the per-minute figure multiplied out.

Every account includes a free allowance. Need more? Upgrade your API plan in your billing settings. Plans are self-serve and apply immediately:

When you exceed any limit we return a 429 with a Retry-After header. Wait that many seconds, then retry. The included per-hour allowance of 500 takes effect on 1 July 2026.