Transactions
API reference for Transactions endpoints and webhooks
Retrieve and refresh up to 24 months of historical transaction data, including geolocation, merchant, and category information. For how-to guidance, see the Transactions documentation.
| Endpoints | |
|---|---|
/transactions/sync | Get transaction data or incremental transaction updates |
/transactions/get | Fetch transaction data |
/transactions/recurring/get | Fetch recurring transaction data |
/transactions/refresh | Refresh transaction data |
/categories/get | Fetch all transaction categories |
| See also | |
|---|---|
/processor/transactions/sync | Get transaction data or incremental transaction updates |
/processor/transactions/get | Fetch transaction data |
/processor/transactions/recurring/get | Fetch recurring transaction data |
/processor/transactions/refresh | Refresh transaction data |
/sandbox/transactions/create | Create custom transactions for testing |
| Webhooks | |
|---|---|
SYNC_UPDATES_AVAILABLE | New updates available |
RECURRING_TRANSACTIONS_UPDATE | New recurring updates available |
INITIAL_UPDATE | Initial transactions ready |
HISTORICAL_UPDATE | Historical transactions ready |
DEFAULT_UPDATE | New transactions available |
TRANSACTIONS_REMOVED | Deleted transactions detected |
Endpoints
/transactions/sync
If you are migrating to /transactions/sync from an existing /transactions/get integration, also refer to the Transactions Sync migration guide.
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). 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 fields
client_idclient_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_tokensecretsecret. The secret is required and may be provided either in the PLAID-SECRET header or as part of a request body.cursor"now", which can be used to fast-forward the cursor as part of migrating an existing Item from /transactions/get to /transactions/sync. For more information, see the Transactions sync migration guide. Note that using the "now" value is not supported for any use case other than migrating existing Items from /transactions/get.The upper-bound length of this cursor is 256 characters of base64.
count100 1 500 false optionsoptions must not be null.include_original _descriptionfalse days_requestedtransactions in the products, required_if_supported_products, or optional_products array when calling /link/token/create or by making a previous call to /transactions/sync or /transactions/get). In those cases, the field controls the maximum number of days of transaction history that Plaid will request from the financial institution. The more transaction history is requested, the longer the historical update poll will take. If no value is specified, 90 days of history will be requested by default.If you are initializing your Items with transactions during the
/link/token/create call (e.g. by including transactions in the /link/token/create products array), you must use the transactions.days_requested field in the /link/token/create request instead of in the /transactions/sync request.If the Item has already been initialized with the Transactions product, this field will have no effect. The maximum amount of transaction history to request on an Item cannot be updated if Transactions has already been added to the Item. To request older transaction history on an Item where Transactions has already been added, you must delete the Item via
/item/remove and send the user through Link to create a new Item.Customers using Recurring Transactions should request at least 180 days of history for optimal results.
1 730 90 account_idaccount_id returns updates for all accounts under the Item. Note that specifying an account_id effectively creates a separate incremental update stream—and therefore a separate cursor—for that account. If multiple accounts are queried this way, you will maintain multiple cursors, one per account_id.If you decide to begin filtering by
account_id after using no account_id, start fresh with a null cursor and maintain separate (account_id, cursor) pairs going forward. Do not reuse any previously saved cursors, as this can cause pagination errors or incomplete data.Note: An error will be returned if a provided
account_id is not associated with the Item.// Provide a cursor from your database if you've previously
// received one for the Item. Leave null if this is your
// first sync call for this Item. The first request will
// return a cursor.
let cursor = database.getLatestCursorOrNull(itemId);
// New transaction updates since "cursor"
let added: Array<Transaction> = [];
let modified: Array<Transaction> = [];
// Removed transaction ids
let removed: Array<RemovedTransaction> = [];
let hasMore = true;
// Iterate through each page of new transaction updates for item
while (hasMore) {
const request: TransactionsSyncRequest = {
access_token: accessToken,
cursor: cursor,
};
const response = await client.transactionsSync(request);
const data = response.data;
// Add this page of results
added = added.concat(data.added);
modified = modified.concat(data.modified);
removed = removed.concat(data.removed);
hasMore = data.has_more;
// Update cursor to the next cursor
cursor = data.next_cursor;
}
// Persist cursor and updated data
database.applyUpdates(itemId, added, modified, removed, cursor);
Response fields
transactions_update _statusTRANSACTIONS_UPDATE_STATUS_UNKNOWN: Unable to fetch transactions update status for Item.
NOT_READY: The Item is pending transaction pull.
INITIAL_UPDATE_COMPLETE: Initial pull for the Item is complete, historical pull is pending.
HISTORICAL_UPDATE_COMPLETE: Both initial and historical pull for Item are complete.TRANSACTIONS_UPDATE_STATUS_UNKNOWN, NOT_READY, INITIAL_UPDATE_COMPLETE, HISTORICAL_UPDATE_COMPLETEaccountsinvestment-type accounts will be omitted.account_idaccount_id will be assigned to the account.The
account_id can also change if the access_token is deleted and the same credentials that were used to generate that access_token are used to generate a new access_token on a later date. In that case, the new account_id will be different from the old account_id.If an account with a specific
account_id disappears instead of changing, the account is likely closed. Closed accounts are not returned by the Plaid API.When using a CRA endpoint (an endpoint associated with Plaid Check Consumer Report, i.e. any endpoint beginning with
/cra/), the account_id returned will not match the account_id returned by a non-CRA endpoint.Like all Plaid identifiers, the
account_id is case sensitive.balances/accounts/balance/get or /signal/evaluate (using a Balance-only ruleset).availableFor
credit-type accounts, the available balance typically equals the limit less the current balance, less any pending outflows plus any pending inflows.For
depository-type accounts, the available balance typically equals the current balance less any pending outflows plus any pending inflows. For depository-type accounts, the available balance does not include the overdraft limit.For
investment-type accounts (or brokerage-type accounts for API versions 2018-05-22 and earlier), the available balance is the total cash available to withdraw as presented by the institution.Note that not all institutions calculate the
available balance. In the event that available balance is unavailable, Plaid will return an available balance value of null.Available balance may be cached and is not guaranteed to be up-to-date in realtime unless the value was returned by
/accounts/balance/get, or by /signal/evaluate with a Balance-only ruleset.If
current is null this field is guaranteed not to be null.double currentFor
credit-type accounts, a positive balance indicates the amount owed; a negative amount indicates the lender owing the account holder.For
loan-type accounts, the current balance is the principal remaining on the loan, except in the case of student loan accounts at Sallie Mae (ins_116944). For Sallie Mae student loans, the account's balance includes both principal and any outstanding interest. Similar to credit-type accounts, a positive balance is typically expected, while a negative amount indicates the lender owing the account holder.For
investment-type accounts (or brokerage-type accounts for API versions 2018-05-22 and earlier), the current balance is the total value of assets as presented by the institution.Note that balance information may be cached unless the value was returned by
/accounts/balance/get or by /signal/evaluate with a Balance-only ruleset; if the Item is enabled for Transactions, the balance will be at least as recent as the most recent Transaction update. If you require realtime balance information, use the available balance as provided by /accounts/balance/get or /signal/evaluate called with a Balance-only ruleset_key.When returned by
/accounts/balance/get, this field may be null. When this happens, available is guaranteed not to be null.double limitcredit-type accounts, this represents the credit limit.For
depository-type accounts, this represents the pre-arranged overdraft limit, which is common for current (checking) accounts in Europe.In North America, this field is typically only available for
credit-type accounts.double iso_currency_codeunofficial_currency_code is non-null.unofficial_currency _codeiso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.See the currency code schema for a full listing of supported
unofficial_currency_codes.last_updated_datetimeYYYY-MM-DDTHH:mm:ssZ) indicating the last time the balance was updated.This field is returned only when the institution is
ins_128026 (Capital One).date-time masknameofficial_nametypeinvestment: Investment account. In API versions 2018-05-22 and earlier, this type is called brokerage instead.credit: Credit carddepository: Depository accountloan: Loan accountother: Non-specified account typeSee the Account type schema for a full listing of account types and corresponding subtypes.
investment, credit, depository, loan, brokerage, othersubtype401a, 401k, 403B, 457b, 529, auto, brokerage, business, cash isa, cash management, cd, checking, commercial, construction, consumer, credit card, crypto exchange, ebt, education savings account, fixed annuity, gic, health reimbursement arrangement, home equity, hsa, isa, ira, keogh, lif, life insurance, line of credit, lira, loan, lrif, lrsp, money market, mortgage, mutual fund, non-custodial wallet, non-taxable brokerage account, other, other insurance, other annuity, overdraft, paypal, payroll, pension, prepaid, prif, profit sharing plan, rdsp, resp, retirement, rlif, roth, roth 401k, rrif, rrsp, sarsep, savings, sep ira, simple ira, sipp, stock plan, student, thrift savings plan, tfsa, trust, ugma, utma, variable annuityverification_statuspending_automatic_verification: The Item is pending automatic verification.pending_manual_verification: The Item is pending manual micro-deposit verification. Items remain in this state until the user successfully verifies the code.automatically_verified: The Item has successfully been automatically verified.manually_verified: The Item has successfully been manually verified.verification_expired: Plaid was unable to automatically verify the deposit within 7 calendar days and will no longer attempt to validate the Item. Users may retry by submitting their information again through Link.verification_failed: The Item failed manual micro-deposit verification because the user exhausted all 3 verification attempts. Users may retry by submitting their information again through Link.unsent: The Item is pending micro-deposit verification, but Plaid has not yet sent the micro-deposit.database_insights_pending: The Database Auth result is pending and will be available upon Auth request.database_insights_fail: The Item's numbers have been verified using Plaid's data sources and have signal for being invalid and/or have no signal for being valid. Typically this indicates that the routing number is invalid, the account number does not match the account number format associated with the routing number, or the account has been reported as closed or frozen. Only returned for Auth Items created via Database Auth.database_insights_pass: The Item's numbers have been verified using Plaid's data sources: the routing and account number match a routing and account number of an account recognized on the Plaid network, and the account is not known by Plaid to be frozen or closed. Only returned for Auth Items created via Database Auth.database_insights_pass_with_caution: The Item's numbers have been verified using Plaid's data sources and have some signal for being valid: the routing and account number were not recognized on the Plaid network, but the routing number is valid and the account number is a potential valid account number for that routing number. Only returned for Auth Items created via Database Auth.database_matched: (deprecated) The Item has successfully been verified using Plaid's data sources. Only returned for Auth Items created via Database Match.null or empty string: Neither micro-deposit-based verification nor database verification are being used for the Item.automatically_verified, pending_automatic_verification, pending_manual_verification, unsent, manually_verified, verification_expired, verification_failed, database_matched, database_insights_pass, database_insights_pass_with_caution, database_insights_failverification_nameuser.legal_name request field in /link/token/create for the Link session that created the Item.verification_insightsname_match_scoreverification_name field) and matched Plaid network accounts. If defined, will be a value between 0 and 100. Will be undefined if name matching was not enabled for the database verification session or if there were no eligible Plaid network matches to compare the given name with.network_statushas_numbers_matchis_numbers_match _verifiedprevious_returnshas_previous _administrative_returnaccount_number_formatvalid: indicates that the account number has a correct format for the institution.invalid: indicates that the account number has an incorrect format for the institution.unknown: indicates that there was not enough information to determine whether the format is correct for the institution.valid, invalid, unknownpersistent_account_idins_56, ins_13) as well as the OAuth Sandbox institution (ins_127287); in Production, it will only be populated for accounts at applicable institutions.holder_categorybusiness, personal, unrecognizedaddedcursor ordered by ascending last modified time.account_idamountiso_currency_code or unofficial_currency_code. For all products except Income: Positive values when money moves out of the account; negative values when money moves in. For example, debit card purchases are positive; credit card payments, direct deposits, and refunds are negative. For Income endpoints, values are positive when representing income.double iso_currency_codenull if unofficial_currency_code is non-null.unofficial_currency _codenull if iso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.See the currency code schema for a full listing of supported
iso_currency_codes.check_numberdateYYYY-MM-DD ). To receive information about the date that a posted transaction was initiated, see the authorized_date field.date locationaddresscityregionstate.postal_codezip.countrylatdouble londouble store_numbernameNote: While Plaid does not currently plan to remove this field, it is a legacy field that is not actively maintained. Use
merchant_name instead for the merchant name.If the
transactions object was returned by a Transactions endpoint such as /transactions/sync or /transactions/get, this field will always appear. If the transactions object was returned by an Assets endpoint such as /asset_report/get/ or /asset_report/pdf/get, this field will only appear in an Asset Report with Insights.merchant_namename field. This is typically a more human-readable version of the merchant counterparty in the transaction. For some bank transactions (such as checks or account transfers) where there is no meaningful merchant name, this value will be null.original_description/transactions/sync or /transactions/get, this field will only be included if the client has set options.include_original_description to true.payment_metanull.If the
transactions object was returned by a Transactions endpoint such as /transactions/sync or /transactions/get, the payment_meta key will always appear, but no data elements are guaranteed. If the transactions object was returned by an Assets endpoint such as /asset_report/get/ or /asset_report/pdf/get, this field will only appear in an Asset Report with Insights.reference_numberppd_idpayeeby_order_ofnull if the transaction is not a wire transfer.payerpayment_methodpayment_processorreasonpendingtrue, identifies the transaction as pending or unsettled. Pending transaction details (name, type, amount, category ID) may change before they are settled. Not all institutions provide pending transactions.pending_transaction_idaccount_ownertransaction_idtransaction_id is case sensitive.transaction_typepayment_channel field, transaction_type will be deprecated in the future.digital: transactions that took place online.place: transactions that were made at a physical location.special: transactions that relate to banks, e.g. fees or deposits.unresolved: transactions that do not fit into the other three types.digital, place, special, unresolvedlogo_urlwebsiteauthorized_datedate field will indicate the posted date, but authorized_date will indicate the day the transaction was authorized by the financial institution. If presenting transactions to the user in a UI, the authorized_date, when available, is generally preferable to use over the date field for posted transactions, as it will generally represent the date the user actually made the transaction. Dates are returned in an ISO 8601 format ( YYYY-MM-DD ).date authorized_datetimeYYYY-MM-DDTHH:mm:ssZ ). For posted transactions, the datetime field will indicate the posted date, but authorized_datetime will indicate the day the transaction was authorized by the financial institution. If presenting transactions to the user in a UI, the authorized_datetime, when available, is generally preferable to use over the datetime field for posted transactions, as it will generally represent the date the user actually made the transaction.This field is returned for select financial institutions and comes as provided by the institution. It may contain default time values (such as 00:00:00). This field is only populated in API version 2019-05-29 and later.
date-time datetimeYYYY-MM-DDTHH:mm:ssZ ). For the date that the transaction was initiated, rather than posted, see the authorized_datetime field.This field is returned for select financial institutions and comes as provided by the institution. It may contain default time values (such as 00:00:00). This field is only populated in API version 2019-05-29 and later.
date-time payment_channelonline: transactions that took place online.in store: transactions that were made at a physical location.other: transactions that relate to banks, e.g. fees or deposits.This field replaces the
transaction_type field.online, in store, otherpersonal_finance _categorySee the
taxonomy CSV file for a full list of personal finance categories. If you are migrating to personal finance categories from the legacy categories, also refer to the migration guide.primarydetailedconfidence_levelVERY_HIGH: We are more than 98% confident that this category reflects the intent of the transaction.
HIGH: We are more than 90% confident that this category reflects the intent of the transaction.
MEDIUM: We are moderately confident that this category reflects the intent of the transaction.
LOW: This category may reflect the intent, but there may be other categories that are more accurate.
UNKNOWN: We don’t know the confidence level for this category.transaction_codeThis field is only populated for European institutions. For institutions in the US and Canada, this field is set to
null.adjustment: Bank adjustmentatm: Cash deposit or withdrawal via an automated teller machinebank charge: Charge or fee levied by the institutionbill payment: Payment of a billcash: Cash deposit or withdrawalcashback: Cash withdrawal while making a debit card purchasecheque: Document ordering the payment of money to another person or organizationdirect debit: Automatic withdrawal of funds initiated by a third party at a regular intervalinterest: Interest earned or incurredpurchase: Purchase made with a debit or credit cardstanding order: Payment instructed by the account holder to a third party at a regular intervaltransfer: Transfer of money between accountsadjustment, atm, bank charge, bill payment, cash, cashback, cheque, direct debit, interest, purchase, standing order, transfer, nullpersonal_finance _category_icon_urlcounterpartiesnameentity_idtypemerchant: a provider of goods or services for purchase
financial_institution: a financial entity (bank, credit union, BNPL, fintech)
payment_app: a transfer or P2P app (e.g. Zelle)
marketplace: a marketplace (e.g DoorDash, Google Play Store)
payment_terminal: a point-of-sale payment terminal (e.g Square, Toast)
income_source: the payer in an income transaction (e.g., an employer, client, or government agency)merchant, financial_institution, payment_app, marketplace, payment_terminal, income_sourcewebsitelogo_urlconfidence_levelVERY_HIGH: We recognize this counterparty and we are more than 98% confident that it is involved in this transaction.
HIGH: We recognize this counterparty and we are more than 90% confident that it is involved in this transaction.
MEDIUM: We are moderately confident that this counterparty was involved in this transaction, but some details may differ from our records.
LOW: We didn’t find a matching counterparty in our records, so we are returning a cleansed name parsed out of the request description.
UNKNOWN: We don’t know the confidence level for this counterparty.account_numbersinternationalmerchant_entity_idmodifiedcursor ordered by ascending last modified time.account_idamountiso_currency_code or unofficial_currency_code. For all products except Income: Positive values when money moves out of the account; negative values when money moves in. For example, debit card purchases are positive; credit card payments, direct deposits, and refunds are negative. For Income endpoints, values are positive when representing income.double iso_currency_codenull if unofficial_currency_code is non-null.unofficial_currency _codenull if iso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.See the currency code schema for a full listing of supported
iso_currency_codes.check_numberdateYYYY-MM-DD ). To receive information about the date that a posted transaction was initiated, see the authorized_date field.date locationaddresscityregionstate.postal_codezip.countrylatdouble londouble store_numbernameNote: While Plaid does not currently plan to remove this field, it is a legacy field that is not actively maintained. Use
merchant_name instead for the merchant name.If the
transactions object was returned by a Transactions endpoint such as /transactions/sync or /transactions/get, this field will always appear. If the transactions object was returned by an Assets endpoint such as /asset_report/get/ or /asset_report/pdf/get, this field will only appear in an Asset Report with Insights.merchant_namename field. This is typically a more human-readable version of the merchant counterparty in the transaction. For some bank transactions (such as checks or account transfers) where there is no meaningful merchant name, this value will be null.original_description/transactions/sync or /transactions/get, this field will only be included if the client has set options.include_original_description to true.payment_metanull.If the
transactions object was returned by a Transactions endpoint such as /transactions/sync or /transactions/get, the payment_meta key will always appear, but no data elements are guaranteed. If the transactions object was returned by an Assets endpoint such as /asset_report/get/ or /asset_report/pdf/get, this field will only appear in an Asset Report with Insights.reference_numberppd_idpayeeby_order_ofnull if the transaction is not a wire transfer.payerpayment_methodpayment_processorreasonpendingtrue, identifies the transaction as pending or unsettled. Pending transaction details (name, type, amount, category ID) may change before they are settled. Not all institutions provide pending transactions.pending_transaction_idaccount_ownertransaction_idtransaction_id is case sensitive.transaction_typepayment_channel field, transaction_type will be deprecated in the future.digital: transactions that took place online.place: transactions that were made at a physical location.special: transactions that relate to banks, e.g. fees or deposits.unresolved: transactions that do not fit into the other three types.digital, place, special, unresolvedlogo_urlwebsiteauthorized_datedate field will indicate the posted date, but authorized_date will indicate the day the transaction was authorized by the financial institution. If presenting transactions to the user in a UI, the authorized_date, when available, is generally preferable to use over the date field for posted transactions, as it will generally represent the date the user actually made the transaction. Dates are returned in an ISO 8601 format ( YYYY-MM-DD ).date authorized_datetimeYYYY-MM-DDTHH:mm:ssZ ). For posted transactions, the datetime field will indicate the posted date, but authorized_datetime will indicate the day the transaction was authorized by the financial institution. If presenting transactions to the user in a UI, the authorized_datetime, when available, is generally preferable to use over the datetime field for posted transactions, as it will generally represent the date the user actually made the transaction.This field is returned for select financial institutions and comes as provided by the institution. It may contain default time values (such as 00:00:00). This field is only populated in API version 2019-05-29 and later.
date-time datetimeYYYY-MM-DDTHH:mm:ssZ ). For the date that the transaction was initiated, rather than posted, see the authorized_datetime field.This field is returned for select financial institutions and comes as provided by the institution. It may contain default time values (such as 00:00:00). This field is only populated in API version 2019-05-29 and later.
date-time payment_channelonline: transactions that took place online.in store: transactions that were made at a physical location.other: transactions that relate to banks, e.g. fees or deposits.This field replaces the
transaction_type field.online, in store, otherpersonal_finance _categorySee the
taxonomy CSV file for a full list of personal finance categories. If you are migrating to personal finance categories from the legacy categories, also refer to the migration guide.primarydetailedconfidence_levelVERY_HIGH: We are more than 98% confident that this category reflects the intent of the transaction.
HIGH: We are more than 90% confident that this category reflects the intent of the transaction.
MEDIUM: We are moderately confident that this category reflects the intent of the transaction.
LOW: This category may reflect the intent, but there may be other categories that are more accurate.
UNKNOWN: We don’t know the confidence level for this category.transaction_codeThis field is only populated for European institutions. For institutions in the US and Canada, this field is set to
null.adjustment: Bank adjustmentatm: Cash deposit or withdrawal via an automated teller machinebank charge: Charge or fee levied by the institutionbill payment: Payment of a billcash: Cash deposit or withdrawalcashback: Cash withdrawal while making a debit card purchasecheque: Document ordering the payment of money to another person or organizationdirect debit: Automatic withdrawal of funds initiated by a third party at a regular intervalinterest: Interest earned or incurredpurchase: Purchase made with a debit or credit cardstanding order: Payment instructed by the account holder to a third party at a regular intervaltransfer: Transfer of money between accountsadjustment, atm, bank charge, bill payment, cash, cashback, cheque, direct debit, interest, purchase, standing order, transfer, nullpersonal_finance _category_icon_urlcounterpartiesnameentity_idtypemerchant: a provider of goods or services for purchase
financial_institution: a financial entity (bank, credit union, BNPL, fintech)
payment_app: a transfer or P2P app (e.g. Zelle)
marketplace: a marketplace (e.g DoorDash, Google Play Store)
payment_terminal: a point-of-sale payment terminal (e.g Square, Toast)
income_source: the payer in an income transaction (e.g., an employer, client, or government agency)merchant, financial_institution, payment_app, marketplace, payment_terminal, income_sourcewebsitelogo_urlconfidence_levelVERY_HIGH: We recognize this counterparty and we are more than 98% confident that it is involved in this transaction.
HIGH: We recognize this counterparty and we are more than 90% confident that it is involved in this transaction.
MEDIUM: We are moderately confident that this counterparty was involved in this transaction, but some details may differ from our records.
LOW: We didn’t find a matching counterparty in our records, so we are returning a cleansed name parsed out of the request description.
UNKNOWN: We don’t know the confidence level for this counterparty.account_numbersinternationalmerchant_entity_idremovedcursor ordered by ascending last modified time.transaction_idaccount_idnext_cursorhas_more being false) will be valid for at least 1 year. This cursor should be persisted for later calls. If transactions are not yet available, this will be an empty string.If
account_id is included in the request, the returned cursor will reflect updates for that specific account.has_morecursor set to next_cursor. If has_more is true, it’s important to pull all available pages, to make it less likely for underlying data changes to conflict with pagination.request_id{
"accounts": [
{
"account_id": "BxBXxLj1m4HMXBm9WZZmCWVbPjX16EHwv99vp",
"balances": {
"available": 110.94,
"current": 110.94,
"iso_currency_code": "USD",
"limit": null,
"unofficial_currency_code": null
},
"mask": "0000",
"name": "Plaid Checking",
"official_name": "Plaid Gold Standard 0% Interest Checking",
"subtype": "checking",
"type": "depository"
}
],
"added": [
{
"account_id": "BxBXxLj1m4HMXBm9WZZmCWVbPjX16EHwv99vp",
"account_owner": null,
"amount": 72.1,
"iso_currency_code": "USD",
"unofficial_currency_code": null,
"check_number": null,
"counterparties": [
{
"name": "Walmart",
"type": "merchant",
"logo_url": "https://plaid-merchant-logos.plaid.com/walmart_1100.png",
"website": "walmart.com",
"entity_id": "O5W5j4dN9OR3E6ypQmjdkWZZRoXEzVMz2ByWM",
"confidence_level": "VERY_HIGH"
}
],
"date": "2023-09-24",
"datetime": "2023-09-24T11:01:01Z",
"authorized_date": "2023-09-22",
"authorized_datetime": "2023-09-22T10:34:50Z",
"location": {
"address": "13425 Community Rd",
"city": "Poway",
"region": "CA",
"postal_code": "92064",
"country": "US",
"lat": 32.959068,
"lon": -117.037666,
"store_number": "1700"
},
"name": "PURCHASE WM SUPERCENTER #1700",
"merchant_name": "Walmart",
"merchant_entity_id": "O5W5j4dN9OR3E6ypQmjdkWZZRoXEzVMz2ByWM",
"logo_url": "https://plaid-merchant-logos.plaid.com/walmart_1100.png",
"website": "walmart.com",
"payment_meta": {
"by_order_of": null,
"payee": null,
"payer": null,
"payment_method": null,
"payment_processor": null,
"ppd_id": null,
"reason": null,
"reference_number": null
},
"payment_channel": "in store",
"pending": false,
"pending_transaction_id": "no86Eox18VHMvaOVL7gPUM9ap3aR1LsAVZ5nc",
"personal_finance_category": {
"primary": "GENERAL_MERCHANDISE",
"detailed": "GENERAL_MERCHANDISE_SUPERSTORES",
"confidence_level": "VERY_HIGH"
},
"personal_finance_category_icon_url": "https://plaid-category-icons.plaid.com/PFC_GENERAL_MERCHANDISE.png",
"transaction_id": "lPNjeW1nR6CDn5okmGQ6hEpMo4lLNoSrzqDje",
"transaction_code": null,
"transaction_type": "place"
}
],
"modified": [
{
"account_id": "BxBXxLj1m4HMXBm9WZZmCWVbPjX16EHwv99vp",
"account_owner": null,
"amount": 28.34,
"iso_currency_code": "USD",
"unofficial_currency_code": null,
"check_number": null,
"counterparties": [
{
"name": "DoorDash",
"type": "marketplace",
"logo_url": "https://plaid-counterparty-logos.plaid.com/doordash_1.png",
"website": "doordash.com",
"entity_id": "YNRJg5o2djJLv52nBA1Yn1KpL858egYVo4dpm",
"confidence_level": "HIGH"
},
{
"name": "Burger King",
"type": "merchant",
"logo_url": "https://plaid-merchant-logos.plaid.com/burger_king_155.png",
"website": "burgerking.com",
"entity_id": "mVrw538wamwdm22mK8jqpp7qd5br0eeV9o4a1",
"confidence_level": "VERY_HIGH"
}
],
"date": "2023-09-28",
"datetime": "2023-09-28T15:10:09Z",
"authorized_date": "2023-09-27",
"authorized_datetime": "2023-09-27T08:01:58Z",
"location": {
"address": null,
"city": null,
"region": null,
"postal_code": null,
"country": null,
"lat": null,
"lon": null,
"store_number": null
},
"name": "Dd Doordash Burgerkin",
"merchant_name": "Burger King",
"merchant_entity_id": "mVrw538wamwdm22mK8jqpp7qd5br0eeV9o4a1",
"logo_url": "https://plaid-merchant-logos.plaid.com/burger_king_155.png",
"website": "burgerking.com",
"payment_meta": {
"by_order_of": null,
"payee": null,
"payer": null,
"payment_method": null,
"payment_processor": null,
"ppd_id": null,
"reason": null,
"reference_number": null
},
"payment_channel": "online",
"pending": true,
"pending_transaction_id": null,
"personal_finance_category": {
"primary": "FOOD_AND_DRINK",
"detailed": "FOOD_AND_DRINK_FAST_FOOD",
"confidence_level": "VERY_HIGH"
},
"personal_finance_category_icon_url": "https://plaid-category-icons.plaid.com/PFC_FOOD_AND_DRINK.png",
"transaction_id": "yhnUVvtcGGcCKU0bcz8PDQr5ZUxUXebUvbKC0",
"transaction_code": null,
"transaction_type": "digital"
}
],
"removed": [
{
"account_id": "BxBXxLj1m4HMXBm9WZZmCWVbPjX16EHwv99vp",
"transaction_id": "CmdQTNgems8BT1B7ibkoUXVPyAeehT3Tmzk0l"
}
],
"next_cursor": "tVUUL15lYQN5rBnfDIc1I8xudpGdIlw9nsgeXWvhOfkECvUeR663i3Dt1uf/94S8ASkitgLcIiOSqNwzzp+bh89kirazha5vuZHBb2ZA5NtCDkkV",
"has_more": false,
"request_id": "Wvhy9PZHQLV8njG",
"transactions_update_status": "HISTORICAL_UPDATE_COMPLETE"
}/transactions/get
Get transaction data
Note: All new implementations are encouraged to use /transactions/sync rather than /transactions/get. /transactions/sync provides the same functionality as /transactions/get and improves developer ease-of-use for handling transactions updates.
The /transactions/get endpoint allows developers to receive user-authorized transaction data for credit, depository, and some loan-type accounts (only those with account subtype student; coverage may be limited). For transaction history from investments accounts, use the Investments endpoint instead. Transaction data is standardized across financial institutions, and in many cases transactions are linked to a clean name, entity type, location, and category. Similarly, account data is standardized and returned with a clean name, number, balance, and other meta information where available.
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 /transactions/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 offset parameters in conjunction with the total_transactions response body field to fetch all available transactions.
Data returned by /transactions/get will be the data available for the Item as of the most recent successful check for new transactions. Plaid typically checks for new data multiple times a day, but these checks may occur less frequently, such as once a day, depending on the institution. To find out when the Item was last updated, 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, you can use the /transactions/refresh endpoint.
Note that data may not be immediately available to /transactions/get. Plaid will begin to prepare transactions data upon Item link, if Link was initialized with transactions, or upon the first call to /transactions/get, if it wasn't. To be alerted when transaction data is ready to be fetched, listen for the INITIAL_UPDATE and HISTORICAL_UPDATE webhooks. If no transaction history is ready when /transactions/get is called, it will return a PRODUCT_NOT_READY error.
Request fields
client_idclient_id. The client_id is required and may be provided either in the PLAID-CLIENT-ID header or as part of a request body.optionsoptions must not be null.account_idsaccount_ids to retrieve for the ItemNote: An error will be returned if a provided
account_id is not associated with the Item.count100 1 500 false offset0 0 include_original _descriptionfalse days_requestedtransactions in the products, optional_products, or required_if_consented_products array when calling /link/token/create or by making a previous call to /transactions/sync or /transactions/get). In those cases, the field controls the maximum number of days of transaction history that Plaid will request from the financial institution. The more transaction history is requested, the longer the historical update poll will take. If no value is specified, 90 days of history will be requested by default. If a value under 30 is provided, a minimum of 30 days of history will be requested.If you are initializing your Items with transactions during the
/link/token/create call (e.g. by including transactions in the /link/token/create products array), you must use the transactions.days_requested field in the /link/token/create request instead of in the /transactions/get request.If the Item has already been initialized with the Transactions product, this field will have no effect. The maximum amount of transaction history to request on an Item cannot be updated if Transactions has already been added to the Item. To request older transaction history on an Item where Transactions has already been added, you must delete the Item via
/item/remove and send the user through Link to create a new Item.Customers using Recurring Transactions should request at least 180 days of history for optimal results.
1 730 90 access_tokensecretsecret. The secret is required and may be provided either in the PLAID-SECRET header or as part of a request body.start_datedate end_datedate const request: TransactionsGetRequest = {
access_token: accessToken,
start_date: '2018-01-01',
end_date: '2020-02-01'
};
try {
const response = await client.transactionsGet(request);
let transactions = response.data.transactions;
const total_transactions = response.data.total_transactions;
// Manipulate the offset parameter to paginate
// transactions and retrieve all available data
while (transactions.length < total_transactions) {
const paginatedRequest: TransactionsGetRequest = {
access_token: accessToken,
start_date: '2018-01-01',
end_date: '2020-02-01',
options: {
offset: transactions.length
},
};
const paginatedResponse = await client.transactionsGet(paginatedRequest);
transactions = transactions.concat(
paginatedResponse.data.transactions,
);
}
} catch((err) => {
// handle error
}
Response fields
accountsaccounts associated with the Item for which transactions are being returned. Each transaction can be mapped to its corresponding account via the account_id field.account_idaccount_id will be assigned to the account.The
account_id can also change if the access_token is deleted and the same credentials that were used to generate that access_token are used to generate a new access_token on a later date. In that case, the new account_id will be different from the old account_id.If an account with a specific
account_id disappears instead of changing, the account is likely closed. Closed accounts are not returned by the Plaid API.When using a CRA endpoint (an endpoint associated with Plaid Check Consumer Report, i.e. any endpoint beginning with
/cra/), the account_id returned will not match the account_id returned by a non-CRA endpoint.Like all Plaid identifiers, the
account_id is case sensitive.balances/accounts/balance/get or /signal/evaluate (using a Balance-only ruleset).availableFor
credit-type accounts, the available balance typically equals the limit less the current balance, less any pending outflows plus any pending inflows.For
depository-type accounts, the available balance typically equals the current balance less any pending outflows plus any pending inflows. For depository-type accounts, the available balance does not include the overdraft limit.For
investment-type accounts (or brokerage-type accounts for API versions 2018-05-22 and earlier), the available balance is the total cash available to withdraw as presented by the institution.Note that not all institutions calculate the
available balance. In the event that available balance is unavailable, Plaid will return an available balance value of null.Available balance may be cached and is not guaranteed to be up-to-date in realtime unless the value was returned by
/accounts/balance/get, or by /signal/evaluate with a Balance-only ruleset.If
current is null this field is guaranteed not to be null.double currentFor
credit-type accounts, a positive balance indicates the amount owed; a negative amount indicates the lender owing the account holder.For
loan-type accounts, the current balance is the principal remaining on the loan, except in the case of student loan accounts at Sallie Mae (ins_116944). For Sallie Mae student loans, the account's balance includes both principal and any outstanding interest. Similar to credit-type accounts, a positive balance is typically expected, while a negative amount indicates the lender owing the account holder.For
investment-type accounts (or brokerage-type accounts for API versions 2018-05-22 and earlier), the current balance is the total value of assets as presented by the institution.Note that balance information may be cached unless the value was returned by
/accounts/balance/get or by /signal/evaluate with a Balance-only ruleset; if the Item is enabled for Transactions, the balance will be at least as recent as the most recent Transaction update. If you require realtime balance information, use the available balance as provided by /accounts/balance/get or /signal/evaluate called with a Balance-only ruleset_key.When returned by
/accounts/balance/get, this field may be null. When this happens, available is guaranteed not to be null.double limitcredit-type accounts, this represents the credit limit.For
depository-type accounts, this represents the pre-arranged overdraft limit, which is common for current (checking) accounts in Europe.In North America, this field is typically only available for
credit-type accounts.double iso_currency_codeunofficial_currency_code is non-null.unofficial_currency _codeiso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.See the currency code schema for a full listing of supported
unofficial_currency_codes.last_updated_datetimeYYYY-MM-DDTHH:mm:ssZ) indicating the last time the balance was updated.This field is returned only when the institution is
ins_128026 (Capital One).date-time masknameofficial_nametypeinvestment: Investment account. In API versions 2018-05-22 and earlier, this type is called brokerage instead.credit: Credit carddepository: Depository accountloan: Loan accountother: Non-specified account typeSee the Account type schema for a full listing of account types and corresponding subtypes.
investment, credit, depository, loan, brokerage, othersubtype401a, 401k, 403B, 457b, 529, auto, brokerage, business, cash isa, cash management, cd, checking, commercial, construction, consumer, credit card, crypto exchange, ebt, education savings account, fixed annuity, gic, health reimbursement arrangement, home equity, hsa, isa, ira, keogh, lif, life insurance, line of credit, lira, loan, lrif, lrsp, money market, mortgage, mutual fund, non-custodial wallet, non-taxable brokerage account, other, other insurance, other annuity, overdraft, paypal, payroll, pension, prepaid, prif, profit sharing plan, rdsp, resp, retirement, rlif, roth, roth 401k, rrif, rrsp, sarsep, savings, sep ira, simple ira, sipp, stock plan, student, thrift savings plan, tfsa, trust, ugma, utma, variable annuityverification_statuspending_automatic_verification: The Item is pending automatic verification.pending_manual_verification: The Item is pending manual micro-deposit verification. Items remain in this state until the user successfully verifies the code.automatically_verified: The Item has successfully been automatically verified.manually_verified: The Item has successfully been manually verified.verification_expired: Plaid was unable to automatically verify the deposit within 7 calendar days and will no longer attempt to validate the Item. Users may retry by submitting their information again through Link.verification_failed: The Item failed manual micro-deposit verification because the user exhausted all 3 verification attempts. Users may retry by submitting their information again through Link.unsent: The Item is pending micro-deposit verification, but Plaid has not yet sent the micro-deposit.database_insights_pending: The Database Auth result is pending and will be available upon Auth request.database_insights_fail: The Item's numbers have been verified using Plaid's data sources and have signal for being invalid and/or have no signal for being valid. Typically this indicates that the routing number is invalid, the account number does not match the account number format associated with the routing number, or the account has been reported as closed or frozen. Only returned for Auth Items created via Database Auth.database_insights_pass: The Item's numbers have been verified using Plaid's data sources: the routing and account number match a routing and account number of an account recognized on the Plaid network, and the account is not known by Plaid to be frozen or closed. Only returned for Auth Items created via Database Auth.database_insights_pass_with_caution: The Item's numbers have been verified using Plaid's data sources and have some signal for being valid: the routing and account number were not recognized on the Plaid network, but the routing number is valid and the account number is a potential valid account number for that routing number. Only returned for Auth Items created via Database Auth.database_matched: (deprecated) The Item has successfully been verified using Plaid's data sources. Only returned for Auth Items created via Database Match.null or empty string: Neither micro-deposit-based verification nor database verification are being used for the Item.automatically_verified, pending_automatic_verification, pending_manual_verification, unsent, manually_verified, verification_expired, verification_failed, database_matched, database_insights_pass, database_insights_pass_with_caution, database_insights_failverification_nameuser.legal_name request field in /link/token/create for the Link session that created the Item.verification_insightsname_match_scoreverification_name field) and matched Plaid network accounts. If defined, will be a value between 0 and 100. Will be undefined if name matching was not enabled for the database verification session or if there were no eligible Plaid network matches to compare the given name with.network_statushas_numbers_matchis_numbers_match _verifiedprevious_returnshas_previous _administrative_returnaccount_number_formatvalid: indicates that the account number has a correct format for the institution.invalid: indicates that the account number has an incorrect format for the institution.unknown: indicates that there was not enough information to determine whether the format is correct for the institution.valid, invalid, unknownpersistent_account_idins_56, ins_13) as well as the OAuth Sandbox institution (ins_127287); in Production, it will only be populated for accounts at applicable institutions.holder_categorybusiness, personal, unrecognizedtransactionscount parameter.account_idamountiso_currency_code or unofficial_currency_code. For all products except Income: Positive values when money moves out of the account; negative values when money moves in. For example, debit card purchases are positive; credit card payments, direct deposits, and refunds are negative. For Income endpoints, values are positive when representing income.double iso_currency_codenull if unofficial_currency_code is non-null.unofficial_currency _codenull if iso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.See the currency code schema for a full listing of supported
iso_currency_codes.check_numberdateYYYY-MM-DD ). To receive information about the date that a posted transaction was initiated, see the authorized_date field.date locationaddresscityregionstate.postal_codezip.countrylatdouble londouble store_numbernameNote: While Plaid does not currently plan to remove this field, it is a legacy field that is not actively maintained. Use
merchant_name instead for the merchant name.If the
transactions object was returned by a Transactions endpoint such as /transactions/sync or /transactions/get, this field will always appear. If the transactions object was returned by an Assets endpoint such as /asset_report/get/ or /asset_report/pdf/get, this field will only appear in an Asset Report with Insights.merchant_namename field. This is typically a more human-readable version of the merchant counterparty in the transaction. For some bank transactions (such as checks or account transfers) where there is no meaningful merchant name, this value will be null.original_description/transactions/sync or /transactions/get, this field will only be included if the client has set options.include_original_description to true.payment_metanull.If the
transactions object was returned by a Transactions endpoint such as /transactions/sync or /transactions/get, the payment_meta key will always appear, but no data elements are guaranteed. If the transactions object was returned by an Assets endpoint such as /asset_report/get/ or /asset_report/pdf/get, this field will only appear in an Asset Report with Insights.reference_numberppd_idpayeeby_order_ofnull if the transaction is not a wire transfer.payerpayment_methodpayment_processorreasonpendingtrue, identifies the transaction as pending or unsettled. Pending transaction details (name, type, amount, category ID) may change before they are settled. Not all institutions provide pending transactions.pending_transaction_idaccount_ownertransaction_idtransaction_id is case sensitive.transaction_typepayment_channel field, transaction_type will be deprecated in the future.digital: transactions that took place online.place: transactions that were made at a physical location.special: transactions that relate to banks, e.g. fees or deposits.unresolved: transactions that do not fit into the other three types.digital, place, special, unresolvedlogo_urlwebsiteauthorized_datedate field will indicate the posted date, but authorized_date will indicate the day the transaction was authorized by the financial institution. If presenting transactions to the user in a UI, the authorized_date, when available, is generally preferable to use over the date field for posted transactions, as it will generally represent the date the user actually made the transaction. Dates are returned in an ISO 8601 format ( YYYY-MM-DD ).date authorized_datetimeYYYY-MM-DDTHH:mm:ssZ ). For posted transactions, the datetime field will indicate the posted date, but authorized_datetime will indicate the day the transaction was authorized by the financial institution. If presenting transactions to the user in a UI, the authorized_datetime, when available, is generally preferable to use over the datetime field for posted transactions, as it will generally represent the date the user actually made the transaction.This field is returned for select financial institutions and comes as provided by the institution. It may contain default time values (such as 00:00:00). This field is only populated in API version 2019-05-29 and later.
date-time datetimeYYYY-MM-DDTHH:mm:ssZ ). For the date that the transaction was initiated, rather than posted, see the authorized_datetime field.This field is returned for select financial institutions and comes as provided by the institution. It may contain default time values (such as 00:00:00). This field is only populated in API version 2019-05-29 and later.
date-time payment_channelonline: transactions that took place online.in store: transactions that were made at a physical location.other: transactions that relate to banks, e.g. fees or deposits.This field replaces the
transaction_type field.online, in store, otherpersonal_finance _categorySee the
taxonomy CSV file for a full list of personal finance categories. If you are migrating to personal finance categories from the legacy categories, also refer to the migration guide.primarydetailedconfidence_levelVERY_HIGH: We are more than 98% confident that this category reflects the intent of the transaction.
HIGH: We are more than 90% confident that this category reflects the intent of the transaction.
MEDIUM: We are moderately confident that this category reflects the intent of the transaction.
LOW: This category may reflect the intent, but there may be other categories that are more accurate.
UNKNOWN: We don’t know the confidence level for this category.transaction_codeThis field is only populated for European institutions. For institutions in the US and Canada, this field is set to
null.adjustment: Bank adjustmentatm: Cash deposit or withdrawal via an automated teller machinebank charge: Charge or fee levied by the institutionbill payment: Payment of a billcash: Cash deposit or withdrawalcashback: Cash withdrawal while making a debit card purchasecheque: Document ordering the payment of money to another person or organizationdirect debit: Automatic withdrawal of funds initiated by a third party at a regular intervalinterest: Interest earned or incurredpurchase: Purchase made with a debit or credit cardstanding order: Payment instructed by the account holder to a third party at a regular intervaltransfer: Transfer of money between accountsadjustment, atm, bank charge, bill payment, cash, cashback, cheque, direct debit, interest, purchase, standing order, transfer, nullpersonal_finance _category_icon_urlcounterpartiesnameentity_idtypemerchant: a provider of goods or services for purchase
financial_institution: a financial entity (bank, credit union, BNPL, fintech)
payment_app: a transfer or P2P app (e.g. Zelle)
marketplace: a marketplace (e.g DoorDash, Google Play Store)
payment_terminal: a point-of-sale payment terminal (e.g Square, Toast)
income_source: the payer in an income transaction (e.g., an employer, client, or government agency)merchant, financial_institution, payment_app, marketplace, payment_terminal, income_sourcewebsitelogo_urlconfidence_levelVERY_HIGH: We recognize this counterparty and we are more than 98% confident that it is involved in this transaction.
HIGH: We recognize this counterparty and we are more than 90% confident that it is involved in this transaction.
MEDIUM: We are moderately confident that this counterparty was involved in this transaction, but some details may differ from our records.
LOW: We didn’t find a matching counterparty in our records, so we are returning a cleansed name parsed out of the request description.
UNKNOWN: We don’t know the confidence level for this counterparty.account_numbersinternationalmerchant_entity_idtotal_transactionstotal_transactions is larger than the size of the transactions array, more transactions are available and can be fetched via manipulating the offset parameter.itemitem_iditem_id is always unique; linking the same account at the same institution twice will result in two Items with different item_id values. Like all Plaid identifiers, the item_id is case-sensitive.institution_idnull for Items created without an institution connection, such as Items created via Same Day Micro-deposits.institution_namenull for Items created without an institution connection, such as Items created via Same Day Micro-deposits.webhookauth_methodnull otherwise. For info about the various flows, see our Auth coverage documentation.INSTANT_AUTH: The Item's Auth data was provided directly by the user's institution connection.INSTANT_MATCH: The Item's Auth data was provided via the Instant Match fallback flow.AUTOMATED_MICRODEPOSITS: The Item's Auth data was provided via the Automated Micro-deposits flow.SAME_DAY_MICRODEPOSITS: The Item's Auth data was provided via the Same Day Micro-deposits flow.INSTANT_MICRODEPOSITS: The Item's Auth data was provided via the Instant Micro-deposits flow.DATABASE_MATCH: The Item's Auth data was provided via the Database Match flow.DATABASE_INSIGHTS: The Item's Auth data was provided via the Database Insights flow.TRANSFER_MIGRATED: The Item's Auth data was provided via /transfer/migrate_account.INVESTMENTS_FALLBACK: The Item's Auth data for Investments Move was provided via a fallback flow.INSTANT_AUTH, INSTANT_MATCH, AUTOMATED_MICRODEPOSITS, SAME_DAY_MICRODEPOSITS, INSTANT_MICRODEPOSITS, DATABASE_MATCH, DATABASE_INSIGHTS, TRANSFER_MIGRATED, INVESTMENTS_FALLBACK, nullerrorerror_code and categorized by error_type. Use these in preference to HTTP status codes to identify and handle specific errors. HTTP status codes are set and provide the broadest categorization of errors: 4xx codes are for developer- or user-related errors, and 5xx codes are for Plaid-related errors, and the status will be 2xx in non-error cases. An Item with a non-null error object will only be part of an API response when calling /item/get to view Item status. Otherwise, error fields will be null if no error has occurred; if an error has occurred, an error code will be returned instead.error_typeINVALID_REQUEST, INVALID_RESULT, INVALID_INPUT, INSTITUTION_ERROR, RATE_LIMIT_EXCEEDED, API_ERROR, ITEM_ERROR, ASSET_REPORT_ERROR, RECAPTCHA_ERROR, OAUTH_ERROR, PAYMENT_ERROR, BANK_TRANSFER_ERROR, INCOME_VERIFICATION_ERROR, MICRODEPOSITS_ERROR, SANDBOX_ERROR, PARTNER_ERROR, SIGNAL_ERROR, TRANSACTIONS_ERROR, TRANSACTION_ERROR, TRANSFER_ERROR, CHECK_REPORT_ERROR, CONSUMER_REPORT_ERROR, USER_ERRORerror_codeerror_code_reasonnull will be returned otherwise. Safe for programmatic use.Possible values:
OAUTH_INVALID_TOKEN: The user’s OAuth connection to this institution has been invalidated.OAUTH_CONSENT_EXPIRED: The user's access consent for this OAuth connection to this institution has expired.OAUTH_USER_REVOKED: The user’s OAuth connection to this institution is invalid because the user revoked their connection.error_messagedisplay_messagenull if the error is not related to user action.This may change over time and is not safe for programmatic use.
request_idcausescauses will return an array of errors containing a breakdown of these errors on the individual Item level, if any can be identified.causes will be provided for the error_type ASSET_REPORT_ERROR or CHECK_REPORT_ERROR. causes will also not be populated inside an error nested within a warning object.statusdocumentation_urlsuggested_actionavailable_productsbilled_products.assets, auth, balance, balance_plus, beacon, identity, identity_match, investments, investments_auth, liabilities, payment_initiation, identity_verification, transactions, credit_details, income, income_verification, standing_orders, transfer, employment, recurring_transactions, transactions_refresh, signal, statements, processor_payments, processor_identity, profile, cra_base_report, cra_income_insights, cra_partner_insights, cra_network_insights, cra_cashflow_insights, cra_monitoring, cra_lend_score, layer, pay_by_bank, protect_linked_bankbilled_productsavailable_products. Note - billed_products is populated in all environments but only requests in Production are billed. Also note that products that are billed on a pay-per-call basis rather than a pay-per-Item basis, such as balance, will not appear here.assets, auth, balance, balance_plus, beacon, identity, identity_match, investments, investments_auth, liabilities, payment_initiation, identity_verification, transactions, credit_details, income, income_verification, standing_orders, transfer, employment, recurring_transactions, transactions_refresh, signal, statements, processor_payments, processor_identity, profile, cra_base_report, cra_income_insights, cra_partner_insights, cra_network_insights, cra_cashflow_insights, cra_monitoring, cra_lend_score, layer, pay_by_bank, protect_linked_bankproductsbilled_products field. For some products, it is possible for the product to be added to an Item but not yet billed (e.g. Assets, before /asset_report/create has been called, or Auth or Identity when added as Optional Products but before their endpoints have been called), in which case the product may appear in products but not in billed_products.assets, auth, balance, balance_plus, beacon, identity, identity_match, investments, investments_auth, liabilities, payment_initiation, identity_verification, transactions, credit_details, income, income_verification, standing_orders, transfer, employment, recurring_transactions, transactions_refresh, signal, statements, processor_payments, processor_identity, profile, cra_base_report, cra_income_insights, cra_partner_insights, cra_network_insights, cra_cashflow_insights, cra_monitoring, cra_lend_score, layer, pay_by_bank, protect_linked_bankconsented_productsassets, auth, balance, balance_plus, beacon, identity, identity_match, investments, investments_auth, liabilities, transactions, income, income_verification, transfer, employment, recurring_transactions, signal, statements, processor_payments, processor_identity, cra_base_report, cra_income_insights, cra_lend_score, cra_partner_insights, cra_cashflow_insights, cra_monitoring, layerconsent_expiration _timenull. Currently, only institutions in Europe and a small number of institutions in the US have expiring consent. For a list of US institutions that currently expire consent, see the OAuth Guide.date-time update_typebackground - Item can be updated in the backgrounduser_present_required - Item requires user interaction to be updatedbackground, user_present_requiredrequest_id{
"accounts": [
{
"account_id": "BxBXxLj1m4HMXBm9WZZmCWVbPjX16EHwv99vp",
"balances": {
"available": 110.94,
"current": 110.94,
"iso_currency_code": "USD",
"limit": null,
"unofficial_currency_code": null
},
"mask": "0000",
"name": "Plaid Checking",
"official_name": "Plaid Gold Standard 0% Interest Checking",
"subtype": "checking",
"type": "depository"
}
],
"transactions": [
{
"account_id": "BxBXxLj1m4HMXBm9WZZmCWVbPjX16EHwv99vp",
"account_owner": null,
"amount": 28.34,
"iso_currency_code": "USD",
"unofficial_currency_code": null,
"check_number": null,
"counterparties": [
{
"name": "DoorDash",
"type": "marketplace",
"logo_url": "https://plaid-counterparty-logos.plaid.com/doordash_1.png",
"website": "doordash.com",
"entity_id": "YNRJg5o2djJLv52nBA1Yn1KpL858egYVo4dpm",
"confidence_level": "HIGH"
},
{
"name": "Burger King",
"type": "merchant",
"logo_url": "https://plaid-merchant-logos.plaid.com/burger_king_155.png",
"website": "burgerking.com",
"entity_id": "mVrw538wamwdm22mK8jqpp7qd5br0eeV9o4a1",
"confidence_level": "VERY_HIGH"
}
],
"date": "2023-09-28",
"datetime": "2023-09-28T15:10:09Z",
"authorized_date": "2023-09-27",
"authorized_datetime": "2023-09-27T08:01:58Z",
"location": {
"address": null,
"city": null,
"region": null,
"postal_code": null,
"country": null,
"lat": null,
"lon": null,
"store_number": null
},
"name": "Dd Doordash Burgerkin",
"merchant_name": "Burger King",
"merchant_entity_id": "mVrw538wamwdm22mK8jqpp7qd5br0eeV9o4a1",
"logo_url": "https://plaid-merchant-logos.plaid.com/burger_king_155.png",
"website": "burgerking.com",
"payment_meta": {
"by_order_of": null,
"payee": null,
"payer": null,
"payment_method": null,
"payment_processor": null,
"ppd_id": null,
"reason": null,
"reference_number": null
},
"payment_channel": "online",
"pending": true,
"pending_transaction_id": null,
"personal_finance_category": {
"primary": "FOOD_AND_DRINK",
"detailed": "FOOD_AND_DRINK_FAST_FOOD",
"confidence_level": "VERY_HIGH"
},
"personal_finance_category_icon_url": "https://plaid-category-icons.plaid.com/PFC_FOOD_AND_DRINK.png",
"transaction_id": "yhnUVvtcGGcCKU0bcz8PDQr5ZUxUXebUvbKC0",
"transaction_code": null,
"transaction_type": "digital"
},
{
"account_id": "BxBXxLj1m4HMXBm9WZZmCWVbPjX16EHwv99vp",
"account_owner": null,
"amount": 72.1,
"iso_currency_code": "USD",
"unofficial_currency_code": null,
"check_number": null,
"counterparties": [
{
"name": "Walmart",
"type": "merchant",
"logo_url": "https://plaid-merchant-logos.plaid.com/walmart_1100.png",
"website": "walmart.com",
"entity_id": "O5W5j4dN9OR3E6ypQmjdkWZZRoXEzVMz2ByWM",
"confidence_level": "VERY_HIGH"
}
],
"date": "2023-09-24",
"datetime": "2023-09-24T11:01:01Z",
"authorized_date": "2023-09-22",
"authorized_datetime": "2023-09-22T10:34:50Z",
"location": {
"address": "13425 Community Rd",
"city": "Poway",
"region": "CA",
"postal_code": "92064",
"country": "US",
"lat": 32.959068,
"lon": -117.037666,
"store_number": "1700"
},
"name": "PURCHASE WM SUPERCENTER #1700",
"merchant_name": "Walmart",
"merchant_entity_id": "O5W5j4dN9OR3E6ypQmjdkWZZRoXEzVMz2ByWM",
"logo_url": "https://plaid-merchant-logos.plaid.com/walmart_1100.png",
"website": "walmart.com",
"payment_meta": {
"by_order_of": null,
"payee": null,
"payer": null,
"payment_method": null,
"payment_processor": null,
"ppd_id": null,
"reason": null,
"reference_number": null
},
"payment_channel": "in store",
"pending": false,
"pending_transaction_id": "no86Eox18VHMvaOVL7gPUM9ap3aR1LsAVZ5nc",
"personal_finance_category": {
"primary": "GENERAL_MERCHANDISE",
"detailed": "GENERAL_MERCHANDISE_SUPERSTORES",
"confidence_level": "VERY_HIGH"
},
"personal_finance_category_icon_url": "https://plaid-category-icons.plaid.com/PFC_GENERAL_MERCHANDISE.png",
"transaction_id": "lPNjeW1nR6CDn5okmGQ6hEpMo4lLNoSrzqDje",
"transaction_code": null,
"transaction_type": "place"
}
],
"item": {
"available_products": [
"balance",
"identity",
"investments"
],
"billed_products": [
"assets",
"auth",
"liabilities",
"transactions"
],
"consent_expiration_time": null,
"error": null,
"institution_id": "ins_3",
"institution_name": "Chase",
"item_id": "eVBnVMp7zdTJLkRNr33Rs6zr7KNJqBFL9DrE6",
"update_type": "background",
"webhook": "https://www.genericwebhookurl.com/webhook",
"auth_method": "INSTANT_AUTH"
},
"total_transactions": 1,
"request_id": "45QSn"
}/transactions/recurring/get
Fetch recurring transaction streams
The /transactions/recurring/get endpoint allows developers to receive a summary of the recurring outflow and inflow streams (expenses and deposits) from a user’s checking, savings or credit card accounts. Additionally, Plaid provides key insights about each recurring stream including the category, merchant, last amount, and more. Developers can use these insights to build tools and experiences that help their users better manage cash flow, monitor subscriptions, reduce spend, and stay on track with bill payments.
This endpoint is offered as an add-on to Transactions. To request access to this endpoint, submit a product access request or contact your Plaid account manager.
This endpoint can only be called on an Item that has already been initialized with Transactions (either during Link, by specifying it in /link/token/create; or after Link, by calling /transactions/get or /transactions/sync).
When using Recurring Transactions, for best results, make sure to use the days_requested parameter to request at least 180 days of history when initializing Items with Transactions. Once all historical transactions have been fetched, call /transactions/recurring/get to receive the Recurring Transactions streams and subscribe to the RECURRING_TRANSACTIONS_UPDATE webhook. To know when historical transactions have been fetched, if you are using /transactions/sync listen for the SYNC_UPDATES_AVAILABLE webhook and check that the historical_update_complete field in the payload is true. If using /transactions/get, listen for the HISTORICAL_UPDATE webhook.
After the initial call, you can call /transactions/recurring/get endpoint at any point in the future to retrieve the latest summary of recurring streams. Listen to the RECURRING_TRANSACTIONS_UPDATE webhook to be notified when new updates are available.
Request fields
client_idclient_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_tokensecretsecret. The secret is required and may be provided either in the PLAID-SECRET header or as part of a request body.account_idsaccount_ids to retrieve for the Item. Retrieves all active accounts on item if no account_ids are provided.Note: An error will be returned if a provided
account_id is not associated with the Item.const request: TransactionsGetRequest = {
access_token: accessToken,
account_ids : accountIds
};
try {
const response = await client.transactionsRecurringGet(request);
let inflowStreams = response.data.inflowStreams;
let outflowStreams = response.data.outflowStreams;
}
} catch((err) => {
// handle error
}
Response fields
inflow_streamsaccount_idstream_iddescriptionmerchant_namefirst_datedate last_datedate predicted_next_datedate frequencyWEEKLY: Assigned to a transaction stream that occurs approximately every week.BIWEEKLY: Assigned to a transaction stream that occurs approximately every 2 weeks.SEMI_MONTHLY: Assigned to a transaction stream that occurs approximately twice per month. This frequency is typically seen for inflow transaction streams.MONTHLY: Assigned to a transaction stream that occurs approximately every month.ANNUALLY: Assigned to a transaction stream that occurs approximately every year.UNKNOWN: Assigned to a transaction stream that does not fit any of the pre-defined frequencies.UNKNOWN, WEEKLY, BIWEEKLY, SEMI_MONTHLY, MONTHLY, ANNUALLYtransaction_idsaverage_amountamountdouble iso_currency_codenull if unofficial_currency_code is non-null.See the currency code schema for a full listing of supported
iso_currency_codes.unofficial_currency _codenull if iso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.last_amountamountdouble iso_currency_codenull if unofficial_currency_code is non-null.See the currency code schema for a full listing of supported
iso_currency_codes.unofficial_currency _codenull if iso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.is_activestatusMATURE: A MATURE recurring stream should have at least 3 transactions and happen on a regular cadence (For Annual recurring stream, we will mark it MATURE after 2 instances).EARLY_DETECTION: When a recurring transaction first appears in the transaction history and before it fulfills the requirement of a mature stream, the status will be EARLY_DETECTION.TOMBSTONED: A stream that was previously in the EARLY_DETECTION status will move to the TOMBSTONED status when no further transactions were found at the next expected date.UNKNOWN: A stream is assigned an UNKNOWN status when none of the other statuses are applicable.UNKNOWN, MATURE, EARLY_DETECTION, TOMBSTONEDpersonal_finance _categorySee the
taxonomy CSV file for a full list of personal finance categories. If you are migrating to personal finance categories from the legacy categories, also refer to the migration guide.primarydetailedconfidence_levelVERY_HIGH: We are more than 98% confident that this category reflects the intent of the transaction.
HIGH: We are more than 90% confident that this category reflects the intent of the transaction.
MEDIUM: We are moderately confident that this category reflects the intent of the transaction.
LOW: This category may reflect the intent, but there may be other categories that are more accurate.
UNKNOWN: We don’t know the confidence level for this category.is_user_modifiedfalse.outflow_streamsaccount_idstream_iddescriptionmerchant_namefirst_datedate last_datedate predicted_next_datedate frequencyWEEKLY: Assigned to a transaction stream that occurs approximately every week.BIWEEKLY: Assigned to a transaction stream that occurs approximately every 2 weeks.SEMI_MONTHLY: Assigned to a transaction stream that occurs approximately twice per month. This frequency is typically seen for inflow transaction streams.MONTHLY: Assigned to a transaction stream that occurs approximately every month.ANNUALLY: Assigned to a transaction stream that occurs approximately every year.UNKNOWN: Assigned to a transaction stream that does not fit any of the pre-defined frequencies.UNKNOWN, WEEKLY, BIWEEKLY, SEMI_MONTHLY, MONTHLY, ANNUALLYtransaction_idsaverage_amountamountdouble iso_currency_codenull if unofficial_currency_code is non-null.See the currency code schema for a full listing of supported
iso_currency_codes.unofficial_currency _codenull if iso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.last_amountamountdouble iso_currency_codenull if unofficial_currency_code is non-null.See the currency code schema for a full listing of supported
iso_currency_codes.unofficial_currency _codenull if iso_currency_code is non-null. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.is_activestatusMATURE: A MATURE recurring stream should have at least 3 transactions and happen on a regular cadence (For Annual recurring stream, we will mark it MATURE after 2 instances).EARLY_DETECTION: When a recurring transaction first appears in the transaction history and before it fulfills the requirement of a mature stream, the status will be EARLY_DETECTION.TOMBSTONED: A stream that was previously in the EARLY_DETECTION status will move to the TOMBSTONED status when no further transactions were found at the next expected date.UNKNOWN: A stream is assigned an UNKNOWN status when none of the other statuses are applicable.UNKNOWN, MATURE, EARLY_DETECTION, TOMBSTONEDpersonal_finance _categorySee the
taxonomy CSV file for a full list of personal finance categories. If you are migrating to personal finance categories from the legacy categories, also refer to the migration guide.primarydetailedconfidence_levelVERY_HIGH: We are more than 98% confident that this category reflects the intent of the transaction.
HIGH: We are more than 90% confident that this category reflects the intent of the transaction.
MEDIUM: We are moderately confident that this category reflects the intent of the transaction.
LOW: This category may reflect the intent, but there may be other categories that are more accurate.
UNKNOWN: We don’t know the confidence level for this category.is_user_modifiedfalse.updated_datetimeYYYY-MM-DDTHH:mm:ssZ) indicating the last time transaction streams for the given account were updated ondate-time request_id{
"updated_datetime": "2022-05-01T00:00:00Z",
"inflow_streams": [
{
"account_id": "lPNjeW1nR6CDn5okmGQ6hEpMo4lLNoSrzqDje",
"stream_id": "no86Eox18VHMvaOVL7gPUM9ap3aR1LsAVZ5nc",
"category": null,
"category_id": null,
"description": "Platypus Payroll",
"merchant_name": null,
"personal_finance_category": {
"primary": "INCOME",
"detailed": "INCOME_WAGES",
"confidence_level": "UNKNOWN"
},
"first_date": "2022-02-28",
"last_date": "2022-04-30",
"predicted_next_date": "2022-05-15",
"frequency": "SEMI_MONTHLY",
"transaction_ids": [
"nkeaNrDGrhdo6c4qZWDA8ekuIPuJ4Avg5nKfw",
"EfC5ekksdy30KuNzad2tQupW8WIPwvjXGbGHL",
"ozfvj3FFgp6frbXKJGitsDzck5eWQH7zOJBYd",
"QvdDE8AqVWo3bkBZ7WvCd7LskxVix8Q74iMoK",
"uQozFPfMzibBouS9h9tz4CsyvFll17jKLdPAF"
],
"average_amount": {
"amount": -800,
"iso_currency_code": "USD",
"unofficial_currency_code": null
},
"last_amount": {
"amount": -1000,
"iso_currency_code": "USD",
"unofficial_currency_code": null
},
"is_active": true,
"status": "MATURE",
"is_user_modified": false
}
],
"outflow_streams": [
{
"account_id": "lPNjeW1nR6CDn5okmGQ6hEpMo4lLNoSrzqDff",
"stream_id": "no86Eox18VHMvaOVL7gPUM9ap3aR1LsAVZ5nd",
"category": null,
"category_id": null,
"description": "ConEd Bill Payment",
"merchant_name": "ConEd",
"personal_finance_category": {
"primary": "RENT_AND_UTILITIES",
"detailed": "RENT_AND_UTILITIES_GAS_AND_ELECTRICITY",
"confidence_level": "UNKNOWN"
},
"first_date": "2022-02-04",
"last_date": "2022-05-02",
"predicted_next_date": "2022-06-02",
"frequency": "MONTHLY",
"transaction_ids": [
"yhnUVvtcGGcCKU0bcz8PDQr5ZUxUXebUvbKC0",
"HPDnUVgI5Pa0YQSl0rxwYRwVXeLyJXTWDAvpR",
"jEPoSfF8xzMClE9Ohj1he91QnvYoSdwg7IT8L",
"CmdQTNgems8BT1B7ibkoUXVPyAeehT3Tmzk0l"
],
"average_amount": {
"amount": 85,
"iso_currency_code": "USD",
"unofficial_currency_code": null
},
"last_amount": {
"amount": 100,
"iso_currency_code": "USD",
"unofficial_currency_code": null
},
"is_active": true,
"status": "MATURE",
"is_user_modified": false
},
{
"account_id": "lPNjeW1nR6CDn5okmGQ6hEpMo4lLNoSrzqDff",
"stream_id": "SrBNJZDuUMweodmPmSOeOImwsWt53ZXfJQAfC",
"category": null,
"category_id": null,
"description": "Costco Annual Membership",
"merchant_name": "Costco",
"personal_finance_category": {
"primary": "GENERAL_MERCHANDISE",
"detailed": "GENERAL_MERCHANDISE_SUPERSTORES",
"confidence_level": "UNKNOWN"
},
"first_date": "2022-01-23",
"last_date": "2023-01-22",
"predicted_next_date": "2024-01-22",
"frequency": "ANNUALLY",
"transaction_ids": [
"yqEBJ72cS4jFwcpxJcDuQr94oAQ1R1lMC33D4",
"Kz5Hm3cZCgpn4tMEKUGAGD6kAcxMBsEZDSwJJ"
],
"average_amount": {
"amount": 120,
"iso_currency_code": "USD",
"unofficial_currency_code": null
},
"last_amount": {
"amount": 120,
"iso_currency_code": "USD",
"unofficial_currency_code": null
},
"is_active": true,
"status": "MATURE",
"is_user_modified": false
}
],
"request_id": "tbFyCEqkU775ZGG"
}/transactions/refresh
Refresh transaction data
/transactions/refresh is an optional endpoint that initiates an on-demand extraction to fetch the newest transactions for an Item. The on-demand extraction takes place in addition to the periodic extractions that automatically occur one or more times per day for any Transactions-enabled Item. The Item must already have Transactions added as a product in order to call /transactions/refresh.
If changes to transactions are discovered after calling /transactions/refresh, Plaid will fire a webhook: for /transactions/sync users, SYNC_UPDATES_AVAILABLE will be fired if there are any transactions updated, added, or removed. For users of both /transactions/sync and /transactions/get, TRANSACTIONS_REMOVED will be fired if any removed transactions are detected, and DEFAULT_UPDATE will be fired if any new transactions are detected. New transactions can be fetched by calling /transactions/get or /transactions/sync.
Note that the /transactions/refresh endpoint is not supported for Capital One (ins_128026) non-depository accounts and will result in a PRODUCTS_NOT_SUPPORTED error if called on an Item that contains only non-depository accounts from that institution.
As this endpoint triggers a synchronous request for fresh data, latency may be higher than for other Plaid endpoints (typically less than 10 seconds, but occasionally up to 30 seconds or more); if you encounter errors, you may find it necessary to adjust your timeout period when making requests./transactions/refresh is offered as an optional add-on to Transactions and has a separate fee model. To request access to this endpoint, submit a product access request or contact your Plaid account manager.
Request fields
client_idclient_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_tokensecretsecret. The secret is required and may be provided either in the PLAID-SECRET header or as part of a request body.const request: TransactionsRefreshRequest = {
access_token: accessToken,
};
try {
await plaidClient.transactionsRefresh(request);
} catch (error) {
// handle error
}
Response fields
request_id{
"request_id": "1vwmF5TBQwiqfwP"
}/categories/get
(Deprecated) Get legacy categories
Send a request to the /categories/get endpoint to get detailed information on legacy categories returned by Plaid. This endpoint does not require authentication.
All implementations are recommended to use the newer personal_finance_category taxonomy instead of the legacy category taxonomy supported by this endpoint. The personal_finance_category taxonomy CSV file is available for download and is not accessible via API.
Request fields
try {
const response = await plaidClient.categoriesGet({});
const categories = response.data.categories;
} catch (error) {
// handle error
}
Response fields
categoriescategory_idcategory_id is a Plaid-specific identifier and does not necessarily correspond to merchant category codes.groupplace for physical transactions or special for other transactions such as bank charges.hierarchycategory_id belongs.request_id{
"categories": [
{
"category_id": "10000000",
"group": "special",
"hierarchy": [
"Bank Fees"
]
},
{
"category_id": "10001000",
"group": "special",
"hierarchy": [
"Bank Fees",
"Overdraft"
]
},
{
"category_id": "12001000",
"group": "place",
"hierarchy": [
"Community",
"Animal Shelter"
]
}
],
"request_id": "ixTBLZGvhD4NnmB"
}Webhooks
You can receive notifications via a webhook whenever there are new transactions associated with an Item, including when Plaid’s initial and historical transaction pull are completed. All webhooks related to transactions have a webhook_type of TRANSACTIONS.
SYNC_UPDATES_AVAILABLE
Fired when an Item's transactions change. This can be due to any event resulting in new changes, such as an initial 30-day transactions fetch upon the initialization of an Item with transactions, the backfill of historical transactions that occurs shortly after, or when changes are populated from a regularly-scheduled transactions update job. It is recommended to listen for the SYNC_UPDATES_AVAILABLE webhook when using the /transactions/sync endpoint. Note that when using /transactions/sync the older webhooks INITIAL_UPDATE, HISTORICAL_UPDATE, DEFAULT_UPDATE, and TRANSACTIONS_REMOVED, which are intended for use with /transactions/get, will also continue to be sent in order to maintain backwards compatibility. It is not necessary to listen for and respond to those webhooks when using /transactions/sync.
After receipt of this webhook, the new changes can be fetched for the Item from /transactions/sync.
Note that to receive this webhook for an Item, /transactions/sync must have been called at least once on that Item. This means that, unlike the INITIAL_UPDATE and HISTORICAL_UPDATE webhooks, it will not fire immediately upon Item creation. If /transactions/sync is called on an Item that was not initialized with Transactions, the webhook will fire twice: once the first 30 days of transactions data has been fetched, and a second time when all available historical transactions data has been fetched.
This webhook will fire in the Sandbox environment as it would in Production. It can also be manually triggered in Sandbox by calling /sandbox/item/fire_webhook.
Properties
webhook_typeTRANSACTIONSwebhook_codeSYNC_UPDATES_AVAILABLEitem_iditem_id of the Item associated with this webhook, warning, or errorinitial_update _completehistorical_update _completeenvironmentsandbox, production{
"webhook_type": "TRANSACTIONS",
"webhook_code": "SYNC_UPDATES_AVAILABLE",
"item_id": "wz666MBjYWTp2PDzzggYhM6oWWmBb",
"initial_update_complete": true,
"historical_update_complete": false,
"environment": "production"
}RECURRING_TRANSACTIONS_UPDATE
Fired when recurring transactions data is updated. This includes when a new recurring stream is detected or when a new transaction is added to an existing recurring stream. The RECURRING_TRANSACTIONS_UPDATE webhook will also fire when one or more attributes of the recurring stream changes, which is usually a result of the addition, update, or removal of transactions to the stream.
After receipt of this webhook, the updated data can be fetched from /transactions/recurring/get.
Properties
webhook_typeTRANSACTIONSwebhook_codeRECURRING_TRANSACTIONS_UPDATEitem_iditem_id of the Item associated with this webhook, warning, or erroraccount_idsaccount_ids for accounts that have new or updated recurring transactions data.environmentsandbox, production{
"webhook_type": "TRANSACTIONS",
"webhook_code": "RECURRING_TRANSACTIONS_UPDATE",
"item_id": "wz666MBjYWTp2PDzzggYhM6oWWmBb",
"account_ids": [
"lPNjeW1nR6CDn5okmGQ6hEpMo4lLNoSrzqDje",
"lPNjeW1nR6CDn5okmGQ6hEpMo4lLNoSrzqDff"
],
"environment": "production"
}INITIAL_UPDATE
Fired when an Item's initial transaction pull is completed. Once this webhook has been fired, transaction data for the most recent 30 days can be fetched for the Item. This webhook will also be fired if account selections for the Item are updated, with new_transactions set to the number of net new transactions pulled after the account selection update.
This webhook is intended for use with /transactions/get; if you are using the newer /transactions/sync endpoint, this webhook will still be fired to maintain backwards compatibility, but it is recommended to listen for and respond to the SYNC_UPDATES_AVAILABLE webhook instead.
Properties
webhook_typeTRANSACTIONSwebhook_codeINITIAL_UPDATEerrornew_transactionsitem_iditem_id of the Item associated with this webhook, warning, or errorenvironmentsandbox, production{
"webhook_type": "TRANSACTIONS",
"webhook_code": "INITIAL_UPDATE",
"item_id": "wz666MBjYWTp2PDzzggYhM6oWWmBb",
"error": null,
"new_transactions": 19,
"environment": "production"
}HISTORICAL_UPDATE
Fired when an Item's historical transaction pull is completed and Plaid has prepared as much historical transaction data as possible for the Item. Once this webhook has been fired, transaction data beyond the most recent 30 days can be fetched for the Item. This webhook will also be fired if account selections for the Item are updated, with new_transactions set to the number of net new transactions pulled after the account selection update.
This webhook is intended for use with /transactions/get; if you are using the newer /transactions/sync endpoint, this webhook will still be fired to maintain backwards compatibility, but it is recommended to listen for and respond to the SYNC_UPDATES_AVAILABLE webhook instead.
Properties
webhook_typeTRANSACTIONSwebhook_codeHISTORICAL_UPDATEerrorerror_code and categorized by error_type. Use these in preference to HTTP status codes to identify and handle specific errors. HTTP status codes are set and provide the broadest categorization of errors: 4xx codes are for developer- or user-related errors, and 5xx codes are for Plaid-related errors, and the status will be 2xx in non-error cases. An Item with a non-null error object will only be part of an API response when calling /item/get to view Item status. Otherwise, error fields will be null if no error has occurred; if an error has occurred, an error code will be returned instead.error_typeINVALID_REQUEST, INVALID_RESULT, INVALID_INPUT, INSTITUTION_ERROR, RATE_LIMIT_EXCEEDED, API_ERROR, ITEM_ERROR, ASSET_REPORT_ERROR, RECAPTCHA_ERROR, OAUTH_ERROR, PAYMENT_ERROR, BANK_TRANSFER_ERROR, INCOME_VERIFICATION_ERROR, MICRODEPOSITS_ERROR, SANDBOX_ERROR, PARTNER_ERROR, SIGNAL_ERROR, TRANSACTIONS_ERROR, TRANSACTION_ERROR, TRANSFER_ERROR, CHECK_REPORT_ERROR, CONSUMER_REPORT_ERROR, USER_ERRORerror_codeerror_code_reasonnull will be returned otherwise. Safe for programmatic use.Possible values:
OAUTH_INVALID_TOKEN: The user’s OAuth connection to this institution has been invalidated.OAUTH_CONSENT_EXPIRED: The user's access consent for this OAuth connection to this institution has expired.OAUTH_USER_REVOKED: The user’s OAuth connection to this institution is invalid because the user revoked their connection.error_messagedisplay_messagenull if the error is not related to user action.This may change over time and is not safe for programmatic use.
request_idcausescauses will return an array of errors containing a breakdown of these errors on the individual Item level, if any can be identified.causes will be provided for the error_type ASSET_REPORT_ERROR or CHECK_REPORT_ERROR. causes will also not be populated inside an error nested within a warning object.statusdocumentation_urlsuggested_actionnew_transactionsitem_iditem_id of the Item associated with this webhook, warning, or errorenvironmentsandbox, production{
"webhook_type": "TRANSACTIONS",
"webhook_code": "HISTORICAL_UPDATE",
"item_id": "wz666MBjYWTp2PDzzggYhM6oWWmBb",
"error": null,
"new_transactions": 231,
"environment": "production"
}DEFAULT_UPDATE
Fired when new transaction data is available for an Item. Plaid will typically check for new transaction data several times a day.
This webhook is intended for use with /transactions/get; if you are using the newer /transactions/sync endpoint, this webhook will still be fired to maintain backwards compatibility, but it is recommended to listen for and respond to the SYNC_UPDATES_AVAILABLE webhook instead.
Properties
webhook_typeTRANSACTIONSwebhook_codeDEFAULT_UPDATEerrorerror_code and categorized by error_type. Use these in preference to HTTP status codes to identify and handle specific errors. HTTP status codes are set and provide the broadest categorization of errors: 4xx codes are for developer- or user-related errors, and 5xx codes are for Plaid-related errors, and the status will be 2xx in non-error cases. An Item with a non-null error object will only be part of an API response when calling /item/get to view Item status. Otherwise, error fields will be null if no error has occurred; if an error has occurred, an error code will be returned instead.error_typeINVALID_REQUEST, INVALID_RESULT, INVALID_INPUT, INSTITUTION_ERROR, RATE_LIMIT_EXCEEDED, API_ERROR, ITEM_ERROR, ASSET_REPORT_ERROR, RECAPTCHA_ERROR, OAUTH_ERROR, PAYMENT_ERROR, BANK_TRANSFER_ERROR, INCOME_VERIFICATION_ERROR, MICRODEPOSITS_ERROR, SANDBOX_ERROR, PARTNER_ERROR, SIGNAL_ERROR, TRANSACTIONS_ERROR, TRANSACTION_ERROR, TRANSFER_ERROR, CHECK_REPORT_ERROR, CONSUMER_REPORT_ERROR, USER_ERRORerror_codeerror_code_reasonnull will be returned otherwise. Safe for programmatic use.Possible values:
OAUTH_INVALID_TOKEN: The user’s OAuth connection to this institution has been invalidated.OAUTH_CONSENT_EXPIRED: The user's access consent for this OAuth connection to this institution has expired.OAUTH_USER_REVOKED: The user’s OAuth connection to this institution is invalid because the user revoked their connection.error_messagedisplay_messagenull if the error is not related to user action.This may change over time and is not safe for programmatic use.
request_idcausescauses will return an array of errors containing a breakdown of these errors on the individual Item level, if any can be identified.causes will be provided for the error_type ASSET_REPORT_ERROR or CHECK_REPORT_ERROR. causes will also not be populated inside an error nested within a warning object.statusdocumentation_urlsuggested_actionnew_transactionsitem_iditem_id of the Item the webhook relates to.environmentsandbox, production{
"webhook_type": "TRANSACTIONS",
"webhook_code": "DEFAULT_UPDATE",
"item_id": "wz666MBjYWTp2PDzzggYhM6oWWmBb",
"error": null,
"new_transactions": 3,
"environment": "production"
}TRANSACTIONS_REMOVED
Fired when transaction(s) for an Item are deleted. The deleted transaction IDs are included in the webhook payload. Plaid will typically check for deleted transaction data several times a day.
This webhook is intended for use with /transactions/get; if you are using the newer /transactions/sync endpoint, this webhook will still be fired to maintain backwards compatibility, but it is recommended to listen for and respond to the SYNC_UPDATES_AVAILABLE webhook instead.
Properties
webhook_typeTRANSACTIONSwebhook_codeTRANSACTIONS_REMOVEDerrorerror_code and categorized by error_type. Use these in preference to HTTP status codes to identify and handle specific errors. HTTP status codes are set and provide the broadest categorization of errors: 4xx codes are for developer- or user-related errors, and 5xx codes are for Plaid-related errors, and the status will be 2xx in non-error cases. An Item with a non-null error object will only be part of an API response when calling /item/get to view Item status. Otherwise, error fields will be null if no error has occurred; if an error has occurred, an error code will be returned instead.error_typeINVALID_REQUEST, INVALID_RESULT, INVALID_INPUT, INSTITUTION_ERROR, RATE_LIMIT_EXCEEDED, API_ERROR, ITEM_ERROR, ASSET_REPORT_ERROR, RECAPTCHA_ERROR, OAUTH_ERROR, PAYMENT_ERROR, BANK_TRANSFER_ERROR, INCOME_VERIFICATION_ERROR, MICRODEPOSITS_ERROR, SANDBOX_ERROR, PARTNER_ERROR, SIGNAL_ERROR, TRANSACTIONS_ERROR, TRANSACTION_ERROR, TRANSFER_ERROR, CHECK_REPORT_ERROR, CONSUMER_REPORT_ERROR, USER_ERRORerror_codeerror_code_reasonnull will be returned otherwise. Safe for programmatic use.Possible values:
OAUTH_INVALID_TOKEN: The user’s OAuth connection to this institution has been invalidated.OAUTH_CONSENT_EXPIRED: The user's access consent for this OAuth connection to this institution has expired.OAUTH_USER_REVOKED: The user’s OAuth connection to this institution is invalid because the user revoked their connection.error_messagedisplay_messagenull if the error is not related to user action.This may change over time and is not safe for programmatic use.
request_idcausescauses will return an array of errors containing a breakdown of these errors on the individual Item level, if any can be identified.causes will be provided for the error_type ASSET_REPORT_ERROR or CHECK_REPORT_ERROR. causes will also not be populated inside an error nested within a warning object.statusdocumentation_urlsuggested_actionremoved_transactionstransaction_ids corresponding to the removed transactionsitem_iditem_id of the Item associated with this webhook, warning, or errorenvironmentsandbox, production{
"webhook_type": "TRANSACTIONS",
"webhook_code": "TRANSACTIONS_REMOVED",
"item_id": "wz666MBjYWTp2PDzzggYhM6oWWmBb",
"removed_transactions": [
"yBVBEwrPyJs8GvR77N7QTxnGg6wG74H7dEDN6",
"kgygNvAVPzSX9KkddNdWHaVGRVex1MHm3k9no"
],
"error": null,
"environment": "production"
}