- Environment: Genesys Cloud US1
- Tool: JMeter 5.6
- Threads: 30 concurrent
- Endpoint: POST /api/v2/conversations/messages
- Error: 429 Too Many Requests
Is it possible to increase the rate limit for messaging endpoints? Running a basic load test to validate message throughput for a new chat integration. The setup is simple: 30 threads sending standard JSON payloads to create messages. Almost immediately, the responses turn into 429 errors. The documentation mentions general API limits, but it is not clear if digital messaging has a separate or stricter cap compared to voice or interaction APIs.
The payload size is small, around 200 bytes. Network latency is low, under 50ms. The issue seems purely related to request volume. I tried adding a small delay between requests, but the 429s still appear when concurrency hits 30. Is this the hard limit for this endpoint? Or is there a specific header or configuration needed to handle higher volume? The goal is to understand the maximum sustainable rate before implementing a queuing mechanism on the client side. Any insight into the specific rate limit parameters for /v2/conversations/messages would be helpful.