Predictive Routing Campaign 429 during JMeter load test

Does anyone know how to handle rate limits for predictive outbound campaigns?

Running JMeter 5.6 against /api/v2/predictivedials/campaigns on Genesys Cloud US1. Pushing 100 concurrent threads triggers HTTP 429 errors immediately. The environment uses standard rate limits.

Need advice on pacing the requests to avoid hitting the cap. Current JMeter config sends bursts every 5 seconds.