Trying to understand why hitting the /v2/analytics/details endpoint returns 429 Too Many Requests when ramping up JMeter threads beyond 50. The environment is Genesys Cloud in the us-east-1 region. Using the standard OAuth2 client credentials flow for authentication. The JMeter script sends requests at a rate of 100 requests per second with a 5-second think time between iterations. After 30 seconds, the response time spikes, and the 429 errors start appearing. The Retry-After header suggests waiting 60 seconds, but the load test requires continuous data retrieval. The API documentation mentions rate limits based on tenant capacity, but the exact threshold for this endpoint is unclear. Is there a way to increase the rate limit or optimize the request pattern to avoid hitting the cap? The current JMeter configuration uses a ThroughputController with a target of 100 requests per second. The error response body contains a message field stating Rate limit exceeded. Any insights on how to handle this in a load testing scenario would be appreciated. The goal is to simulate a high-throughput analytics dashboard pulling real-time data.
TL;DR:
This is caused by exceeding the tenant-level rate limit for analytics queries, which defaults to ~200 requests/min. Implement exponential backoff in JMeter or aggregate requests client-side instead of hammering the API.