Just noticed that running concurrent requests against the analytics endpoint triggers immediate rate limiting errors. This blocks our capacity planning validation for the new reporting dashboard.
Environment details:
- Genesys Cloud US1
- Tool: JMeter 5.6
- Threads: 20 concurrent
- Endpoint: GET /api/v2/analytics/interactions/summary
- Error: 429 Too Many Requests
The test simulates a batch process pulling interaction summaries for the last 24 hours. When thread count stays below 10, responses return 200 OK with data. Once we push to 20 threads, the 429 errors start instantly. The response headers show a retry-after value, but this seems too aggressive for a read-only analytics call.
Is there a specific rate limit tier for analytics endpoints? We need to understand the throughput ceiling to size our backend aggregation service correctly. The documentation mentions general API limits but does not specify analytics query constraints.
Any guidance on how to structure these requests to avoid hitting the limit? We are trying to optimize the polling interval without losing real-time visibility.