Outbound campaign api 429 when jmeter hits 200 req/s in ap-southeast-1

I can’t seem to figure out why /api/v2/outbound/campaigns returns 429 when pushing jmeter threads to 200 req/s. the rate limit headers show x-ratelimit-limit: 100 but we are only testing campaign creation, not dialing. using python requests library v2.31.0 in singapore edge cluster.