Rate Limiting

Every API key is subject to per-key limits:

• short — 60 requests per second.
• medium — 120 requests per 60 seconds.

A single burst of up to 60 requests is absorbed; sustained traffic over 120/min starts returning 429.

Headers on every response

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 59
X-RateLimit-Reset: 1745169024

The headers reflect whichever tier is currently tightest — on most requests that's short (60/s), so Limit reads 60. Once sustained traffic pushes the medium tier's remaining budget below short's, the headers switch to Limit: 120. There is always exactly one set of headers per response: the one closest to tripping.

X-RateLimit-Reset is a Unix timestamp (seconds) indicating when the tightest window resets.

429 response

{
  "error": {
    "code": "RATE_LIMITED",
    "message": "Too many requests — retry after 42 seconds",
    "details": { "retry_after_seconds": 42 }
  }
}

The standard Retry-After: 42 header is also set. Respect it — retrying earlier just wastes your quota.

Need a higher ceiling?

Contact support@mobilytics.com with your expected volume and use case. We set per-key overrides for partners that need more.