Agent Scripting API 429 during JMeter load test on US1

Need some help troubleshooting rate limiting issues with the Agent Scripting API.

Running JMeter 5.6 against the /api/v2/agent-engagement/scripts endpoint on Genesys Cloud US1. The goal is to validate throughput for script updates during peak hours. Pushing 50 concurrent threads triggers HTTP 429 Too Many Requests after about 10 seconds. The test uses standard OAuth2 client credentials flow for authentication. Environment has default rate limits configured.

The JMeter test plan includes a thread group with 50 threads, ramp-up period of 10 seconds, and loop count set to 1. Each thread sends a PUT request to update a script version with a small payload containing text content and metadata. The request headers include standard Authorization Bearer token and Content-Type application/json.

Error response shows:
{
“message”: “Too Many Requests”,
“status”: 429,
“code”: “too_many_requests”,
“details”: “Rate limit exceeded for /api/v2/agent-engagement/scripts”
}

The retry-after header suggests waiting 60 seconds, but this breaks the load test flow. Increasing the ramp-up time to 30 seconds delays the 429 errors but does not eliminate them. Reducing concurrent threads to 25 allows the test to complete without errors, but this does not match our production peak requirements.

We have reviewed the API documentation for rate limits. The scripting API appears to have stricter limits compared to other endpoints tested previously. Previous tests against analytics and WFM APIs showed similar patterns at higher thread counts.

Has anyone successfully load tested the Agent Scripting API with high concurrency? What JMeter configurations or request patterns help avoid hitting rate limits? Are there specific headers or parameters that should be included to optimize throughput? Looking for best practices from others who have validated script update performance at scale.

Any guidance on expected throughput limits or recommended test configurations would be appreciated. The environment uses standard Genesys Cloud US1 infrastructure without custom rate limit adjustments.