Is there a difference in pagination between conversations and userdetails?

[LvR]

Hello,

I’m using SSIS and a zappysys plugin to get conversation details and user details from the genesys api.

If I post to the end point: https://api.mypurecloud.ie/api/v2/analytics/conversations/details/query I can use pagination to get all pages within my interval (last week). I filter on the array: $.conversations[*]

If I post to the end point: https://api.mypurecloud.ie/api/v2/analytics/users/details/query and use pagination to get all pages I only get a part of my resultset. I filter on the array: $.userDetails[].primaryPresence[]

Body (request data):
{
"interval": ""2024-09-25T00:00:00.000/2024-09-30T00:00:00.000""
, "paging": {
"pageSize": 100,
"pageNumber": <%page%>
}
}

I start on page 1 and use an increment of 1 page. This works for conversations but not for userdetails.
Anyone an idea what the problem might be? Any pointer would be helpfull.

[Eos_Rios]

Yes, assuming you're using GET /api/v2/analytics/users/details/jobs/{jobId}/results

That API uses a cursor system.
You can see the API documentation here - GET /api/v2/analytics/users/details/jobs/{jobId}/results

There's an explanation of how the cursors work versus normal pagination here.

[LvR]

Thank you for your response. No I'm using:

POST /api/v2/analytics/conversations/details/query
and
POST /api/v2/analytics/users/details/query

I will look into the job and the cursor but for now I want to be able to get up-to-date data, so that's why I choose the query. But both options have a different kind of paging result which I don't understand.

[Eos_Rios]

That should be working and might be a bug you need to report to customer care.

[tim.smith]

@LvR

POST /api/v2/analytics/conversations/details/query
and
POST /api/v2/analytics/users/details/query

Both of these use numbered pages per the documentation. (Jobs are different endpoints and use cursors)

• POST /api/v2/analytics/users/details/query
  POST /api/v2/analytics/conversations/details/query

@LvR

This works for conversations but not for userdetails.
Anyone an idea what the problem might be?

What is the problem you're having? In what way is it not working?

[LvR]

@tim.smith
Using POST /api/v2/analytics/users/details/query I expect 866 records back (totalhits = 866) and since the page size is max 100 I expect 9 pages. I only get back 2 pages. (I store filename for testing, which is the page number). Now I miss a lot of data (test cases, so I know what I am missing).

My SSIS code is a copy of my POST /api/v2/analytics/conversations/details/query and this is working good. I get back all expected pages. That's why I asked if there is any known difference in the two end points.
Any idea?

[tim.smith]

It could be because of division access or something else, but we can only make uneducated guesses in this setting. Please open a case with Genesys Cloud Care to investigate missing data; we don't have access to your org's data via the forum.