Is it possible to bypass WFM scheduling API rate limits during load tests?

Is it possible to bypass the strict rate limits on the /api/v2/wfm/scheduling/availability endpoint when running a high-concurrency JMeter script? I am hitting 429 errors immediately after spawning 50 threads in the ap-southeast-1 region.

My goal is to validate API throughput for bulk availability updates. The default quota seems too low for this scale. Are there specific headers or authentication methods that allow for higher throughput during testing phases?