Looking for advice on handling rate limits when pulling performance metrics for our scale test. JMeter 5.6 runs 50 concurrent threads against /api/v2/analytics/users/summary and immediately returns 429 Too Many Requests. The goal is to validate data retrieval speed under high concurrent call volumes, not just API throughput for config changes.
We are using basic auth with an admin token. The test setup is simple:
- JMeter 5.6
- 50 threads
- Loop count: 100
- Target: Genesys Cloud US1
The error happens on the first request of every thread. No delay is applied. Is there a specific header or parameter we are missing to batch these requests? Or is the limit strictly per token regardless of concurrency?
429 Too Many Requests
Retry-After: 1
We need to know if this is a hard limit for load testing scenarios or if we need to adjust our JMeter configuration to stagger requests more aggressively. Any guidance on best practices for analytics API load testing would be appreciated.