quick question about the /api/v2/outbound/calls endpoint. pushing 200 concurrent requests via jmeter and hitting 429 errors immediately. is there a specific header or rate limit config i am missing for load testing outbound campaigns?
Make sure you align the outbound dialer configuration with the documented rate limits for the /api/v2/outbound/calls endpoint. The 429 errors indicate the system is throttling concurrent requests, which is expected behavior during high-volume load testing.
Review the Architect flow to ensure the export job waits for the metadata synchronization to complete. Adjusting the pacing in the campaign settings should mitigate the immediate spike in 429 responses.
The quickest way to solve this is:
- Implement exponential backoff in the JMeter thread group to respect the 429 Retry-After header.
- Check the
X-RateLimit-Remainingresponse headers to dynamically adjust your request pacing.
TL;DR: Rate limits protect audit integrity.
If I remember correctly, the 429 response includes a Retry-After header. JMeter needs to parse this value for dynamic pacing. Blindly increasing concurrency breaks chain of custody for recording exports. Respect the backoff interval to ensure metadata sync completes without data loss.