Cursor Pagination

Use cursor pagination to retrieve results one page at a time from supported endpoints.

A cursor token tracks your position in a result set. The server generates a token and returns it in each response; pass that token in your next request to retrieve the next page.

FIRST and LAST do not require a token. NEXT and PREVIOUS require a token returned by a prior API response. Do not construct the token manually.

Retrieve pages

1. Start at the beginning

GET /api/rest/v1/statistics/tags/{tagID}?cursor.pageRequest=FIRST&cursor.pageSize=20

{
  "result": [...],
  "cursor": {
    "currentPage": "eyJjdXJyIjoiLi4uIn0=",
    "hasNext": true,
    "hasPrevious": false
  }
}

When hasPrevious is false, you are at the start of the result set. When hasNext is true, another page is available.

2. Retrieve the next page

Copy cursor.currentPage from the response verbatim and pass it back:

GET /api/rest/v1/statistics/tags/{tagID}?cursor.pageRequest=NEXT&cursor.pageSize=20&cursor.currentPage=eyJjdXJyIjoiLi4uIn0=

The server continues from the previous position and returns a new token.

3. Continue until the final page

Repeat the request with the latest cursor.currentPage value until hasNext is false. A value of false means you reached the end of the result set.

pageRequest Values

Endpoints That Support Cursor Pagination

Troubleshoot invalid cursor errors

E900-INVALID_CURSOR_DATA

This error means the cursor token is invalid. It occurs when you construct cursor.currentPage manually instead of copying it from an API response.

The server base64-encodes and serializes the token internally. Copy cursor.currentPage directly from the prior response, without modifying it, before you send the next request.