Quick question about the rate limiting behavior for the analytics endpoints when running concurrent load tests.
I am setting up a JMeter script to validate the API throughput for conversation details. The test creates 100 virtual users, each sending a GET request to /api/v2/analytics/conversations/details/summary every 5 seconds. The query parameters are set to:
interval=PT1H
size=500
After about 2 minutes of execution, the response rate drops significantly, and the majority of requests return 429 Too Many Requests. The response headers include Retry-After: 60.
I read this in the documentation:
“The Analytics API enforces strict rate limits to ensure service stability. Clients should implement exponential backoff strategies when receiving 429 responses.”
My current JMeter config has a simple constant throughput timer, but I am not seeing the expected steady state. Is there a specific header or configuration I need to adjust in the request to handle this better? Or is this a hard limit for the tier we are on? I want to make sure the test results are not skewed by these errors. Any advice on how to structure the load test to stay within limits while still validating capacity would be helpful.