Error: 429 Too Many Requests
Endpoint: /api/v2/conversations/bots
Running a load test with JMeter to simulate high-volume inbound bot traffic. The script creates 500 concurrent threads, each initiating a new bot conversation via the API. After approximately 150 requests, the response code shifts to 429. The headers indicate rate limiting on the conversation creation endpoint.
The environment is a standard Genesys Cloud org with no custom API rate limit overrides. I have verified that the JWT tokens are valid and not expiring during the test. The Architect flow is simple, just a greeting and a menu prompt. No complex NLP or external integrations are triggered yet.
Is there a specific limit on bot conversation creation per second that differs from standard API limits? I see documentation for general API throughput, but bot-specific limits are unclear. Should I implement a wait strategy in JMeter to stagger requests, or is this a configuration issue on the org side?
Any insights on handling bot load testing without hitting these limits would be appreciated.
Thanks for the help.