Transactions Sync
Provides a paginated feed of transactions, grouped into created
, updated
, and removed
lists.
Each call will also return a next_cursor
value. In subsequent calls, include that value to receive only changes that have occurred since the previous call.
Large numbers of transactions will be paginated, and the has_more
field will be true. You should continue calling this endpoint with each new next_cursor
value until has_more
is false.
Note that this endpoint does not trigger a fetch of transactions from the institution; it merely returns
transactions that have already been fetched, either because prefetch
was requested when the link was created, or
because of scheduled or on-demand updates. MoneyKit checks for updated account data, including transactions,
periodically throughout the day, but the update frequency can vary, depending on the downstream data provider, the
institution, and whether one or both provide webhook-based updates.
To force a check for updated transactions, you can use the /products endpoint.
transactions.updates_available
webhook will alert you when new data is available.Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Headers
Path Parameters
The unique ID for this link.
Query Parameters
A cursor value representing the last update requested. If included, the response will only return changes after this update. If omitted, a complete history of updates will be returned. This value must be stored by the client as we do not keep track of customer cursors.
The number of items to return.
1 <= x <= 500
Response
Successful Response
The response is of type object
.