Clarification regarding Pagination for API based data extracts

[Vinay_Katta]

Hi All,

We would like to seek clarification regarding Pagination for API based data extracts through Python.

We have observed there is a limit on page size for extracting the data for Conversation Detail and Masters (Routing Queue, DNIS, Routing Language, Routing Skills and Users) through API. The default page size is 25. Our requirement is to extract the complete set of data for a given date range (applicable for Conversation Detail)

If we go with the default page size of 25, the observation is some records are not getting extracted for Masters. Later when we increased the page size, all the data got extracted. The same is applicable for Conversation Detail.

Questions

1. Is there any recommendation for setting the page size ? What is the best practice to follow ?
2. Is there any parameter to set so that all the data is extracted without omitting any records. I understand for Transactions i.e. Conversation Detail, we have set a date range.
3. While going through the Genesys documentation (https://developer.genesys.cloud/platform/audit/usecursor) , we came across “Cursors”. How do we obtain value for Cursor ?

Thanks & Regards,

Vinay

[ralegner]

1. It'd be helpful for you to list out the specific endpoints you're pulling data from. Different endpoints source for different services which can have varying payload or page size limitations.
2. We have realtime topics for unbounded "get everything" style of data consumption. https://developer.genesys.cloud/notificationsalerts/notifications/available-topics Historic data from the current endpoints all will require some sort of data criteria. The endpoint available that's best suited for bulk extraction is the analytics jobs endpoint that contains conversation detail records. https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job
3. An example of cursor usage is indicated on the jobs documentation page https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job#example-queries

[Vinay_Katta]

Hi,

API Endpoints for Masters

    GET api/v2/flows/datatables/
GET api/v2/routing/language/
GET /api/v2/routing/queues/
GET api/v2/routing/skills/
GET api/v2/users/

For the Conversation Detail, we are calling the package PureCloudPlatformClientV2.ConversationsApi()

Let me know if you need any other details for # 1.

Thank you for sharing the details for # 2 & # 3. Will go through it and revert to in case of any questions.