Analytics API 429s during JMeter ramp-up

I’ve spent hours trying to figure out why the /api/v2/analytics/interactions/summary endpoint returns 429 Too Many Requests immediately when JMeter hits 50 threads from Singapore. The docs state:

Rate limits are applied per user per minute. Exceeding this limit results in a 429 response.

Is there a specific header or token rotation strategy needed to handle higher throughput for load testing?