Skip to main content
The endpoint follows the standard cursor-based pagination contract used across the Embedded Banking REST API. The Quick reference lists the defaults at a glance.

​
Sweep loop

To read an account’s full ledger:
  1. Make the first request with the desired limit and any filters.
  2. If the response includes a non-null nextPaginationToken, pass it as pagination_token on the next request — without changing limit or filters.
  3. Stop when nextPaginationToken is null. That is the only valid stop condition.
A short page is not a stop signal. The cursor may return fewer items than limit even when more pages exist. Drive the loop off nextPaginationToken alone.

​
Opaque tokens

Pagination tokens are opaque. Do not parse, decode, base64-strip, or otherwise inspect them. Do not construct one yourself. Do not assume any structure. The format may change at any time without notice — only round-trip the value the API returned.
Persisting a token across processes is fine; treating it as data is not. If you need to resume a sweep later, store the token verbatim and pass it back unchanged.