Analytics API 413 Entity Too Large on 90-day queue disposition query

Regarding the GET /api/v2/analytics/queues/dispositions endpoint, I require clarification on the expected payload handling for extended analytical windows. Our current administrative configuration utilizes a FROMDATE to TODATE window spanning 90 days. The system consistently returns a 413 ENTITY TOO LARGE response.

Debugging Log:

  • Attempted to partition the GROUPBY parameters across sequential requests. Status: Failed.
  • Reduced the SIZE parameter limit to 100. Status: Failed.
  • Executed via GENESYS-CLOUD-PYTHON SDK V3.0.2 within the GENESYS CLOUD EU-WEST-1 environment. Status: Failed.
  • Payload generation remains constrained by the same threshold.

Specific Inquiry: Please provide the precise JSON structure required to segment this analytical query into weekly intervals. The implementation must preserve the integrity of the DISPOSITIONCODE aggregation while aligning with standard ADMIN_UI routing constraints.