Pulling conversation details for a QA audit using the /api/v2/analytics/conversations/details/query endpoint. The docs mention a paging object with pageSize, pageNumber, and pageCount. I’m trying to get 500 records in one go, so I set pageSize to 500. But the response only gives me 250. The pageCount in the response header says 2, which makes sense if the max page size is 250. I tried setting pageNumber to 2 to get the next batch, but the response is empty. No error, just an empty array in the data field. I checked the request headers, and the Accept header is application/json. The OAuth token is valid, and I can query other endpoints without issues. Here’s the JSON payload I’m sending:
{
“dateFrom”: “2023-10-01T00:00:00.000Z”,
“dateTo”: “2023-10-07T23:59:59.999Z”,
“paging”: {
“pageSize”: 500,
“pageNumber”: 1
},
“groupBy”: [“conversationId”]
}
The response has a total of 450 records, but I only get the first 250. The pageCount is 2. I expected the API to ignore my pageSize if it exceeds the max, but it doesn’t throw an error. It just silently caps it. Then when I increment pageNumber, I get nothing. I’m using the Python SDK, but I’ve also tested with Postman to rule out SDK bugs. The issue seems to be how the paging object is interpreted. Is there a specific way to handle the pageCount? Should I be using cursor-based paging instead? The docs are vague on this. I’ve tried setting pageSize to 100, and it works fine, returning 100 records per page. But I need to pull large datasets efficiently. Any ideas on how to correctly paginate through large result sets without hitting this wall?