Detail Query to retrieve Queue IDs from interaction not working

Hi all.

I am trying to use the POST /api/v2/analytics/conversations/details/query

Goals + info.
(1) Architect runs this DATA action submitting the Interaction ID from a previous data action to retrieve all the Queue IDs that interaction has recorded in what i think should be the PURPOSE=ACD section (but open to ideas)
(2) Those Queue IDs are then sorted in Desc order.
(3) These interactions are either Voice or Callbacks, inbound or outbound, ACD or NON ACD calls (so there may actually be NO QUEUE IDs to retrieve in many cases)
(4) Take the most recent Queue ID (based on latest time stamp by sort desc process) and pass that back to my Architect flow
(5) This interaction we are querying will have just ended (so does that mean we us conversationEnd = Exists and segmentEnd = Exists? given this could be a NON ACD call with NO Queue IDs or an ACD call wtih Queue IDs and agent would be in wrap up / after call work stage of the call)
(6) I only want 1 Queue ID returned to Architect, that is the MOST RECENT one.

I am having trouble building the query in the new Api Explorer. So far i have this setup and i can't seem to get it to run. I am new to this APi explorer and struggle to understand it.

QUERY

{
"conversationFilters": [
{
"predicates": [
{
"type": "dimension",
"dimension": "conversationId",
"operator": "matches",
"value": "12871da8-57af-4c3e-8f56-3c67decb7e9a"
}
],
"clauses": [
{
"type": "and"
}
]
}
],
"order": "desc",
"orderBy": "conversationEnd",
"paging": {
"pageSize": 1,
"pageNumber": 1
},
"segmentFilters": [
{
"predicates": [
{
"type": "property",
"dimension": "mediaType",
"operator": "matches",
"value": "voice",
"propertyType": "string"
},
{
"type": "dimension",
"dimension": "purpose",
"operator": "matches",
"value": "acd",
"propertyType": "string"
}
]
}
]
}

Trying this input/output contract.. Given i KNOW the Interaction ID, i shouldn't need to input Date right? (eg. 2023-11-03T01:30:30.000Z/2023-11-03T23:30:30.000Z
)

I am getting this output error

{
"message": "type is required",
"code": "bad.request",
"status": 400,
"messageParams": {},
"contextId": "53ea5ca8-398d-49ef-ab5c-87cc12ada627",
"details": [],
"errors": []
}

I always recommend that developers nail down their API usage in something like postman or the API explorer prior to attempting to create a data action, so in this case I would keep troubleshooting the issue with the analytics explorer, or ask this room for help:

I do think that a time range is always required.

--Jason

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.