Screen Recording API 429 errors during JMeter load test

Could someone explain the rate limits for the Screen Recording API in Genesys Cloud US1?

Background

Running JMeter 5.6 with 100 concurrent users against GET /api/v2/recording/screencaptures. The standard flow works fine at lower concurrency.

Issue

Just noticed that the Screen Recording endpoint returns HTTP 429 Too Many Requests when JMeter 5.6 hits 50 req/s in US1. The error happens immediately after the ramp-up phase. The response body contains "code":"too_many_requests","message":"Rate limit exceeded". This is causing significant test failures in our performance suite.

Troubleshooting

We have reviewed the standard API rate limit documentation, but the specific limits for Screen Recording APIs are not clearly defined. The error occurs even when we include proper authentication headers and respect the Retry-After header in subsequent requests. We are using the same JMeter configuration that works for other APIs like Quality Management and WFM. The issue persists across multiple test runs. We need to understand the exact rate limit threshold for this endpoint to adjust our load test parameters accordingly. Any guidance on how to properly handle these rate limits during high-concurrency testing would be appreciated.