Working on an aggregation query against the /api/v2/analytics/queues/summary endpoint. Need to group results by both queue and mediaType. The goal is to get a breakdown of call vs chat volume per queue for the last 24 hours.
Here is the payload I’m sending in the POST request body:
{
"interval": "P1D",
"groupBy": ["queue", "mediaType"],
"select": ["talkDuration", "workDuration"]
}
The API returns a 200 OK, but the structure of the buckets array is weird. Instead of a flat list of objects with queue.id and mediaType, I’m getting nested objects where the key is a concatenated string like "queue:12345|mediaType:voice". Parsing this in our downstream Python script is a pain because the keys are dynamic strings, not standard JSON fields.
Is this the expected behavior for the v2 analytics endpoint? I’ve tried setting groupBy to just ["queue"] and it works fine (returns standard object keys). Adding mediaType breaks the schema consistency.
Also noticed that if I add "aggregations": [{"name": "count"}] it changes nothing about the key format. Just wondering if there’s a different endpoint or a specific parameter to force flat JSON output instead of these composite keys.