Agent scripting api 429s during jmeter load test

I’ve spent hours trying to figure out why the flow scripting endpoints return 429s when simulating 50 concurrent agent sessions. using jmeter with default keep-alive settings, the rate limit hits after 60 requests per minute despite the docs suggesting higher throughput for scripting actions. is there a specific header or batch size required to bypass this?

1 Like