Get Events rate limit unexpectedly changed from 3,500/min to 150/min
Hi! Has anyone else noticed a recent rate-limit change for GET /api/events?
Our daily extraction previously sustained approximately 3,400 requests/minute. On August 14, it completed around 374,600 requests in 110 minutes. Starting sometime between August 14 and 16, throughput dropped to approximately 148 requests/minute, with continuous HTTP 429 responses.
Successful Events responses now advertise:
ratelimit-limit: 10, 10;w=1, 150;w=60That appears to be the Medium tier: 10 requests/second and 150/minute. However, the Get Events documentation still specifies 350/s and 3,500/min.
We tested:
- OAuth and private API key authentication
- Revisions
2026-04-15and2026-07-15 - With and without
include=metric - Two separate Klaviyo accounts
Every Events combination returned the same 10/s and 150/min limits. The response headers confirmed that the requested revision was applied correctly.
As a control, GET /api/profiles on the same account and connection returned its expected higher limits:
ratelimit-limit: 75, 75;w=1, 750;w=60This suggests the issue is specific to Get Events rather than authentication, account-wide throttling, or incorrect interpretation of the headers.
We have also ruled out competing local processes, our implementation has not changed since the successful August 14 extraction, and Klaviyo’s status page shows no API incident.
Was Get Events recently moved from the XL to Medium tier, or could this be an unintended configuration change? Has anyone else observed these headers or a sudden increase in 429 responses?
