Looking for advice on a permission issue we are hitting when trying to retrieve screen recording URLs via the platform API. We are running a load test from our Singapore office to simulate a spike in agent activity. The test involves 200 concurrent virtual agents logging in and initiating screen recording sessions simultaneously using JMeter.
The initial recording start requests via POST /api/v2/recordings/screen are succeeding and returning valid recording IDs. However, when the script attempts to fetch the actual recording URL or metadata via GET /api/v2/recordings/screen/{recordingId} just a few seconds later, we are getting a 403 Forbidden error. This is strange because the Service Account used for the API calls has the recording:view scope enabled.
We suspect this might be related to how Genesys Cloud handles resource locking or permission checks under high load. The 403 errors seem to occur randomly across different recording IDs, not just specific ones. The error message in the response body is generic, just saying “Forbidden”. We have checked the token validity and it is not expiring. The issue persists even when we reduce the concurrency to 50 agents.
Has anyone seen similar behavior with screen recording endpoints during load testing? We are using the standard OAuth2 client credentials flow. The JMeter thread group is set to ramp up over 10 seconds. We need to ensure our capacity planning accounts for this API throughput limitation. Any insights on whether there is a hidden rate limit or a specific permission we are missing for bulk retrieval?