Stuck on handling rate limits for Workforce Engagement Management endpoints. Running a JMeter 5.6.2 script from Singapore to simulate bulk agent login events. The target is POST /api/v2/wem/agents/{agentId}/login.
When concurrency hits 100 users, the gateway throws 429 Too Many Requests immediately. Retrying with exponential backoff helps, but the test duration balloons. Need to understand the exact threshold for this endpoint. Is it per tenant or per org unit? The documentation is vague on WEM specific limits versus general API limits.
HTTP/1.1 429 Too Many Requests
Retry-After: 5
Content-Type: application/json
{
"errors": [
{
"code": "too_many_requests",
"message": "Rate limit exceeded."
}
]
}
The goal is to validate capacity for 500 concurrent logins. Current setup uses a single bearer token. Should I be rotating tokens or adjusting the ramp-up time? Looking for best practices on structuring the JMeter thread group for this specific API.