Skip to main content
All list endpoints share the same conventions for paging through results, narrowing them down, and controlling what related data is embedded.

​
Pagination

List endpoints are paginated with page[number] and page[size] query parameters:
  • Default page size: 25
  • Maximum page size: 100
Responses wrap the results in data and include links and meta for navigation:
Iterate by following links.next until it is null, or use meta.last_page.

​
Filtering

List endpoints accept filter[...] query parameters. The available filters for each endpoint are listed on its reference page. For example, transactions support filters such as:
Date-range filters (booking_date_after, booking_date_before, value_date_after, value_date_before) are inclusive on both ends. Multiple filters combine with AND. Where a filter accepts multiple values, separate them with commas:

​
Sorting

Use the sort parameter with a field name; prefix with - for descending order:
Sortable fields per endpoint are listed in the reference. Some endpoints can embed related resources in the response via the include parameter, saving you extra round trips:
For example, transactions support includes such as financial_account (and its connection and institution via dot notation, like financial_account.financial_connection.institution), transfer_logs, enriched (transaction enrichment data), and trade (brokerage trade details). Available includes are documented per endpoint in the reference; fields backed by an include are absent unless you request it.