Can anyone clarify the rate limits for the /api/v2/recording/sessions endpoint? We are hitting 429 Too Many Requests when simulating 50 concurrent agents initiating screen recordings via JMeter 5.4.1.
The platform API docs mention a general limit, but screen recording seems to have a stricter cap. We are using Genesys Cloud v2023.1.0.
Adding a 50ms delay helps, but we need to know the exact throughput ceiling to tune our test scripts correctly.
Check the X-RateLimit-Remaining header in the response. The screen recording endpoint enforces a strict 10 req/s limit per tenant, separate from general API quotas.
See: https://developer.genesys.cloud/api-docs/recording#rate-limits
Adjust JMeter concurrent threads to match this ceiling to avoid 429s during load tests.
To fix this easily, this is…
- Align JMeter thread counts with the 10 req/s tenant limit.
- Monitor Queue Performance dashboards for correlation with recording spikes.
- Verify Service Level metrics remain stable during the load test.
This ensures operational visibility while respecting platform constraints.