klaviyo-rate-limits

# Klaviyo Rate Limits ## Overview Handle Klaviyo's per-account fixed-window rate limits with proper `Retry-After` header handling, exponential backoff, and request queuing. ## Prerequisites - `klaviyo-api` SDK installed - Understanding of Klaviyo's dual-window rate limiting ## Klaviyo Rate Limit Architecture Klaviyo uses **per-account fixed-window rate limiting** with two distinct windows: | Window | Duration | Limit | Description | |--------|----------|-------|-------------| | **Burst** | 1 second | 75 requests | Short spike protection | | **Steady** | 1 minute | 700 requests | Sustained throughput cap | Both windows apply simultaneously. Exceeding either triggers a `429 Too Many Requests`. ### Rate Limit Headers **On successful requests:** | Header | Description | |--------|-------------| | `RateLimit-Limit` | Max requests for the window | | `RateLimit-Remaining` | Remaining requests in window | | `RateLimit-Reset` | Seconds until window resets | **On 429 responses (different headers!):** | Header | Description | |--------|-------------| | `Retry-After` | Integer seconds to wait before retrying | > **Critical:** When you hit a 429, `RateLimit-*` headers are NOT returned. Only `Retry-After` is present. ## Instructions ### Step 1: Retry-After Aware Backoff ```typescript // src/klaviyo/rate-limiter.ts export async function withRateLimitRetry<T>( operation: () => Promise<T>, options = { maxRetries: 5, baseDelayMs: 1000, maxDelayMs: 60000 } ): Promise<T> { ...