Interval query for /api/v2/analytics/conversations/details/query

[prem.sharma]

Our clients schedule calls on genesys We use the conversation details query api with the below query. with intervals of 30 minutes to get all calls that ended in last 30 minutes.
{
"interval": "<start_time>/<end_time>",
}
Using this query we get the call on the day the customer created the schedule however on the day the call took place the call is not available on the response.

I went through some documentation and found that the interval query goes through a daily index and will not include the calls if the interval does not touch the day the call started. The way to get the call would be to increase the interval duration to include the start day of the call. This would however lead to unnecessary fetch of data from genesys and will also result in higher load on your servers as we would have to get the data for several days to get these calls.

I found another way to get the filtered calls via another API in the documentation. it mentioned we can use startOfDayIntervalMatching to control the usage of index.

In light of this, we have several questions that require clarification:

1. Is there a better way to get the calls that may span several days.
2. Is there a way we can pass some flag to the conversations/details/query api to ignore the daily index limitation just like the conversation details job api
3. Since interval query filters on the calls that end within the interval can the index be on the end date rather than start date? It seems inconsistent that the filter is using an index on a different field.
4. Is there is a different better way to get the metadata of these calls on the day the call took place.
5. Also we noticed for these calls the value we get in conversationStart is the not the start time of the conversation between agent and customer rather it was the time when the call was scheduled. Is there a way we can get the conversation start time in this metadata instead of the scheduled time? Or is there a different metadata field in the response that can help us identify the start time of the call correctly.

[Eos_Rios]

1. Use conversation details job api
2. No, because they made conversation details job api able to do that and the query API is only for small datasets and/or short periods of time.
3. They're not going to drastically change the behavior now.
4. They want you to use event bridge and put it in your own thing not use the API, so no.
5. Not without making your own way from the available data.

If you haven't already, you can refer to https://genesyscloud.ideas.aha.io/ideas for the backlog of wishlists and ideas and hopes and dreams you can add to and support.