Working on a script to pull detailed conversation logs for the last quarter. The volume is high, so pagination is a must. The docs for /api/v2/analytics/conversations/details/query mention cursor but the SDK methods I’m looking at seem to default to page-based logic. I’ve tried passing a cursor string in the request body, but the response just ignores it and returns the first 1000 records every time. Here’s the payload I’m sending:
{
"dateFrom": "2023-10-01T00:00:00Z",
"dateTo": "2023-12-31T23:59:59Z",
"size": 1000,
"cursor": "eyJpZCI6IjEyMyJ9"
}
The response comes back with a 200 OK but no new cursor in the header or body. I checked the response headers and there’s no Link header either. Am I missing a specific header or query param to enable cursor-based pagination? Or is this endpoint strictly page-based despite what the schema hints at? I’ve tried using the page parameter as a fallback but it feels brittle for large datasets. Any pointers would be appreciated.