Running into a 413 Entity Too Large error when trying to pull conversation details for a 90-day period. The payload size seems to be the issue, even though I’m just setting date filters.
Here’s the POST body I’m sending to /api/v2/analytics/conversations/details/query:
{
"dateFrom": "2023-10-01T00:00:00.000Z",
"dateTo": "2023-12-30T23:59:59.000Z",
"groupBy": ["conversationId"],
"metrics": ["totalHandleTime"],
"select": ["conversationId", "startTime", "duration"]
}
The response is just 413: Entity Too Large. I’ve checked the docs and it mentions a 2MB limit for request bodies, but this JSON is tiny. I suspect the server is pre-validating the result set size based on the date range before it even processes the query.
I’ve tried reducing the range to 30 days and it works fine. Splitting it into three 30-day chunks works too, but that’s inefficient for our reporting script. Is there a way to paginate the request or use a different endpoint that handles larger date ranges without hitting this limit? Or am I missing a header to bypass this check?