WFM API 429 Rate Limit during JMeter Load Test on US1

Does anyone know the specific rate limit for the Workforce Management API when simulating high concurrency in JMeter?

I am running a performance validation suite using JMeter 5.6 against the Genesys Cloud US1 environment. The goal is to test the stability of the scheduling engine under heavy load. We are simulating 50 concurrent threads hitting the /api/v2/wfm/schedules endpoint to retrieve schedule details.

After about 30 seconds, the response time spikes significantly. Then, we start seeing a lot of 429 Too Many Requests errors. The response headers show Retry-After: 5. This is happening even though we are not hitting the global API limit for the organization.

I have checked the Genesys Docs and it mentions rate limiting but does not give specific numbers for WFM endpoints. The documentation says to use exponential backoff, but I want to know the exact threshold. Is it per tenant or per API key?

Here is the JMeter configuration:

  • Thread Group: 50 threads, ramp-up 10 seconds, loop count 10.
  • HTTP Request: GET /api/v2/wfm/schedules?scheduleId=xxx
  • Authorization: Bearer token (refreshed every 50 minutes).
  • User Defined Variables: baseUrl=https://api.mypurecloud.com

We are seeing this pattern consistently. First 100 requests are OK. Then errors start. The error rate is about 40% after the initial burst.

I tried adding a constant timer of 200ms between requests. This reduced the error rate but did not eliminate it. I also tried using the HTTP Cookie Manager to handle sessions, but that did not help.

Is there a specific limit for WFM APIs? Or is it sharing the limit with other APIs like Conversations? I need to tune the JMeter script to stay within the limits without slowing down the test too much. Any advice on how to handle this for WFM endpoints would be appreciated. We are trying to validate the capacity for our upcoming go-live.