The documentation actually says rate limits are hard-coded and cannot be adjusted, even for test organizations. Attempting to bypass them violates the platform’s usage policies. For accurate capacity planning, implement exponential backoff in your JMeter scripts to handle 429 responses gracefully. See the rate limiting guide here: https://developer.genesys.cloud/rest-api-v2/rate-limiting
Have you tried adding the Retry-After header logic to your JMeter controller? Ignoring 429s risks IP bans, which complicates legal discovery audits later. The platform enforces strict limits to protect data integrity. Adjust your thread ramp-up to respect the X-RateLimit-Remaining header instead of forcing throughput.