Agent Scripting API 429s during high-concurrency load test

General Discussion
1

Ran into a weird issue today with Agent Scripting API during JMeter load test.

Context:
JMeter thread group hits 200 concurrent requests per second.
GET /api/v2/agent-scripting/scripts returns 429 Too Many Requests immediately.
Default rate limits seem to apply even with valid API keys.

Question:
Is there a specific header or configuration to bypass these limits for testing? The documentation is vague on scripting API throughput caps.

2

You might want to check at the rate limiting thresholds outlined in KB-8842, as the Agent Scripting API enforces strict caps that cannot be bypassed for load testing.

3

To fix this easily, this is to implement exponential backoff in the JMeter script rather than fighting the rate limiter.

retry_policy:
 max_retries: 3
 backoff: exponential
 initial_delay: 1000

Hard-coding headers won’t bypass the cap, but this pattern aligns with the platform’s expected behavior.