v51

latestOpenAPI 3.0.0raw.githubusercontent.com2026-07-313352,3122.9 MB
plaid

Gets transaction data in `cashflow_report`

The /cashflow_report/get endpoint retrieves transactions data associated with an Item. Transactions data is standardized across financial institutions. Transactions are returned in reverse-chronological order, and the sequence of transaction ordering is stable and will not shift. Transactions are not immutable and can also be removed altogether by the institution; a removed transaction will no longer appear in /cashflow_report/get. For more details, see Pending and posted transactions. Due to the potentially large number of transactions associated with an Item, results are paginated. Manipulate the count and cursor parameters in conjunction with the has_more response body field to fetch all available transactions. Note that data isn't likely to be immediately available to /cashflow_report/get. Plaid will begin to prepare transactions data upon Item link, if Link was initialized with cashflow_report, or if it wasn't, upon the first call to /cashflow_report/refresh. To be alerted when transaction data is ready to be fetched, listen for the CASHFLOW_REPORT_READY webhook.

post/cashflow_report/get

Request body

client_idstring

Your Plaid API client_id. The client_id is required and may be provided either in the PLAID-CLIENT-ID header or as part of a request body.

access_tokenstring required

The access token associated with the Item for which data is being requested.

secretstring

Your Plaid API secret. The secret is required and may be provided either in the PLAID-SECRET header or as part of a request body.

days_requestedinteger required

Number of days to retrieve transactions data for (1 to 730)

countinteger

Number of transactions to fetch per call

cursorstring

The cursor value represents the last update requested. Pass in the empty string "" in the first call.

Response

OK

total_transactionsinteger required

The total number of transactions available within the date range specified. If total_transactions is larger than the size of the transactions array, more transactions are available and can be fetched using the cursor parameter.

next_cursorstring required

Cursor used for fetching any future updates after the latest update provided in this response.

has_moreboolean required

Represents if more than requested count of transactions exists to be fetched

last_successful_update_timestring date-time required

The last successful update time in ISO 8601 format ( YYYY-MM-DDTHH:mm:ssZ )

request_idstring required

A unique identifier for the request, which can be used for troubleshooting. This identifier, like all Plaid identifiers, is case sensitive.