Is it possible to configure Genesys Cloud to handle rapid OAuth token refreshes without hitting 429s? Running a load test from Singapore targeting 500 concurrent WebSocket connections. Each connection needs to authenticate via OAuth 2.0. The test ramp-up phase triggers a burst of POST requests to https://api.mypurecloud.com/oauth/token.
JMeter reports 429 Too Many Requests after roughly 200 concurrent auth attempts. The response headers indicate the limit is per client ID, but the docs are vague on the exact threshold for this endpoint.
“Rate limits for the OAuth 2.0 endpoint are enforced to prevent abuse. Specific limits vary by endpoint and subscription tier. Refer to the API documentation for detailed rate limit information.”
This generic statement doesn’t help with capacity planning. We need to know if there’s a hard cap like 100 req/min or if it’s dynamic. Also, should we be implementing a custom token caching strategy in our test script to avoid hitting the auth endpoint repeatedly, or is there a way to increase the limit for testing purposes? Current setup uses the standard client_credentials grant type.