Skip to main content
Build a dashboard that shows a user’s linked accounts, recent transactions, financial health scores, and recurring bills — all from a single API key.

Fetch the overview

Start with GET /me/summary to get accounts, scores, and goals in one call:
This single call replaces three separate requests to /accounts, /scores, and /goals.

List recent transactions

Fetch the latest transactions across all accounts:
Filter by account to show transactions for a specific card or bank account:

Show balance history

Plot account balances over time with the balance series endpoint:

Add recurring streams

Show subscriptions, bills, and income streams:

Caching strategy

Not all data changes at the same rate:
Use webhooks instead of polling. Subscribe to transaction.created and balance.updated events to refresh your dashboard in real time.

Polling vs webhooks

For a simple dashboard, poll on a timer:
For real-time updates, register a webhook endpoint and listen for events:

Handle pending transactions

Transactions can arrive in a pending state before they post:
Pending transactions may change amount, date, or even disappear before posting. Always use the transaction id for deduplication — don’t rely on amount or description matching.

What’s next

Webhooks

Set up real-time updates instead of polling.

Data freshness

Understand when and how data syncs.
Last modified on April 30, 2026