Ran into a weird issue today with the Genesys Cloud Interactions API when simulating high concurrent traffic. We are attempting to validate write capacity limits using JMeter 5.6.2. The test plan creates 200 concurrent threads, each posting a new interaction payload to the POST /api/v2/interactions endpoint. The goal is to determine the exact threshold before rate limiting triggers under standard tier configurations. The environment is a US East production instance, and we are using a service account with full interaction.write permissions.
The issue occurs almost immediately after the test ramp-up phase completes. Instead of a smooth throughput increase, we see a sudden spike in HTTP 429 Too Many Requests responses. The error payload indicates that the rate limit has been exceeded, but the Retry-After header is missing or inconsistent. This makes it difficult for our test script to implement proper backoff logic. We have verified that the OAuth token is valid and has not expired. The request headers include the correct Content-Type and Accept values.
We have analyzed the traffic pattern using Wireshark and confirmed that the WebSocket connections for the underlying interactions are stable. The problem seems isolated to the REST API calls. We have tried reducing the concurrency to 100 threads, and the errors disappear. However, at 150 threads, the 429 errors return intermittently. This suggests a hard cap or a burst limit that is not clearly documented in the current API reference. We need to know the exact burst allowance for this endpoint.
Can someone clarify the specific rate limit rules for the POST /api/v2/interactions endpoint? We need to understand if there is a per-minute or per-second burst limit that applies to service accounts. Also, is there a way to request a higher limit for load testing purposes? We are trying to model accurate capacity planning scenarios and need predictable behavior from the API. Any insights on how to handle these rate limits in JMeter would be appreciated.