Stumbled on a weird bug today with the /api/v2/analytics/conversations/details query when aggregating data from our JMeter load tests. The endpoint returns a 429 Too Many Requests error immediately after hitting the rate limit, even with the recommended backoff strategy.
{
"code": "too_many_requests",
"message": "Rate limit exceeded. Please retry after 30 seconds."
}
The issue persists across multiple tenant accounts in the APAC region. Is there a specific header or pagination trick to bypass this for high-volume analytics retrieval?