Pulling conversation detail records via GET /api/v2/analytics/conversations/details for a post-call quality audit tool in our Android app. The response payload consistently returns null for the wrapUpCode field, even when I know for a fact the agents selected a specific code in the UI.
I’ve checked the raw JSON response and the structure looks standard:
{
"fromDateTime": "2023-10-27T08:00:00.000Z",
"toDateTime": "2023-10-27T18:00:00.000Z",
"groupings": [
{
"type": "wrapUpCode"
}
],
"selectionCriteria": {
"query": "conversationId:12345"
},
"aggregations": []
}
The conversation object in the returned detail items has the wrapUpCode field present but empty. Is this a known limitation of the detail endpoint versus the summary endpoint? I tried adding wrapUpCode to the groupings array as shown above, but it didn’t populate the value. The summary endpoint /analytics/conversations/summary seems to handle this grouping better, but I need the granular detail data for the specific conversation logs.
Any idea if I’m missing a specific header or if the data just isn’t exposed in the detail view yet?