Can anyone explain why the /api/v2/analytics/conversations/details/query endpoint is returning a 429 Too Many Requests error when pushing 30 concurrent threads through JMeter 5.6.2?
Running this load test from Asia/Singapore to validate our reporting pipeline’s capacity. The test plan sends a basic query for conversation details over the last 24 hours. Everything works fine at 10 threads, but as soon as I scale to 30, the responses start failing with 429 status codes. The response headers include Retry-After: 1, but adding a 1-second delay between requests doesn’t seem to help when running concurrently.
I have checked the API documentation for rate limits, but it’s unclear if the limit is per-user or per-organization for this specific endpoint. We are using a standard developer account for now. Is there a way to configure the JMeter thread group to respect the rate limits automatically, or do I need to implement a custom logic to handle the backoff? Any insights on the expected throughput for this endpoint under load would be helpful.
Here is the relevant JMeter HTTP Request sampler config:
- Method: POST
- Path: /api/v2/analytics/conversations/details/query
- Body: {“dateRange”: {“from”: “2023-10-01T00:00:00.000Z”, “to”: “2023-10-02T00:00:00.000Z”}}