Pagination

A paginated list answers one page of items and a next_cursor, which the next request passes back as its cursor, with a limit from 1 to 200 (50 by default).

Request a page

A paginated list operation returns one page: items and a next_cursor. List providers returns only items and takes no pagination parameters. Pass the next_cursor back as cursor to read the next page, and set the size of a page with limit, from 1 to 200, 50 when you leave it out. The next_cursor is null on the last page. A cursor is opaque: pass back exactly what a page returned and never build or change one.

{
  "items": [],
  "next_cursor": null
}

Follow the cursors

Request the first page without a cursor, then repeat the request with each next_cursor until it is null, and send the same filters with every page. The API client of the SDK does this for you: the SDK API client page shows listGamesAll.

Order and filters

List games filters by provider, category, currency and device. List rounds and List transactions filter by playerId, gameId, from and to, where from is inclusive and to is exclusive, and return the newest first. The catalogue reads its query strictly: a key sent twice, a key the operation does not declare, a limit that is not a plain integer and a cursor that no page returned are each 400 with MALFORMED_REQUEST; the errors page lists the codes.