Skip to main content
GET
curl
Didit’s Sync Transactions endpoint returns what changed in a connection’s transactions since a cursor: added, modified and removed. An empty cursor returns everything with reset: true. Store next_cursor only after a response with has_more: false. See Continuous bank feed for accounting.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is wrong, revoked or expired; 403 means no key was sent, the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Path Parameters

id
string<uuid>
required

The connection id.

Query Parameters

cursor
string

The next_cursor you stored. Empty or omitted starts from the beginning.

limit
integer
default:100

Page size, 1 to 500. Default 100.

Required range: 1 <= x <= 500
page_token
string

Continues the same read while has_more is true.

Response

A page of changes.

Changes of a connection's transactions since a cursor. An empty cursor returns every current transaction as added. All pages of one read reflect the same snapshot; changes that arrive meanwhile come in the next read.

added
object[]
required

Transactions to add. On a first read (no cursor, or after reset) this is every transaction the connection had when the read started, each exactly once and in its current state, even if a sync runs while you page. In later reads it holds the transactions that are new since your cursor, and the booked transaction that replaces a pending one.

modified
object[]
required

Transactions that changed since your cursor, in their current state. Apply each as an upsert by id: a transaction you already received while paging the first read comes again here if it changed meanwhile, and a bank correction arrives here too.

removed
object[]
required

Transactions that no longer exist, with a reason. Ignore an id you do not have: a transaction that was removed while you paged a first read was still delivered once as added and arrives here in the next read.

has_more
boolean
required

true while there are more pages. Store next_cursor only after a response with has_more: false; if paging fails midway, restart from the cursor you had stored.

next_page_token
string | null
required

Continues this read while has_more is true.

next_cursor
string | null
required

The durable checkpoint of the feed, returned only on the last page. Opaque and bound to the application, environment and connection. Replayable for 90 days. On a first read it marks the moment the read started, so what changed meanwhile arrives in the next read.

reset
boolean
required

true on every bootstrap, which is every read from an empty cursor: replace your copy with the result instead of adding to it.

Last modified on November 22, 2026