Wfm scheduling api 429 during jmeter load

Could someone explain why i get 429 too many requests on POST /api/v2/wfm/schedulingschedule? running jmeter 5.6 on us1 with 100 threads. its a beginner config issue maybe. the rate limit header says x-ratelimit-remaining: 0 after 10 seconds. we are just testing basic capacity planning api throughput. no architect flows involved just pure wfm api calls. any idea how to bypass or fix this limit in load test?