Reporting API 429 during JMeter load test for bulk metric retrieval

General Discussion
1

Can’t get this config to load properly…

Running a load test against the Reporting API in Genesys Cloud US1. The goal is to validate capacity for bulk metric retrieval before peak season. The flow uses a simple GET request to /api/v2/analytics/interactions/summary.

Environment:

  • Genesys Cloud US1
  • JMeter 5.6
  • Endpoint: /api/v2/analytics/interactions/summary
  • Config: 150 concurrent threads send requests with 1-minute intervals.

I cannot figure out why the Reporting API returns rate limit errors. The test fails with 429 Too Many Requests when concurrent thread count exceeds 50. The error response is:

{
 "status": 429,
 "code": "rateLimitExceeded",
 "message": "Rate limit exceeded. Please retry after 60 seconds."
}

I read the documentation on rate limits, but it is not clear how to handle this for bulk reporting queries.

“The Reporting API has a rate limit of 100 requests per minute per organization. If you exceed this limit, you will receive a 429 Too Many Requests response.”

Is there a way to increase the rate limit for reporting queries? Or is there a best practice for handling rate limiting in JMeter for bulk data retrieval? Any advice is appreciated.