Outbound Campaign API 429s during JMeter ramp-up

Context: Running into a weird bug with the Outbound Campaign API returning 429 Too Many Requests when simulating high-concurrency dialing via JMeter.
We are hitting /api/v2/outbound/campaigns/{campaignId} to trigger predictive dialing for 500 concurrent agents. The error spikes right at the 200-user mark, despite staying within documented rate limits.

Question: Could someone explain if there are hidden throttling rules for campaign initiation endpoints during load tests?