Running into a weird issue with the pageSize parameter on /api/v2/analytics/conversations/queries. The docs say it defaults to 100, but when I set it explicitly to 50 in the request body, the response pageCount stays at 1 even though I know there are more records.
Here’s the payload I’m sending:
{
"pageSize": 50,
"pageNumber": 1,
"dateRange": {
"startDate": "2023-10-01T00:00:00.000Z",
"endDate": "2023-10-02T00:00:00.000Z"
}
}
The response comes back with a 200 OK, but the results array only has 42 items. The paging object in the response looks like this:
"paging": {
"pageSize": 50,
"pageNumber": 1,
"pageCount": 1
}
I thought pageCount would tell me how many pages exist so I can loop through them. It’s acting like 42 is the total universe of data here. Am I misreading the spec? Or does pageCount only reflect the current batch if the server decides to cap it early?
Trying to build a Kotlin wrapper around this and the pagination logic is breaking because I can’t trust the pageCount field to drive my loop. Just getting the first chunk and stopping feels wrong.