Legacy Dev Forum Posts

Darren_West | 2020-02-20 13:14:45 UTC | #1

Hi,

I am looking at using the endpoint /api/v2/analytics/conversations/details/jobs to retrieve all the conversations that have finished in a day.

When I do the query for yesterday I get no calls with conversationEnd attribute which is different from what I get on the non-async calls and I know to be incorrect. Is there some sort of batch process that runs to add the conversationEnd because I notice it works if I go two days back?

I cannot use the non-async endpoints because I need the attributes we have set for a call.

This is for the query:

{
   "interval": "2020-02-18T00:00:00/2020-02-18T23:59:59",
   "SegmentDetailQueryClause": {
     "predicates":[
        {
          "dimension":"mediaType",
          "value": "voice"
        }
      ]
   },
   "conversationFilters":[
      {
        "type": "and",
        "predicates":[
          {
            "dimension": "conversationEnd",
            "operator":"exists"
          }
        ]
      }
    ],
   "order": "asc",
   "orderBy": "conversationStart"
}

Thanks in advance

tim.smith | 2020-02-20 21:54:52 UTC | #2

Per https://developer.mypurecloud.com/api/rest/v2/analytics/conversation_details_job.html, emphasis added:

An important consideration is that the jobs-backed data is not continuously updated in real-time and so depending on when you query, you may not see up-to-the-moment data. While your job might execute and have results for you ready in seconds, the data it can search/return may not be up-to-date for on the order of hours to a full day behind real-time.

Darren_West | 2020-02-21 10:31:23 UTC | #3

Thanks for getting back to me.

Is there a way of knowing where you are up to in populating the data?

i.e I want to pull all the data from time x to now but I want to stop until the data is present in your api. Is it safe to say it is never more than a day behind?

tim.smith | 2020-02-21 19:54:54 UTC | #4

It's a nightly process that aggregates the job data. The 24 hours statement is a generalization about how long it will be until the job completes running next time. It's not currently possible to know how up to date your data is except that it's not older than approximately 24 hours. An app should be perfectly safe to pull data starting at 2 days old, if that's an acceptable delay.

It would be a nice enhancement to add a last synced timestamp to the job results to be able to know precisely how up to date the data is. You can request this enhancement and share your use case at https://purecloud.ideas.aha.io/ideas.

system | 2020-03-22 20:00:59 UTC | #5

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

This post was migrated from the old Developer Forum.

ref: 7169