Platform API 429 Rate Limiting during JMeter WebSocket Burst Test

Can anyone clarify the exact rate limit thresholds for the Genesys Cloud Platform API when handling high-concurrency WebSocket handshake requests? We are running a load test from our Singapore office using JMeter 5.6.2. The goal is to validate call capacity planning for a peak volume of 500 concurrent agents.

The test setup involves generating OAuth tokens and immediately initiating WebSocket connections to the Edge BYOC endpoint. The first batch of connections succeeds, but subsequent bursts trigger HTTP 429 Too Many Requests errors on the token refresh endpoint. This causes a cascade of failed WebSocket handshakes, returning 401 Unauthorized instead of the expected connection.

  1. Generate OAuth token via POST /oauth/token.
  2. Initiate WebSocket handshake using the bearer token.
  3. Repeat steps 1-2 for 50 concurrent threads.
  4. Observe 429 errors on token requests after 10 seconds.

The documentation mentions general API rate limits, but it is unclear if WebSocket-specific endpoints share the same bucket as REST APIs. We are hitting limits much faster than anticipated. Is there a way to increase the quota for load testing, or do we need to implement a specific retry strategy with exponential backoff? Sharing the JMeter config would be helpful if anyone has faced similar throughput issues.