Query transactions by date range and paginate results

The GET /v1/banking/transactions endpoint supports date range filtering and cursor-based pagination. Full parameter and schema details are in the API reference.

Filter by date range

Use the from and to query parameters to limit results to a time window:

GET /v1/banking/transactions?end_user_id={id}&from=2025-01-01T00:00:00Z&to=2025-02-01T00:00:00Z

Both accept RFC 3339 datetime strings. If from is omitted, results include all available transactions up to the to date; if to is omitted, results extend to the present.

Date filtering compares against each transaction's posting_datetime, falling back to execution_datetime when the posting datetime is empty. Transactions with neither datetime are excluded from date-filtered results. See Transaction datetimes for what each field means.

How far back results can go depends on your consent configuration and the institution — see Statements and history depth.

Paginate

The endpoint returns at most 1000 records per page (configurable with page[size]). When more pages are available, the response includes pagination links with a page[after] cursor:

1. Request the first page with your filters.
2. Follow the next-page link (or pass its page[after] cursor) to fetch the next page.
3. Repeat until the response contains no next-page link — you have reached the last page.

Incremental syncs

To fetch only transactions newer than a known point, set from to the datetime of your most recent stored transaction rather than re-pulling full history:

GET /v1/banking/transactions?end_user_id={id}&from=2025-06-15T10:30:00Z

Scope to a single account

Add the account_id parameter to retrieve transactions for one account only:

GET /v1/banking/transactions?end_user_id={id}&account_id={account_id}&from={from}&to={to}

Account IDs are returned by the GET /v1/banking/accounts endpoint.