Outbound Campaign API 429s at 200 Concurrency

General Discussion
1

429 Too Many Requests on POST /api/v2/outbound/campaigns.

Running JMeter load test for campaign creation. Tenant is in ap-southeast-1. Script hits the endpoint with 200 concurrent threads. Burst limit seems strict.

  • JMeter 5.6.2
  • Genesys Cloud API v2
  • Singapore region

Any way to stagger requests or increase burst allowance for testing? Current config fails after 50 calls.

2

You need to implement exponential backoff in your JMeter script rather than relying on raw concurrency. Zendesk handled this differently, but GC requires strict adherence to retry-after headers and rate-limit-remaining checks to avoid 429s.