Is it possible to bypass or increase the rate limits on the Outbound Campaign API endpoints when running high-concurrency load tests? We are currently stress-testing the platform’s ability to handle rapid campaign creation and modification for a large-scale BPO environment in Singapore. The goal is to determine the breaking point for API throughput when multiple teams attempt to update campaign settings simultaneously.
We are using JMeter 5.6.2 configured with a Thread Group of 50 users, each executing a loop to POST requests to /api/v2/outbound/campaigns. The test scenario involves creating dummy campaigns, updating their wrap-up codes, and immediately querying the campaign status. After just 30 seconds of execution, we start receiving a flood of HTTP 429 Too Many Responses. The response headers indicate X-RateLimit-Remaining: 0 and Retry-After: 60.
The specific error payload is:
{
"message": "Rate limit exceeded",
"errors": [
"Too many requests"
],
"status": 429,
"code": "rate_limit_exceeded"
}
We have tried implementing exponential backoff in the JMeter script, but this significantly reduces the effective throughput, which defeats the purpose of the load test. We need to know if there is a way to request a temporary increase in the API rate limit for testing purposes or if there is a specific pattern we are missing in our request structure. The environment is Genesys Cloud US-East. We are not hitting WebSocket limits, just the REST API endpoints for outbound configuration. Any insights on how other load testing engineers handle this bottleneck would be appreciated. We are also seeing occasional 502 Bad Gateway errors on the GET endpoints, which might be related to the backend struggling with the high volume of concurrent writes. Thanks in advance for any guidance.