Pagination

List endpoints that may return large result sets are paginated.

Request Parameters

Pagination parameters are accepted as query parameters (or request-body fields, depending on the endpoint contract):

Parameter	Type	Default	Description
page	integer	0	Zero-based page index.
size	integer	20	Page size. Maximum recommended value is 100.
sort	string	varies	Sorting in the format field,asc or field,desc. Endpoint specific.

Refer to each endpoint's documentation for the exact parameter location and any additional filters.

Response Envelope

Paginated endpoints return:

{
  "content": [ /* page of items */ ],
  "page": 0,
  "size": 20,
  "totalElements": 137,
  "totalPages": 7
}

Field	Description
content	The array of items for the requested page.
page	Zero-based page index returned.
size	Page size used.
totalElements	Total number of matching items across all pages.
totalPages	Total number of pages available given the current size.

Iterating Pages

A simple loop pattern in pseudocode:

page = 0
loop:
  result = GET /transactions?page=page&size=50
  process(result.content)
  if page + 1 >= result.totalPages: break
  page = page + 1

Recommendations

• Use the smallest page size that meets your need. Smaller pages return faster.
• Don't fetch every page on each polling cycle. For status polling, query by transactionId instead.
• For exports of historical data, use the largest reasonable page size (e.g. 100) and iterate.

---

Last updated: April 2026