Trying to understand the exact rate limit behavior for the /api/v2/outbound/campaigns endpoint when simulating 500 concurrent dialing requests via JMeter.
429 Too Many Requests
The standard 100 requests per minute cap seems to block our load generation spikes. Is there a specific header or token needed to bypass this for performance validation?
Check your request distribution strategy first. The 429 error is not a bug to bypass; it is a protective measure for the outbound engine. Attempting to force 500 concurrent dialing requests through a single endpoint will inevitably trigger the rate limiter, regardless of any headers. The system is designed to handle high volume by distributing load, not by accepting massive bursts on one API call.
Do not attempt to bypass this limit using undocumented headers or tokens, as this will likely result in temporary IP bans or service degradation for your tenant.
Instead, structure your JMeter test to stagger requests. Use a thread group with a ramp-up period that aligns with the 100 requests per minute window. If you need to simulate higher concurrency, parallelize the test across multiple virtual users or split the campaign creation into smaller batches. The performance dashboard will show queue activity spikes if the engine is overwhelmed, so monitor those metrics closely during the test to ensure you are validating system capacity, not just API limits.
Make sure you stagger the outbound calls instead of hitting the endpoint all at once. The 429 error is the system protecting the dialer from overload.
Use a simple exponential backoff in your script. Spreading the load over time is the only way to simulate realistic high-volume scenarios without triggering the rate limiter.