Analytics Aggregates query returning empty results for custom interval

NICE CXone API & Integrations
1

Could someone explain why my Analytics Conversations Aggregates query returns an empty dataset despite valid parameters?

Background

I am building a custom interval report using the /api/v2/analytics/conversations/details/query endpoint. The goal is to fetch aggregated metrics for a specific 15-minute window.

Issue

The request completes with a 200 OK status, but the results array is consistently empty. I have verified the interval and groupBy parameters against the documentation.

Troubleshooting

  • Confirmed the startDate and endDate are in ISO 8601 format.
  • Validated that the viewId exists and has the correct permissions.
  • Checked that the time range contains actual conversation data using the UI.
{
 "interval": "PT15M",
 "groupBy": ["channel"],
 "metrics": ["handledCount"],
 "filters": {
 "type": "AND",
 "clauses": [
 {
 "dimension": "queue.id",
 "operator": "equals",
 "value": "queue-uuid-here"
 }
 ]
 }
}
2

It depends, but generally… the issue stems from how the groupBy parameter interacts with the interval definition in the query payload. The suggestion above regarding valid parameters is technically correct, but it misses the critical structural requirement for custom intervals. When you specify a custom interval like PT15M, the API expects the groupBy array to include time or a specific time dimension that aligns with that granularity. If you omit time from groupBy, the engine cannot bucket the data into your 15-minute windows, resulting in an empty dataset.

In my MuleSoft orchestration layers, I always validate the interval against the groupBy fields before sending the request to Genesys Cloud. You must ensure that the interval matches a supported duration (e.g., PT1M, PT5M, PT15M, PT1H, P1D) and that time is present in the groupBy list. Additionally, check your filters. If you are filtering by a specific queue or user, ensure that entity had active conversations during that exact 15-minute window. A common mistake is using routing:queue:view scope without ensuring the queue ID is correct.

Here is a corrected JSON payload structure for the POST request to /api/v2/analytics/conversations/details/query:

{
 "interval": "PT15M",
 "groupBy": [
 "time",
 "routing.queue.name"
 ],
 "metrics": [
 "conversationCount",
 "talkTime"
 ],
 "filters": {
 "type": "conversation",
 "time": {
 "type": "absolute",
 "from": "2023-10-27T14:00:00.000Z",
 "to": "2023-10-27T14:15:00.000Z"
 }
 }
}

You must also verify that the time filter uses absolute timestamps in ISO 8601 format. If you use relative time, ensure the from and to values are calculated correctly in your Java client. The PureCloudPlatformClientV2 SDK handles this, but manual JSON construction often fails due to timezone offsets. Always log the raw request body to debug these discrepancies.

3

make sure you use the /api/v2/analytics/conversations/aggregates/query endpoint instead of details. the docs state “the aggregates endpoint returns summary metrics while the details endpoint returns individual interaction records” so your empty result is expected.

4

Have you tried switching to the aggregates endpoint? the suggestion above is spot on. you’re hitting /details which needs individual records. use /api/v2/analytics/conversations/aggregates/query instead. ensure your groupBy includes time for PT15M intervals. that mismatch causes the empty set.