Incremental transaction changefeed for maintaining a current mirror, not an immutable history log. For a no-gap bootstrap, call this endpoint without a cursor and save nextCursor, then backfill with GET /v1/transactions, then poll from the saved cursor. Responses are ordered by the server’s sync cursor ascending and act as a convergence-safe stream: reusing the same cursor later returns the then-current ordered suffix after that cursor, not a byte-for-byte replay of an earlier page. Persist nextCursor only after the full page has been durably applied. Clients should upsert both added and modified, delete on removed, and call again immediately with nextCursor while hasMore is true. Duplicates between the backfill and later sync calls are expected. Cursors are valid only for the same stream-defining filters, expire after 90 days, and return invalid_cursor for malformed or filter-mismatched cursors or cursor_expired when the client must rebootstrap. If rate limited, honor Retry-After when present and retry with the same cursor. Under the current product model, sync events are transaction-write driven: removed is emitted for transaction deletions, and account visibility changes without transaction mutations are intentionally out of scope.
Opaque API key passed as Authorization: Bearer <key>. Keys are organization-bound, environment-bound (live or test), scope-carrying, and expiring. Create and manage keys via the console.
Opaque cursor returned by a previous /v1/transactions/sync response. Omit on the first call to initialise the stream head for no-gap bootstrap. Cursors are valid only for the same stream-defining filters (accountId, connectionId), expire after 90 days, and act as lower bounds in the ordered sync stream. invalid_cursor means malformed or filter-mismatched. cursor_expired means the client must rebootstrap.
Maximum number of change events to return.
1 <= x <= 500Comma-separated sparse fieldset applied to embedded transaction objects. The server always includes required identifiers. This does not change stream membership and is not part of cursor compatibility.
Limit the stream to a single account. This is a stream-defining filter and must stay consistent for the lifetime of the cursor stream.
Limit the stream to a single connection. This is a stream-defining filter and must stay consistent for the lifetime of the cursor stream.
Successful Response
Mirror-maintenance change events ordered by the server's sync cursor ascending. They are designed to keep a current mirror correct, not to provide an immutable replay log. Reusing the same cursor later returns the then-current ordered suffix after that cursor rather than a byte-for-byte replay of an earlier page.
Opaque cursor to use on the next sync call. Persist it only after the full page has been durably applied.