Stuck on 429 Too Many Requests when querying the /v2/analytics/conversations/details/summary endpoint during a load test. I am running a JMeter script from the ap-southeast-1 region to validate API throughput before our peak season. The goal is to fetch conversation metrics for the last 24 hours.
With just 10 concurrent threads, the requests succeed initially. After about 30 seconds, the response headers return x-ratelimit-remaining: 0. The retry-after value is consistently 60 seconds, which kills the throughput. I expected a higher limit for read-only analytics endpoints, especially since I am using an admin account with full permissions.
The request payload includes a standard date range filter and a few metric selections (duration, handled calls). I am not batching multiple queries in a single request. Is there a specific configuration or header I am missing to increase the quota for analytics queries? Or is this a hard limit for the platform API tier we are on?
How can I increase the rate limit for the /v2/analytics/conversations/details/summary endpoint to support higher concurrent loads in JMeter?