mary8886 | 2020-07-15 21:22:37 UTC | #1
I'm curious what are methods that others have employed to expose data for reporting?
My initial approach was to use Denodo to call the API. The hope was that I could expose a Denodo view to the end users, each time they use the view, it would call the API. But, there were a few items that became blockers within the Denodo application. I'm curious how else others are able to expose the data to their business for reporting. As far as I'm aware, the BI tools our business partners use do not have a PureCloud connector. Although, they could use a web service connector, they will likely encounter similar blockers as Denodo (i.e. encoding url parameters, accessing a dynamic endpoint).
Also, is it common for organizations to replicate PureCloud data to a physical data store?
tim.smith | 2020-07-15 21:28:16 UTC | #2
Historical Genesys Cloud data is obtained using the Analytics APIs, particularly the conversation detail query and conversation detail job. If the application you're using isn't capable of consuming these REST APIs, you will need to write some sort of middleware to fetch data from Genesys Cloud and deliver it to your application in a format your app can consume.
mary8886 | 2020-07-16 13:55:04 UTC | #3
@tim.smith, what is the data retention for the historical data in Analytics API: conversation detail job? Thank you.
tim.smith | 2020-07-16 21:20:12 UTC | #4
Analytics data is available forever. Conversation APIs are 90 days.
mary8886 | 2020-07-17 14:47:39 UTC | #5
@tim.smith I apologize for a request on clarification, the analytics data is available forever. What do you mean by conversation API are 90 days? Is that the max interval we can return in a response? We can return up to 90 days worth of data per call?
Thank you.
Jerome.Saint-Marc | 2020-07-20 08:19:09 UTC | #6
Hello,
There are 2 "repositories" for conversation data in the PureCloud platform.
When a conversation is created, its data can be retrieved:
- via the Conversation API (requests starting with /api/v2/conversations) for up to 90 days after the conversation happened.
- via the Analytics API (requests starting with /api/v2/analytics)
Analytics data is available immediately (while the conversation is active) and is kept forever. From 0 to 90 days, you can retrieve data via the 2 APIs (Conversation API and Analytics API). After 90 days, the data is only available via the Analytics API.
Regards,
mary8886 | 2020-07-20 18:47:05 UTC | #7
@Jerome.Saint-Marc Thank you for the clarification. May I ask the top half of the endpoints in the Conversation API documentation points to the analytics repository? I assume those are the exact same endpoints in the Analytics API documentation and data is kept forever.
Jerome.Saint-Marc | 2020-07-20 19:58:29 UTC | #8
I wouldn't say half of the endpoints :slight_smile: Just 9 out of many. And yes, these 9 endpoints are the same than in the Analytics API documentation. As you can note, they are using the same HTTP method and have the exact same url.
I guess it is just to make it easy to find what relates to conversations in a single page.
As I mentioned above, what we refer to as Conversation API are all request urls starting with /api/v2/conversations. Ex: /api/v2/conversations/{conversationId}, /api/v2/conversations/{conversationId}/participants/*, /api/v2/conversations/calls/{conversationId}, ...
Analytics related endpoints start with /api/v2/analytics.
system | 2020-08-20 19:58:31 UTC | #9
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 8295