413 Entity Too Large on GET /api/v2/analytics/interactions/query with 90-day span

Running into a wall with the Analytics API. Trying to pull interaction data for a full quarter. The query spans exactly 90 days.

Using the standard POST endpoint:
POST /api/v2/analytics/interactions/query

The payload looks like this:

{
 "dateFrom": "2023-10-01T00:00:00.000Z",
 "dateTo": "2023-12-30T23:59:59.999Z",
 "groupBy": ["conversation.mediaType"],
 "select": ["conversation.mediaType", "duration", "talkTime"],
 "filter": [
 {
 "type": "conversation",
 "dimension": "mediaType",
 "operator": "in",
 "value": ["voice", "webchat"]
 }
 ]
}

Getting a 413 Entity Too Large response immediately. No useful error body. Just the status code.

Tried splitting the date range into 30-day chunks. That works fine. But I need to automate this in a script using the REST Proxy. Sending three separate requests and merging the JSON arrays in a loop is messy. It adds latency and complexity to the logic.

Is there a way to increase the payload limit? Or is there a different endpoint that handles larger datasets? Maybe a streaming option?

Checked the docs. Nothing about pagination for this specific query type. The page parameter doesn’t seem to apply here since it’s an aggregation query, not a list of entities.

Anyone have a workaround for bulk historical pulls without hitting the 413? Or should I just bite the bullet and write the loop?