Context:
My config is not working…
Trying to validate API throughput for agent script updates under high concurrent call volumes. Using JMeter 5.6 with 50 concurrent threads against /api/v2/scripts. The environment is Genesys Cloud US1. We are simulating a scenario where scripts are swapped dynamically during peak hours. The test hits 429 Too Many Requests errors immediately after 10 seconds. We have not seen this issue before with other endpoints. The goal is to understand the rate limits for script management APIs. We need to ensure our load testing framework can handle the expected volume. The JMeter plan uses basic authentication and standard headers. We are seeing this behavior consistently across multiple test runs. The latency spikes are also noticeable before the 429 errors occur. We suspect there is a hidden rate limit or a specific throttling mechanism for script updates that is not documented clearly. We want to avoid any service disruption during actual peak loads.
Question:
Is it possible to increase the API rate limit for POST /api/v2/scripts? Or is there a specific recommendation for pacing requests to avoid 429 errors during high-volume load tests? We need to validate our capacity planning assumptions. Any guidance on the expected throughput for script updates would be helpful. We are using the standard REST API and not any SDK wrappers. The issue persists even with a simple payload. We want to ensure our infrastructure can handle the load without hitting these limits.