- Environment: Genesys Cloud US1
- Tool: JMeter 5.6
- Threads: 100 concurrent
- Endpoint: POST /api/v2/interaction/screenpop
- Error: 429 Too Many Requests
Could someone explain the rate limiting behavior for screen pop interactions during load testing? The goal is to validate system capacity for a high-volume inbound campaign where agents receive simultaneous screen pops. Running JMeter with 100 threads against the screen pop endpoint. Getting immediate 429 errors after the first 20 requests. The error response indicates rate limit exceeded, but documentation is unclear on the specific threshold for this endpoint compared to standard interaction APIs. Need to know if this is a hard limit per organization or per user token. Also, checking if WebSocket connections for screen pops have different constraints than REST API calls. Any advice on configuring JMeter to respect these limits while still measuring throughput would be helpful. Want to ensure the test reflects realistic peak concurrency without triggering unnecessary blocks. Current setup uses a single admin token for all requests, which might be causing the issue. Should I be rotating tokens or using a different approach for load validation?