Screen Recording API returning 429 during high-concurrency load test

Can anyone clarify the rate limits for the /api/v2/recordings/interactions endpoint?

Running a JMeter script simulating 200 concurrent calls in our Singapore BYOC environment. The API throughput drops significantly when requesting recording metadata immediately after call disposition. Getting 429 Too Many Requests errors consistently after 50 requests per second. Is there a specific throttle for screen recording metadata retrieval that differs from standard audio recordings?

Have you tried adding a delay sampler in JMeter? The screen recording API often has stricter limits than standard audio endpoints during high concurrency.

Set the delay to 200ms between requests. This usually keeps you under the 50 rps threshold and stops the 429 errors.