Skip to main content
Didit’s Sync Now reads the bank for the latest data of a connection at any moment, with one call. Live syncs are included in the monthly price of the connection: nothing extra is charged. The only limit is the bank’s.

The automatic sync

  • The first sync runs when the person connects.
  • After that, every active ongoing connection syncs automatically between one and four times a day, depending on the bank. sync.frequency_per_day on the connection says how many, and sync.next_sync_at when the next one is planned.
  • Where the bank allows more unattended reads a day, at least two a day always remain for live syncs.
  • When a sync stores changes, bank.data.updated arrives and you read the change feed with your cursor.
  • A sync that fails is retried with backoff. After 24 hours of failures the connection stays active with sync.status: failing, and bank.sync.failed is sent. bank.sync.recovered follows when it works again.
  • When the bank asks the person to sign in again, the connection becomes renewal_required.

Sync now, in one call

Add "wait": true and one request returns fresh data:
The header Prefer: wait=25 does the same. The call holds for up to 25 seconds:
If a sync is already running you get that same sync_id, not a second job. After a 200 or a bank.data.updated, read the change feed with your stored cursor. Read what a sync did later with get_sync_run.

The price

Automatic syncs and live syncs are both included in the monthly price of the connection, see pricing. A live sync never adds a charge.

The bank’s daily limit

A bank limits how often data can be fetched without the person present. European rules let a bank limit unattended access to four reads a day per account. That is a ceiling, not a promise: a bank may allow fewer or agree to more.
  • Automatic and live syncs share one budget, and the automatic schedule never uses the last two reads of a day.
  • sync.live_syncs_left_today on the connection says how many live syncs remain today, and sync.budgets[] shows each bucket: scope (connection or account), resource, limit, remaining and resets_at.
  • While the person is present in Bank Link, for a renewal or a reconnect, reads are not limited.
  • When the day’s budget is used up, the call answers 429 refresh_limit_reached with a Retry-After header (the seconds until the budget resets) and a sync object with live_syncs_left_today and budgets. Wait that long, and rely on the automatic sync meanwhile.
  • Your API limits are separate: 600 reads and 300 writes per minute per application, with X-RateLimit-* headers.

Know how fresh the data is

  • sync.last_synced_at on the connection and on each account is when Didit last fetched from the bank, not when you last read it.
  • Both transaction reads return X-Bank-Last-Synced-At.

Errors you should handle

Last modified on November 22, 2026