Quick question about hitting rate limits on the /api/v2/analytics/interactions/summary endpoint. running a jmeter script in ap-southeast-1 with 50 concurrent threads, the api starts returning 429 Too Many Requests after just 200 calls. the response headers show x-ratelimit-limit: 50 and x-ratelimit-remaining: 0, which seems aggressive for a summary query.
the payload is minimal, just filtering by interactionType: voice and a 24h interval. no complex aggregations or custom metrics involved. i have tried adding a 200ms delay between requests, but the throughput drops too low for our load test requirements. the goal is to validate report generation latency under concurrent user load, not to spam the api.
is there a way to increase the rate limit for analytics endpoints, or is this a hard ceiling for standard orgs? also, should i be batching these requests differently to avoid the 429s? any config tweaks in jmeter that might help with the token refresh or request pacing would be appreciated. thanks.