Banking data

The Data API returns consumer banking data that an end user has agreed to share through a consent. Once a user connects an institution, you can retrieve:

• Accounts — the accounts included in the consent, with product and account details.
• Balances — current and available balances per account.
• Transactions — line-item transaction data, including statements-grade history going back months or years depending on the institution and your consent configuration.

Data is synced from each institution (the data holder) after a consent is created and refreshed on an ongoing basis. Because institutions serve data at different speeds, freshness and history depth vary — the articles in this section explain what to expect and how to build around it.

In this section

• Data freshness and refresh timing — see how recent your data is and get it faster.
• Date ranges and pagination — query transactions efficiently.
• Filtering by status — handle pending vs posted transactions.
• Transaction datetimes — which timestamp fields to rely on.
• Missing or duplicate transactions — diagnose gaps and doubles.
• Statements and history depth — how much history you can retrieve.
• Unsupported account channels — when accounts can't be shared.

For endpoint schemas and request examples, see the API reference.