Looking for advice on handling rate limits for the Outbound Campaign API during initial load testing. The goal is to simulate a modest ramp-up of outbound calls to verify edge capacity. The environment is Genesys Cloud BYOC Edge 24.1.0 in Asia/Singapore. Using JMeter 5.6.2 for the test execution.
The issue arises immediately when targeting the v2/outbound/campaigns endpoint. Even with a single JMeter thread and a generous 500ms delay between requests, the API returns 429 Too Many Requests errors. The response headers indicate a retry-after value, but the frequency seems disproportionate for such low concurrency. Basic authentication is handled via JWT tokens generated via the security API.
Current JMeter config includes a HTTP Request sampler pointing to the campaign creation endpoint. Headers are set correctly with Content-Type application/json. The payload contains standard campaign details including name, dialing mode, and contact list ID. No complex logic or multiple threads are involved at this stage. Just trying to establish a baseline for call initiation throughput.
Has anyone seen this behavior with the Outbound API specifically? Is there a hidden throttle for campaign creation distinct from general API limits? Need to understand if this is a configuration error or a platform constraint before scaling up to higher volumes.