Trying to build an aggregation query that groups by queue and mediaType. The API keeps rejecting the request with a 400 error.
Here is the payload:
{
"groupBy": ["queue", "mediaType"],
"aggregates": [
{
"name": "handleTime",
"type": "sum"
}
]
}
Is this combination not allowed in the v2 analytics endpoint?
You can’t group by queue and mediaType in the same query. The API rejects mixed granularity. Split it up. Use /api/v2/analytics/details/queries for queue stats, then a separate call for media type breakdowns. Keep the payloads simple.
{
"groupBy": ["queue"],
"aggregates": [{"name": "handleTime", "type": "sum"}]
}
Actually, you can group by both queue and mediaType in a single call, but only if you are using the correct endpoint and the data actually supports that granularity. The /api/v2/analytics/details/queries endpoint is notoriously picky about mixed dimensions. It often throws a 400 if the underlying data model doesn’t support that specific combination for the requested time window or entity type.
The suggestion to split it up is safe, but it’s also inefficient if you just need a quick cross-tab. I ran into this exact issue last week while building a dashboard in Blazor. The problem wasn’t the groupBy array itself, it was missing the interval or having an invalid dateRange. Without a valid interval, the API can’t determine the bucket for the aggregation, so it rejects the dimension combo as ambiguous.
Try adding an explicit interval and ensuring the entityId (if you’re querying a specific interaction) matches the groupBy context. Here is a working payload I use in my .NET service:
{
"groupBy": ["queue", "mediaType"],
"aggregates": [
{
"name": "handleTime",
"type": "sum"
}
],
"interval": "P1D",
"dateRange": {
"startDate": "2023-10-01T00:00:00.000Z",
"endDate": "2023-10-02T00:00:00.000Z"
}
}
If you are hitting /api/v2/analytics/evaluations instead, that one is more flexible but requires you to define the entities array correctly. The docs say “The groupBy dimensions must be supported by the selected entities,” which is vague. In practice, queue and mediaType work together for routing/queues entities. If you’re querying routing/agents, it will fail because agents don’t have a mediaType attribute in the same way.
Check which entity type you are targeting. If it’s queues, the payload above should pass. If it’s still failing, dump the full error body from the response, not just the status code. The detail field usually tells you exactly which dimension is invalid for that entity type.