Skip to main content
Paginated endpoints use offset pagination with two query parameters:
Not every endpoint enforces the same pageSize ceiling, and a few enforce none at all. Each endpoint’s reference page states its own limit.

​
Two response shapes

Paging metadata comes back in one of two shapes, depending on the endpoint. Check the endpoint’s reference page rather than assuming.

​
Flat inside data

The transaction and beneficiary listings put the rows and the paging counters side by side inside data:
Used by List Transactions, List Wallet Transactions, and List Beneficiaries. List Accounts and List Transactions Across Accounts use the same shape plus a boolean hasMore. Those two are the only endpoints that return it, so iterate on page against totalPages everywhere else.

​
Nested pagination object

The team, broker, and payer-name listings nest the counters under pagination, and the total is named total rather than totalCount:
Used by Get Team Members, Get Commissions, and List Payer Names. Get Referred Businesses is the one exception to both shapes: its data is the array of rows itself, and pagination sits beside data at the top level of the response rather than inside it.

​
CSV exports

List Transactions Across Accounts with format=csv returns the file as the response body, so its paging metadata travels in response headers instead:
Export Transactions behaves differently: it does not return a CSV body at all, but a JSON response carrying a signed download URL.

​
Unpaginated lists

A few small collections return the full array in one response with no paging parameters — Get Virtual Accounts, List Bank Accounts, and List Banks among them. Each endpoint’s reference page states which behaviour it uses.