Can anyone clarify the exact rate limit thresholds for the Outbound Campaign API when creating campaign segments via JMeter? We are running a load test to validate our Genesys Cloud instance performance under high concurrency. The test involves creating 50 concurrent users simulating admin actions to push campaign segment updates. The script hits /api/v2/outbound/campaigns/{campaignId}/segments with a POST request. After approximately 120 requests per minute, we start receiving HTTP 429 Too Many Requests errors with a Retry-After header value of 5 seconds. Our JMeter configuration uses a constant throughput timer set to 120 requests per minute. The error payload indicates that we have exceeded the allowed request rate for this endpoint. We have verified that the OAuth tokens are valid and the service account has the necessary permissions for outbound campaign management. The environment is Genesys Cloud v1.24.3. We are unsure if this limit is per organization, per user, or per API key. The documentation mentions general rate limits but does not specify the exact numbers for outbound campaign operations. We need to adjust our test script to avoid hitting this limit while still validating the system’s capacity. Any insights on the specific limits or best practices for handling these errors in a load testing scenario would be appreciated.