API Rate Limiting — Overview. The v3 API enforces rate limits to ensure fair usage and platform stability for all consumers. Standard API keys are limited to 1,000 requests per minute (RPM). Enterprise API keys support up to 10,000 RPM. Rate limits are applied on a per-key basis using a sliding-window algorithm. Every API response includes the following rate-limit headers: X-RateLimit-Limit (maximum requests per window), X-RateLimit-Remaining (requests remaining in the current window), and X-RateLimit-Reset (Unix timestamp when the window resets). When a client exceeds the rate limit, the API returns HTTP 429 Too Many Requests with a Retry-After header indicating the number of seconds to wait before retrying. Clients should implement exponential backoff with jitter to avoid thundering-herd problems. Burst allowances of up to 50 requests above the limit are permitted for brief spikes but sustained overuse will trigger throttling. Enterprise customers may request custom rate-limit configurations through their account manager.