What’s the standard way to handle date range limits in the analytics API?
Problem
We’re pulling queue performance data for the last 90 days. The admin UI renders this report without issue, yet the direct API call keeps failing. The response payload is just too big for a single request apparently. We’ve checked the headers and nothing jumps out. The queue ID is correct. We’re using the standard OAuth token. The region is us-east-1. We’ve tried reducing the group_by fields but the error persists. The body is empty on the GET request so it’s not a payload size issue on the send side. Must be the response size limit.
Code
GET /api/v2/analytics/queues/summary?dateFrom=2023-10-01T00:00:00.000Z&dateTo=2023-12-31T23:59:59.999Z&group_by=queue/id
Error
HTTP 413 Entity Too Large
Question
Does the API enforce a hard cap on rows? We’re splitting the date range into 30-day chunks. The loop works locally. Just wondering if there’s a better approach. The docs are silent on this.