Is it possible to bypass the standard rate limiting for the /api/v2/agent-scripting/scripts endpoint when pushing high-volume concurrent updates?
Running a JMeter test suite to validate script deployment latency across 500 virtual agents.
Hit a wall with HTTP 429 Too Many Requests after just 50 concurrent POST calls.
The error payload returns "reason": "Rate limit exceeded" with a Retry-After header of 30 seconds.
Current setup uses a single service account token for all threads to simplify auth, which might be the bottleneck.
Wondering if distributing tokens across multiple service accounts would help, or if there is a specific header to request a higher throughput window for load testing.
The documentation mentions platform-wide limits but doesn’t specify if Agent Scripting has separate caps.
Environment is Genesys Cloud US-East.
JMeter config: Thread Group with 500 users, Ramp-Up 10 seconds, Loop Count 1.
Need to confirm if this is a hard limit for the platform_api tier or if we are hitting a WebSocket connection limit on the client side.
Any tips on structuring the request payload to minimize overhead? Currently sending minimal JSON bodies.
Appreciate any insights on handling these spikes without getting throttled.