Quick question about the rate limiting behavior for the Predictive Outbound campaign API endpoints. We are currently running load tests against the US1 environment using JMeter 5.6 to validate the system capacity for high-volume outbound campaigns. The specific endpoint causing issues is POST /api/v2/predictivedialing/campaigns/contacts. When we ramp up the thread group to simulate 100 concurrent users creating contacts, the API starts returning 429 Too Many Requests errors almost immediately after the first few successful calls. The error response body indicates that the rate limit for this tenant has been exceeded, but we are unsure of the exact threshold or the correct backoff strategy to implement in our load test script. We have tried implementing a constant throughput timer in JMeter to limit the requests to 50 per second, but the 429 errors still persist intermittently. The environment details are Genesys Cloud US1, JMeter 5.6, and we are using the standard OAuth 2.0 client credentials flow for authentication. We are not seeing any issues with the campaign creation endpoint itself, only with the bulk contact insertion. We need to understand if this is a hard limit per tenant or if there is a way to request a higher throughput allowance for our load testing purposes. We are also checking if the WebSocket connection for real-time campaign updates is affecting the API rate limits, but we suspect it is isolated to the REST API calls. Any insights into the expected throughput limits for contact creation or best practices for handling 429 errors in a load testing scenario would be greatly appreciated. We want to ensure our test results accurately reflect the system’s capacity under heavy load without being skewed by artificial rate limiting errors.