Rate Limits

Rate Limits by Plan

Rate Limit Headers

Every API response includes these headers:

HTTP/1.1 200 OK
Content-Type: application/json
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1706810460

Handling Rate Limits

When you exceed the rate limit, you'll receive a 429 response:

{
  "error": "Rate limit exceeded",
  "code": "RATE_LIMITED",
  "retry_after": 23
}

Best Practices

• Check headers proactively — Monitor X-RateLimit-Remaining and slow down before hitting zero
• Implement exponential backoff — On 429 errors, wait the retry_after seconds, then retry with increasing delays
• Cache responses — Stats and timeseries data don't change frequently; cache for 60 seconds
• Batch requests wisely — Use date ranges to get more data per request instead of many small requests

async function fetchWithRetry(url, options, maxRetries = 3) {
  for (let i = 0; i < maxRetries; i++) {
    const response = await fetch(url, options);

    // Check rate limit headers
    const remaining = response.headers.get('X-RateLimit-Remaining');
    if (remaining && parseInt(remaining) < 5) {
      console.log('Approaching rate limit, slowing down...');
    }

    if (response.status === 429) {
      const data = await response.json();
      const waitTime = data.retry_after || Math.pow(2, i) * 1000;
      console.log(`Rate limited. Waiting ${waitTime}s...`);
      await new Promise(r => setTimeout(r, waitTime * 1000));
      continue;
    }

    return response;
  }
  throw new Error('Max retries exceeded');
}

Event Limits

In addition to API rate limits, each plan has a monthly event quota. Events include bot visits, referrals, and conversions tracked by your sites.

• Free: 10,000 events/month across all sites
• Pro: 100,000 events/month across all sites

When you reach your event limit, new tracking events are dropped (not recorded). Existing data remains accessible via the API. Usage resets on the first of each month.