Backfill bank account history

Imports historical bank transactions for this account from the provider over a date range, then runs matching against the account's full current card set. Unlike the backfill object on PATCH /bank-accounts/{bankAccountId} — which imports history for cards being added in that same request — this endpoint recovers a date window without touching card links.

Requires a backing connection. Starting a backfill while another sync already holds the account's connection returns 409 Conflict; retry shortly.

For Mastercard-provider accounts, loadHistoric: true additionally asks the provider to generate deep history (up to 2 years) for this account before the import runs. This is a billable provider operation and generation is asynchronous on the provider side: if the immediate import returns few rows, re-run the same window without the flag once generation completes (typically within minutes). Providers without a deep-history operation reject the flag with 400 Bad Request.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
Body Params

Date range to import. Both bounds are optional; send an empty object for the default window.

date

Start of the range in YYYY-MM-DD format. Defaults to 90 days ago.

date

End of the range in YYYY-MM-DD format. Defaults to today.

boolean

Mastercard-provider accounts only. Triggers the provider's billable deep-history generation (up to 2 years) for this account before the import. Generation is asynchronous — re-run the window without the flag if rows are missing. Providers without the capability return 400.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
OAuth2
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json