- Genesys Cloud EU1
- JMeter 5.6.2
- Java SDK 13.0.1
- Outbound Campaign API v2
Could someone explain why the outbound campaign creation endpoints are hitting rate limits so aggressively?
Running a simple load test to simulate campaign setup. The goal is just 50 concurrent requests to /api/v2/outbound/campaigns. Everything works fine at 10 threads. Once I push past 30, the response time spikes and I start seeing 429 Too Many Requests errors. The retry-after header is returning random values, making backoff logic in the JMeter script unreliable.
The docs say the limit is 100 requests per minute for this endpoint, but I am hitting it way before that. Is there a hidden throttle for campaign resources specifically? Or is this a general API gateway issue during peak hours in SG timezone?
The error payload looks like this:
{ "errors": [ { "code": "RATE_LIMIT_EXCEEDED" } ] }
Trying to figure out if I need to adjust the JMeter timer or if there is a specific header I am missing. The auth token is valid and refreshed properly. Just trying to get the baseline throughput numbers for the client.