FrankOMartin | 2020-07-03 14:50:30 UTC | #1
Hello Forum,
I'm currently diving into the Genesys API and try to understand the options for getting data out of the system into a DWH.
After exploring the Analytics API and requesting data via the /api/v2/analytics/conversations/details/query endpoint I try to understand the Notification API and the data structure that is provided by the websocket interface.
While subscribed to the v2.routing.queues.{id}.conversations topic I made a call and got 24 blocks of the SCHEMA that is described on https://developer.mypurecloud.com/api/rest/v2/notifications/available_topics.html which totals to nearly 5k rows of data output.
The same call queried via the /api/v2/analytics/conversations/details/query endpoint is as compact as 373 lines of JSON and has a different structure (Conversation > Participant > Session > Segment). The documentation (https://developer.mypurecloud.de/api/rest/v2/analytics/) in combination with some test data provides me with enough information to get data from that interface.
The Notification API is much harder to understand. I desperately miss some (more) detailed documention about the structure of the data that is yielded. And also about the relation to the data provided by the Analytics data.
Is there any documentation that elaborates more on the details of the v2.routing.queues.{id}.conversations topic ? And how this topic relates to the corresponding analytics api?
Best regards, Frank
tim.smith | 2020-07-07 13:23:03 UTC | #2
Conversations APIs have a different schema than Analytics APIs. The conversations notifications correspond to the Conversations APIs. They both have the same data, just different structures. (with the exception of analytics not having participant attributes, unless you're using an export job).
system | 2020-08-06 13:23:05 UTC | #3
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: 8185