Running a load test to validate our analytics pipeline’s capacity under high concurrency. The goal is to simulate 100 concurrent users fetching real-time interaction details via GET /api/v2/analytics/details.
Using JMeter with a Thread Group set to 100 users, ramp-up 10 seconds, and a loop count of 10. Each request uses a valid access token and queries a 5-minute window for a specific skill.
At roughly 40 concurrent threads, the API starts returning 429 Too Many Requests. The response headers include Retry-After: 2. Dropping the thread count to 20 resolves the issue, but we need to understand the hard limits for this endpoint in the US1 region.
Has anyone hit a specific rate limit threshold for the analytics details endpoint? Is there a way to increase the limit for a load testing environment, or is this a hard platform cap? The documentation mentions general rate limits but doesn’t specify per-endpoint caps for analytics queries.
Any insights on how to structure the JMeter script to respect these limits while still testing throughput? Adding a constant throughput timer helps, but we want to know the absolute ceiling before hitting the 429s.