Hitting a wall with the Analytics API during our latest load test. When JMeter threads exceed 50 concurrent requests to /api/v2/analytics/conversations/details/summary, the response shifts from 200 OK to 429 Too Many Requests. The header x-rate-limit-remaining drops to zero quickly, and subsequent calls are blocked for 60 seconds. This is breaking our automated reporting pipeline which expects real-time data every 5 minutes.
Current JMeter config:
- Thread Group: 100 users
- Ramp-up: 10 seconds
- Loop Count: Forever
- Request: POST /api/v2/analytics/conversations/details/summary
Payload sent:
{
"query": {
"date_from": "2023-10-25T00:00:00Z",
"date_to": "2023-10-25T23:59:59Z",
"granularity": "FIFTEEN_MINUTES"
},
"fields": ["wrap.up.code", "conversation.duration"]
}
Is there a specific header or retry logic I should implement to handle this better? Or is there a higher tier API endpoint for bulk historical data that doesn’t have this strict per-second limit? We are testing peak volume scenarios for Q4 planning and this bottleneck is critical. Environment is Genesys Cloud US East, version 2023-10-25.