Can anyone explain why the Outbound Campaign API returns 429 Too Many Requests so aggressively during initial load test ramp-up?
Running JMeter 5.4.1 against the v2/outbound/campaigns endpoint in the ap-southeast-1 region. The test plan simulates 150 concurrent threads creating campaigns simultaneously. According to the docs, the standard rate limit is 100 requests per minute per org. However, the errors start appearing after just 12 concurrent requests, not after exceeding the minute quota.
The response headers show Retry-After: 10. This suggests a burst limit is being hit immediately, but the documentation does not explicitly define a burst threshold for this specific endpoint. Is there a hidden per-second limit that overrides the per-minute quota?
Current config:
- SDK: Genesys Cloud REST API v2
- Environment:
ap-southeast-1 - Payload size: ~2KB JSON per request
- Authentication: OAuth2 Client Credentials
Need to understand if this is a hard-coded burst cap or if the client IP is being throttled differently than expected. Any insights on tuning the JMeter throughput controller to respect these undocumented limits would be appreciated. The goal is to model realistic campaign creation spikes without triggering immediate rejection.