IZI API Rate Limits

IZI API Rate Limits

IZI API enforces per-token request limits. This protects shared infrastructure and ensures stability for all partners.

Quotas

Limit	Value
Sliding window	10 seconds
Max requests	100 per window
Counted per	Token (not IP)
Standard request cost	1
Analytics request cost	5–10 (depends on complexity)

The limit is sliding — not reset every 10 seconds, but continuously calculated over the last 10 seconds.

Response Headers

Every API response includes:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 73
X-RateLimit-Reset: 1717072920
X-RateLimit-Cost: 1

• X-RateLimit-Remaining — requests remaining in the current window
• X-RateLimit-Reset — Unix timestamp when the window resets
• X-RateLimit-Cost — cost of the current request

On limit exceeded:

HTTP/1.1 429 Too Many Requests
Retry-After: 7
X-RateLimit-Remaining: 0

Handling 429

async function requestWithBackoff(query, variables, maxRetries = 3) {
  for (let attempt = 0; attempt < maxRetries; attempt++) {
    try {
      return await client.request(query, variables);
    } catch (error) {
      if (error.status === 429) {
        const retryAfter = parseInt(error.headers['retry-after'] || '5', 10);
        // Add jitter to avoid synchronized retries
        const delay = retryAfter * 1000 + Math.random() * 1000;
        await new Promise(resolve => setTimeout(resolve, delay));
        continue;
      }
      throw error;
    }
  }
  throw new Error('Max retries exceeded');
}

Recommendations

For data sync — use webhooks instead of polling. Rather than asking “what changed?” every 5 seconds, subscribe to events and receive a push on change.

For bulk operations — group requests via batching (up to 10 per POST).

For analytics — run heavy queries during off-peak hours or cache results on your side.

Related Pages

• IZI API: Overview — general architecture
• Webhooks — alternative to polling
• API Error Codes — full error code reference