Get incremental transaction updates on an Item
The /transactions/sync endpoint retrieves transactions associated with an Item and can fetch updates using a cursor to track which updates have already been seen.
For important instructions on integrating with /transactions/sync, see the Transactions integration overview. If you are migrating from an existing integration using /transactions/get, see the Transactions Sync migration guide.
This endpoint supports credit, depository, and some loan-type accounts (only those with account subtype student or mortgage). For investments accounts, use /investments/transactions/get instead.
When retrieving paginated updates, track both the next_cursor from the latest response and the original cursor from the first call in which has_more was true; if a call to /transactions/sync fails when retrieving a paginated update (e.g. due to the TRANSACTIONS_SYNC_MUTATION_DURING_PAGINATION error), the entire pagination request loop must be restarted beginning with the cursor for the first page of the update, rather than retrying only the single request that failed.
If transactions data is not yet available for the Item, which can happen if the Item was not initialized with transactions during the /link/token/create call or if /transactions/sync was called within a few seconds of Item creation, /transactions/sync will return empty transactions arrays.
Plaid typically checks for new transactions data between one and four times per day, depending on the institution. To find out when transactions were last updated for an Item, use the Item Debugger or call /item/get; the item.status.transactions.last_successful_update field will show the timestamp of the most recent successful update. To force Plaid to check for new transactions, use the /transactions/refresh endpoint.
To be alerted when new transactions are available, listen for the SYNC_UPDATES_AVAILABLE webhook.
Request body
Response
OK