Pagination

Some list endpoints return paginated results. Stables uses cursor-based pagination, with two styles depending on the endpoint group.

Pagination parameter names vary by endpoint group. Always refer to the individual endpoint's API reference for the exact query parameter and response field names.

Page tokens

Used by List Transfers, List Customers and the balance lists (/api/v1/prefund/activity, /api/v1/prefund/whitelisted-wallets).

Query Parameters

ParameterTypeDescription
page_sizeintegerMaximum number of records to return (1 to 100)
page_tokenstringOpaque token from the previous response's next_page_token

Pagination Fields in Response

Endpoint groupNext tokenAlso returnedLast page
Transfers, Customerspage.next_page_tokenpage.totalnext_page_token is empty
Balancesnext_page_tokenhas_morehas_more is false

On List Customers, page is only returned when you pass page_size. Without it, every customer is returned in one response.

Starting after an id

Used by the virtual account lists and virtual account history.

Query Parameters

ParameterTypeDescription
limitintegerMaximum number of records to return (1 to 100, default 10)
starting_afterstringCursor: the id of the last item from the previous page
ending_beforestringCursor: the id of the first item from the previous page

Pagination Fields in Response

EndpointFields
List Virtual Accountsdata, and count (the total number of matching virtual accounts)
Virtual account historydata, and has_more (whether more results exist)

Example

GET /api/v1/customers/{customerId}/virtual-accounts?limit=20&starting_after=550e8400-e29b-41d4-a716-446655440000

Other lists

  • List RFIs takes limit (default 50) and cursor, and returns next_cursor, which is absent on the last page.
  • List webhook deliveries takes pageSize and pageToken, and returns page.nextPageToken, which is empty on the last page.

On this page