Pearlsia_Jamadin | 2017-08-22 00:16:17 UTC | #1
Hi,
We are tasked to pull conversations data from Purecloud. Is there a way to just grab all the data without having to provide the conversationID param? If it is really not an option, would there be a way to generate all the conversationID into a csv file so we can just work our way to just passing this param values?
Your help is much appreaciated.
Thanks.
Rick_McGlinchey | 2017-08-22 00:47:15 UTC | #2
Hi - I'm with a technology partner of Genesys that is called PureInsights and we have a low cost option to extract PureCloud conversation detail into a CSV using only a date range and the desired queues as parameters. For more complex needs, we have another offering to extract your PureCloud data into a hosted Oracle database so you can access it using SQL query and business intelligence tools. You might find this easier and more affordable than having to build and maintain your own integration using the API - we've already solved that and done all the heavy lifting.
See mypureinsights.com for more information or feel free to contact me directly.
best regards, Rick McGlinchey Co-Founder, PureInsights
tim.smith | 2017-08-23 15:02:36 UTC | #3
You'll want to use the Analytics APIs to query for conversation details. This will allow you to provide the interval for which to retrieve conversations as well as applying additional filters to choose only conversations that meet your filter criteria.
Additionally, there's an open source project that can automate this process for you. Some of the examples may already be close to what you're looking for: https://github.com/MyPureCloud/open-data-exporter
Dariusz | 2017-08-23 16:37:45 UTC | #4
Hi, You can also check the PureCloud Stats Dispatcher. It's an open source tool that allows to export the conversations data from Analytics API into SQL database or CSV file.
https://bitbucket.org/eccemea/purecloud-stats-dispatcher
system | 2017-09-23 16:38:21 UTC | #5
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: 1705