{
  "opencollection": "1.0.0",
  "info": {
    "name": "Plaid transactions/",
    "version": "2020-09-14_1.517.0"
  },
  "items": [
    {
      "info": {
        "name": "Plaid",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Plaid Get transaction data",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/transactions/get",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "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.\n\nThe `/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 i"
        },
        {
          "info": {
            "name": "Plaid Refresh transaction data",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/transactions/refresh",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "`/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`.\n\nIf changes to transactions are discovered after calling `/transactions/refresh`, Plaid will fire a web"
        },
        {
          "info": {
            "name": "Plaid Fetch recurring transaction streams",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/transactions/recurring/get",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "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"
        },
        {
          "info": {
            "name": "Plaid Get incremental transaction updates on an Item",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/transactions/sync",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/transactions/sync` endpoint allows developers to subscribe to all transactions associated with an Item and get updates synchronously in a stream-like manner, using a cursor to track which updates have already been seen.\n\n`/transactions/sync` provides the same functionality as `/transactions/get` and can be used instead of `/transactions/get` to simplify the process of tracking transactions updates. To learn more about migrating from `/transactions/get`, see the [Transactions Sync migration"
        },
        {
          "info": {
            "name": "Plaid Enrich locally-held transaction data",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/transactions/enrich",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/transactions/enrich` endpoint enriches raw transaction data generated by your own banking products or retrieved from other non-Plaid sources."
        },
        {
          "info": {
            "name": "Plaid Get transaction data",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/processor/transactions/get",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/processor/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). 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 informati"
        },
        {
          "info": {
            "name": "Plaid Get incremental transaction updates on a processor token",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/processor/transactions/sync",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "This endpoint replaces `/processor/transactions/get` and its associated webhooks for most common use-cases.\n\nThe `/processor/transactions/sync` endpoint allows developers to subscribe to all transactions associated with a processor token and get updates synchronously in a stream-like manner, using a cursor to track which updates have already been seen. `/processor/transactions/sync` provides the same functionality as `/processor/transactions/get` and can be used instead of `/processor/transactio"
        },
        {
          "info": {
            "name": "Plaid Refresh transaction data",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/processor/transactions/refresh",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "`/processor/transactions/refresh` is an optional endpoint for users of the Transactions product. It initiates an on-demand extraction to fetch the newest transactions for a processor token. This on-demand extraction takes place in addition to the periodic extractions that automatically occur one or more times per day for any Transactions-enabled processor token. If changes to transactions are discovered after calling `/processor/transactions/refresh`, Plaid will fire a webhook: for `/transaction"
        },
        {
          "info": {
            "name": "Plaid Fetch recurring transaction streams",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/processor/transactions/recurring/get",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/processor/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 sta"
        },
        {
          "info": {
            "name": "Plaid Get investment transactions",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/investments/transactions/get",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/investments/transactions/get` endpoint allows developers to retrieve up to 24 months of user-authorized transaction data for investment accounts.\n\nTransactions are returned in reverse-chronological order, and the sequence of transaction ordering is stable and will not shift.\n\nDue to the potentially large number of investment transactions associated with an Item, results are paginated. Manipulate the count and offset parameters in conjunction with the `total_investment_transactions` respons"
        },
        {
          "info": {
            "name": "Plaid enhance locally-held transaction data",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/beta/transactions/v1/enhance",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/beta/transactions/v1/enhance` endpoint enriches raw transaction data provided directly by clients.\n\nThe product is currently in beta."
        },
        {
          "info": {
            "name": "Plaid Create transaction category rule",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/beta/transactions/rules/v1/create",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/transactions/rules/v1/create` endpoint creates transaction categorization rules.\n\nRules will be applied on the Item's transactions returned in `/transactions/get` response.\n\nThe product is currently in beta. To request access, contact transactions-feedback@plaid.com."
        },
        {
          "info": {
            "name": "Plaid Return a list of rules created for the Item associated with the access token.",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/beta/transactions/rules/v1/list",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/transactions/rules/v1/list` returns a list of transaction rules created for the Item associated with the access token."
        },
        {
          "info": {
            "name": "Plaid Remove transaction rule",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/beta/transactions/rules/v1/remove",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/transactions/rules/v1/remove` endpoint is used to remove a transaction rule."
        },
        {
          "info": {
            "name": "Plaid Obtain user insights based on transactions sent through /transactions/enrich",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://production.plaid.com/beta/transactions/user_insights/v1/get",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The `/beta/transactions/user_insights/v1/get` gets user insights for clients who have enriched data with `/transactions/enrich`.\n\nThe product is currently in beta."
        }
      ]
    }
  ],
  "bundled": true
}