---
title: "Enrich locally-held transaction data"
method: POST
path: "/transactions/enrich"
tags: ["plaid"]
---

# Enrich locally-held transaction data

`POST /transactions/enrich`

The `/transactions/enrich` endpoint enriches raw transaction data generated by your own banking products or retrieved from other non-Plaid sources.

## Request body

- TransactionsEnrichRequest — TransactionsEnrichRequest defines the request schema for `/transactions/enrich`.
  - `client_id` string — Your Plaid API `client_id`. The `client_id` is required and may be provided either in the `PLAID-CLIENT-ID` header or as part of a request body.
  - `secret` string — Your Plaid API `secret`. The `secret` is required and may be provided either in the `PLAID-SECRET` header or as part of a request body.
  - `account_type` string, required — The account type for the requested transactions (either `depository` or `credit`).
  - `transactions` ClientProvidedTransaction[], required — An array of transaction objects to be enriched by Plaid. Maximum of 100 transactions per request.
    - `id` string, required — A unique ID for the transaction used to help you tie data back to your systems.
    - `user_id` string — The Plaid generated ID that identifies the end user for whom you would like to enrich transactions.
    - `client_user_id` string — A unique user id used to group transactions for a given user, as a unique identifier from your application. Personally identifiable information, such as an email address or phone number, should not be used in the `client_user_id`.
    - `client_account_id` string — A unique account id used to group transactions for a given account, as a unique identifier from your application. Personally identifiable information, such as an email address or phone number, should not be used in the `client_account_id`.
    - `account_type` string — The account type associated with the transaction. For a full list of valid types and subtypes, see the [Account schema](https://plaid.com/docs/api/accounts#account-type-schema).
    - `account_subtype` string — The account subtype associated with the transaction. For a full list of valid types and subtypes, see the [Account schema](https://plaid.com/docs/api/accounts#account-type-schema).
    - `description` string, required — The raw description of the transaction. If you have location data in available an unstructured format, it may be appended to the `description` field.
    - `amount` number, double, required — The absolute value of the transaction (>= 0). When testing Enrich, note that `amount` data should be realistic. Unrealistic or inaccurate `amount` data may result in reduced quality output.
    - `direction` 'INFLOW' | 'OUTFLOW', required — The direction of the transaction from the perspective of the account holder: `OUTFLOW` - Includes outgoing transfers, purchases, and fees. (Typically represented as a negative value on checking accounts and debit cards and a positive value on credit cards.) `INFLOW` - Includes incoming transfers, refunds, and income. (Typically represented as a positive value on checking accounts and debit cards and a negative value on credit cards.)
    - `iso_currency_code` string, required — The ISO-4217 currency code of the transaction e.g. USD.
    - `location` ClientProvidedTransactionLocation — A representation of where a transaction took place. Use this field to pass in structured location information you may have about your transactions. Providing location data is optional but can increase result quality. If you have unstructured location information, it may be appended to the `description` field.
      - `country` string — The country where the transaction occurred, formatted as an ISO 3166-1 alpha-2 country code ("US" or "CA").
      - `region` string — The region or state where the transaction occurred, formatted as the official two-letter US state or Canadian province postal code, e.g. "CT" or "QC".
      - `city` string — The city where the transaction occurred.
      - `address` string — The street address where the transaction occurred.
      - `postal_code` string — The postal code where the transaction occurred.
    - `mcc` string — Merchant category codes (MCCs) are four-digit numbers that describe a merchant's primary business activities.
    - `date_posted` string, date — The date the transaction posted, in [ISO 8601](https://wikipedia.org/wiki/ISO_8601) (YYYY-MM-DD) format.
  - `options` TransactionsEnrichRequestOptions — An optional object to be used with the request.
    - `include_legacy_category` boolean — Include `legacy_category` and `legacy_category_id` in the response (in addition to the default `personal_finance_category`). Categories are based on Plaid's legacy taxonomy. For a full list of legacy categories, see [`/categories/get`](https://plaid.com/docs/api/products/transactions/#categoriesget).
    - `personal_finance_category_version` 'v1' | 'v2' — Indicates which version of the personal finance category taxonomy is being used. [View PFCv2 and PFCv1 taxonomies](https://plaid.com/documents/pfc-taxonomy-all.csv). If you enabled Transactions or Enrich before December 3, 2025 you will receive the `v1` taxonomy by default and may request `v2` by explicitly setting this field to `v2` in the request. If you enabled Transactions or Enrich on or after December 3, 2025, you may only receive the `v2` taxonomy.

## Response `200`

OK

- TransactionsEnrichResponse — TransactionsEnrichResponse defines the response schema for `/transactions/enrich`.
  - `enriched_transactions` ClientProvidedEnrichedTransaction[], required — A list of enriched transactions.
    - `id` string, required — The unique ID for the transaction as provided by you in the request.
    - `client_user_id` string — A unique user id used to group transactions for a given user, as a unique identifier from your application. Personally identifiable information, such as an email address or phone number, should not be used in the `client_user_id`.
    - `client_account_id` string — A unique account id used to group transactions for a given account, as a unique identifier from your application. Personally identifiable information, such as an email address or phone number, should not be used in the `client_account_id`.
    - `account_type` string — The account type associated with the transaction. For a full list of valid types and subtypes, see the [Account schema](https://plaid.com/docs/api/accounts#account-type-schema).
    - `account_subtype` string — The account subtype associated with the transaction. For a full list of valid types and subtypes, see the [Account schema](https://plaid.com/docs/api/accounts#account-type-schema).
    - `description` string, required — The raw description of the transaction.
    - `amount` number, double, required — The absolute value of the transaction (>= 0)
    - `direction` 'INFLOW' | 'OUTFLOW' — The direction of the transaction from the perspective of the account holder: `OUTFLOW` - Includes outgoing transfers, purchases, and fees. (Typically represented as a negative value on checking accounts and debit cards and a positive value on credit cards.) `INFLOW` - Includes incoming transfers, refunds, and income. (Typically represented as a positive value on checking accounts and debit cards and a negative value on credit cards.)
    - `iso_currency_code` string, required — The ISO-4217 currency code of the transaction e.g. USD.
    - `enrichments` Enrichments, required — A grouping of the Plaid produced transaction enrichment fields.
      - `check_number` string, nullable — The check number of the transaction. This field is only populated for check transactions.
      - `counterparties` Counterparty[], required — The counterparties present in the transaction. Counterparties, such as the merchant or the financial institution, are extracted by Plaid from the raw description.
        - `name` string, required — The name of the counterparty, such as the merchant or the financial institution, as extracted by Plaid from the raw description.
        - `entity_id` string, nullable — A unique, stable, Plaid-generated ID that maps to the counterparty.
        - `type` 'merchant' | 'financial_institution' | 'payment_app' | 'marketplace' | 'payment_terminal' | 'income_source', required — The counterparty type. `merchant`: 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)
        - `website` string, nullable, required — The website associated with the counterparty.
        - `logo_url` string, nullable, required — The URL of a logo associated with the counterparty, if available. The logo will always be a 100×100 pixel PNG file.
        - `confidence_level` string, nullable — A description of how confident we are that the provided counterparty is involved in the transaction. `VERY_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.
        - `phone_number` string, nullable, required — The phone number associated with the counterparty in E.164 format. If there is a location match (i.e. a street address is returned in the location object), the phone number will be location specific.
        - `account_numbers` CounterpartyNumbers, nullable — Account numbers associated with the counterparty, when available. This field is currently only filled in for select financial institutions in Europe.
          - `bacs` CounterpartyNumbersBACS, nullable — Identifying information for a UK bank account via Bacs.
            - `account` string, nullable — The Bacs account number for the account.
            - `sort_code` string, nullable — The Bacs sort code for the account.
          - `international` CounterpartyNumbersInternational, nullable — Account numbers using the International Bank Account Number and BIC/SWIFT code format.
            - `iban` string — International Bank Account Number (IBAN).
            - `bic` string, nullable — Business Identifier Code (BIC) for this counterparty.
      - `entity_id` string, nullable — A unique, stable, Plaid-generated ID that maps to the primary counterparty.
      - `legacy_category_id` string, nullable — The ID of the legacy category to which this transaction belongs. For a full list of legacy categories, see [`/categories/get`](https://plaid.com/docs/api/products/transactions/#categoriesget). We recommend using the `personal_finance_category` for transaction categorization to obtain the best results.
      - `legacy_category` string[], nullable — A hierarchical array of the legacy categories to which this transaction belongs. For a full list of legacy categories, see [`/categories/get`](https://plaid.com/docs/api/products/transactions/#categoriesget). We recommend using the `personal_finance_category` for transaction categorization to obtain the best results.
      - `location` Location, required — A representation of where a transaction took place. Location data is provided only for transactions at physical locations, not for online transactions. Location data availability depends primarily on the merchant and is most likely to be populated for transactions at large retail chains; small, local businesses are less likely to have location data available.
        - `address` string, nullable, required — The street address where the transaction occurred.
        - `city` string, nullable, required — The city where the transaction occurred.
        - `region` string, nullable, required — The region or state where the transaction occurred. In API versions 2018-05-22 and earlier, this field is called `state`.
        - `postal_code` string, nullable, required — The postal code where the transaction occurred. In API versions 2018-05-22 and earlier, this field is called `zip`.
        - `country` string, nullable, required — The ISO 3166-1 alpha-2 country code where the transaction occurred.
        - `lat` number, double, nullable, required — The latitude where the transaction occurred.
        - `lon` number, double, nullable, required — The longitude where the transaction occurred.
        - `store_number` string, nullable, required — The merchant defined store number where the transaction occurred.
      - `logo_url` string, nullable, required — The URL of a logo associated with this transaction, if available. The logo will always be a 100×100 pixel PNG file.
      - `merchant_name` string, nullable, required — The name of the primary counterparty, such as the merchant or the financial institution, as extracted by Plaid from the raw description.
      - `payment_channel` 'online' | 'in store' | 'other', required — The channel used to make a payment. `online:` 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.
      - `phone_number` string, nullable, required — The phone number associated with the counterparty in E.164 format. If there is a location match (i.e. a street address is returned in the location object), the phone number will be location specific.
      - `personal_finance_category` PersonalFinanceCategory, nullable, required — Information describing the intent of the transaction. Most relevant for personal finance use cases, but not limited to such use cases. See the [taxonomy CSV file](https://plaid.com/documents/pfc-taxonomy-all.csv) 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](https://plaid.com/docs/transactions/pfc-migration/).
        - `primary` string, required — A high level category that communicates the broad category of the transaction.
        - `detailed` string, required — A granular category conveying the transaction's intent. This field can also be used as a unique identifier for the category.
        - `confidence_level` string, nullable — A description of how confident we are that the provided categories accurately describe the transaction intent. `VERY_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.
        - `version` 'v1' | 'v2' — Indicates which version of the personal finance category taxonomy is being used. [View PFCv2 and PFCv1 taxonomies](https://plaid.com/documents/pfc-taxonomy-all.csv). If you enabled Transactions or Enrich before December 3, 2025 you will receive the `v1` taxonomy by default and may request `v2` by explicitly setting this field to `v2` in the request. If you enabled Transactions or Enrich on or after December 3, 2025, you may only receive the `v2` taxonomy.
      - `personal_finance_category_icon_url` string, required — The URL of an icon associated with the primary personal finance category. The icon will always be a 100×100 pixel PNG file.
      - `website` string, nullable, required — The website associated with this transaction.
    - `client_customization` ClientCustomization, nullable — Custom client fields
      - `custom_entity_id` string — Custom entity ID that maps to a merchant or counterparty. This is different from the `merchant_entity_id` as well as the `entity_id` on the counterparties object to meet client specific needs.
  - `request_id` string — A unique identifier for the request, which can be used for troubleshooting. This identifier, like all Plaid identifiers, is case sensitive.

## Other responses

- `default` — Error response

---

[API](https://skmtc.net/plaid/apis/the-plaid-api.md) · [All operations](https://skmtc.net/plaid/apis/the-plaid-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/plaid/the-plaid-api/versions/64c4514ea59b/schema)