Incremental transaction changefeed. Use GET /transactions for the initial historical backfill. Then call this endpoint without a cursor to initialise the stream at the current end of stream. Subsequent calls should send the previously returned nextCursor. Responses contain added, modified, and removed events ordered by (updatedAt, id) ascending. If hasMore is true, call again immediately with nextCursor. A cursor is only valid when reused with the same filter set.
OAuth 2.0 Client Credentials issuing JWT Bearer access tokens.
Opaque cursor returned by a previous /transactions/sync response. Omit on the first call to initialise the stream.
Maximum number of change events to return.
1 <= x <= 500Comma-separated sparse fieldset applied to embedded transaction objects. The server always includes required identifiers.
Limit the stream to a single account. If used, keep it consistent for the lifetime of the cursor stream.
Limit the stream to a single connection. If used, keep it consistent for the lifetime of the cursor stream.
Successful Response
Change events ordered by (updatedAt, id) ascending. Clients should process events in order and persist nextCursor.
Opaque cursor to use on the next sync call.
Whether more change events are immediately available.