Cursor pagination issue with /api/v2/analytics/conversations/details/query

Building a New Relic integration to track conversation metrics. The /api/v2/analytics/conversations/details/query endpoint is returning inconsistent cursors. I’m using the nextPage token from the response headers, but subsequent requests return duplicate data.

POST /api/v2/analytics/conversations/details/query
{
  "dateRange": {
    "start": "2023-10-01T00:00:00.000Z"
  },
  "pageSize": 100
}

The 200 OK response includes a cursor, but the next call doesn’t advance properly. Is this a known SDK limitation?

3 Likes