plaid 50.0.0 → 51.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f785d271c20277242d022dafd8b1e797326c888bd4d53daeb482fe46dad14a77
-  data.tar.gz: 0eb287bbfaa0d8129b26c2db3247d76d709aa1cc26a5773ab8b682bfcdf2c228
+  metadata.gz: a96f11319ee49849a144dff17d494c79808e635afd33fa2fa038d44331918462
+  data.tar.gz: db68135c76abff0f24ff358541074e7abbbb8c3e974492593485be73855eca4f
 SHA512:
-  metadata.gz: d521004d542bfc1cfa571e5a037fc7595ad949e94af9c808c3518df942a643a3c31d2ecbcef161fc7178a868e230038669a4e3f8c0d4e9d94a10b58831ae4d76
-  data.tar.gz: 937274bec2ba3475b7f52588ef100b855eccb1cfcdb51e3ba29c23c5733f061b5508cb954fe7d39e78b7e90670f9e558ff584f0b7cce97a7c84cde362aa2422e
+  metadata.gz: adc392c0142b46bbc11eb7ab72117cb82bcf9cc7be0a6516c7c1805af0280eac183bc8c3a72b989136fd45c494c27630e897067b564620d3025d418c10d04542
+  data.tar.gz: a31385873324980128c3c3c8fa071388285b1750a19b96bc1eedc1e46b7978eb48f98db59c20ef72b4e44bad45c01526f10e5feb2492b6dcc2c135a0e96504f6

data/CHANGELOG.md

@@ -1,5 +1,107 @@
 See full changelog for the OpenAPI schema (OAS) [here](https://github.com/plaid/plaid-openapi/blob/master/CHANGELOG.md).
 
+# 51.0.0
+- Updating to OAS 2020-09-14_1.740.1
+
+## Breaking changes in this version
+
+ - [BREAKING] `/processor/token/create`: the `processor` enum value `paynote` is replaced by `seamlessach` (SeamlessChex rebranded Paynote to Seamless ACH). Send `seamlessach` instead. The API still accepts `paynote` during a transition period, and processor tokens already issued under `paynote` keep working and do not need to be regenerated.
+ - [BREAKING] `/protect/compute`: the generic `cash-advance-onboarding-1.0` and `cash-advance-ongoing-1.0` models are removed. Use the client-scoped model issued for your client: `cash-advance-onboarding-<client>-1.0` or `cash-advance-ongoing-<client>-1.0`.
+ - [BREAKING] `/protect/cash_advance/repayment/create`: the repayment status `DELIVERED` is replaced by `PARTIAL_PAYMENT`, which indicates a payment was made but an outstanding balance remains. `amount_paid` is no longer required and is now nullable; it is required only when `status` is `REPAID` or `PARTIAL_PAYMENT`.
+ - [BREAKING] `/protect/cash_advance/decision/create`: `is_taken` moves out of the `cash_advance` object to the top level of the request, and the `cash_advance` object schema is renamed from `CashAdvanceDetails` to `CashAdvanceInfo`. A new required `advance_type` field (`FIRST` / `REPEAT`) and an optional non-negative `previous_advance_count` field are added. `is_taken` must be `false` when the decision is `DECLINED`; when `true`, both `client_advance_id` and `cash_advance` are required. `advance_type` is required only when `is_taken` is `true`.
+ - [BREAKING] `/protect/event/send`: `protect_session_id` is renamed to `device_session_id`, both at the top level and within `event`.
+ - [BREAKING] `/protect/compute`: the `sdk` model inputs object is renamed to `device`, its `sdk_session_id` field is renamed to `device_session_id`, and the `ProtectSDKModelInputs` schema is now `ProtectDeviceModelInputs`.
+
+## OpenAPI Schema Changes
+### 2020-09-14_1.740.1
+
+- Added the missing `PRODUCT_GENERATION_ERROR` enum value to `options.error_webhook_code` on `/sandbox/cra/servicing/simulate`. This change brings the OpenAPI specification in line with actual API behavior; the endpoint already accepted the value and emitted it on the resulting `CRA_REPORT_UPDATED` webhook.
+
+### 2020-09-14_1.740.0
+
+### 2020-09-14_1.739.0
+
+- Document `options.transactions.days_requested` on `/sandbox/public_token/create`, which controls how much transaction history the Sandbox Item is created with, matching `transactions.days_requested` on `/link/token/create`. The field was already present in the client libraries; only its documentation visibility changes.
+- Deprecate `options.transactions.start_date` and `options.transactions.end_date` on `/sandbox/public_token/create` in favor of `days_requested`, and remove them from the API reference. Both are still accepted and still have no effect on the history available on the Item.
+
+### 2020-09-14_1.738.0
+
+- [Breaking] SeamlessChex has rebranded Paynote to Seamless ACH. On `/processor/token/create`, the `processor` enum value `paynote` is replaced by `seamlessach`. Client libraries no longer expose `paynote` as an enum member, so upgrading to this version requires sending `seamlessach` instead. The API still accepts `paynote` during a transition period, so integrations pinned to an older client library continue to work, but the value is retired and will stop being accepted. Processor tokens already issued under `paynote` keep working and do not need to be regenerated.
+
+### 2020-09-14_1.737.2
+
+- Add `client_user_id` to the `/cra/report/get` response.
+
+### 2020-09-14_1.737.1
+
+- Internal changes only.
+
+### 2020-09-14_1.737.0
+
+- Document the `CRA_REPORT_UPDATED` webhook (`CRA_REPORT` type), fired when a subscribed CRA report is updated. The `successful_products`/`failed_products` fields indicate which products were updated, and `scope` indicates the data the report was computed over.
+
+### 2020-09-14_1.736.3
+
+### 2020-09-14_1.736.2
+
+- [Breaking] Remove the generic `cash-advance-onboarding-1.0` and `cash-advance-ongoing-1.0` models from `/protect/compute`. Cash advance scoring now requires the client-scoped model issued for your client, named `cash-advance-onboarding-<client>-1.0` or `cash-advance-ongoing-<client>-1.0`.
+
+### 2020-09-14_1.736.1
+
+- Hide `/beta/webhook_events/list` from public API docs until GA, and document its errors, mutually exclusive `cursor`/`start_time` behavior, and additional request/response examples. The request/response shapes are unchanged.
+
+### 2020-09-14_1.736.0
+
+- [Breaking] Make `amount_paid` nullable on `/protect/cash_advance/repayment/create`; it is now required only when `status` is `REPAID` or `PARTIAL_PAYMENT`.
+- Make `advance_type` optional on `/protect/cash_advance/decision/create`; it is now required only when `is_taken` is `true`.
+
+### 2020-09-14_1.735.0
+
+- [Breaking] Add the required `advance_type` field (`FIRST` / `REPEAT`) and the optional non-negative `previous_advance_count` field to the `/protect/cash_advance/decision/create` request body.
+- [Breaking] Replace the `DELIVERED` repayment status with `PARTIAL_PAYMENT` on `/protect/cash_advance/repayment/create`. `PARTIAL_PAYMENT` indicates a payment has been made but an outstanding balance remains.
+- [Breaking] Move `is_taken` out of the `cash_advance` object to the top level of the `/protect/cash_advance/decision/create` request. It must be `false` when the decision is `DECLINED`, and when `true` both `client_advance_id` and `cash_advance` are required.
+- [Breaking] Rename the `cash_advance` object schema from `CashAdvanceDetails` to `CashAdvanceInfo` on `/protect/cash_advance/decision/create`.
+
+### 2020-09-14_1.734.1
+
+- Add `kikoff_enterprise` to the `processor` enum on `/processor/token/create`, for creating processor tokens for the Kikoff Enterprise integration.
+
+### 2020-09-14_1.734.0
+
+- Make `device_data` optional and deprecated on `/protect/client/session/start`. The field remains accepted for backward compatibility.
+
+### 2020-09-14_1.733.0
+
+- Added a `running_balance` field to the Transaction object. It is the balance of the account after that transaction was applied, as reported by the financial institution, and is only present where the institution sends one.
+
+### 2020-09-14_1.732.0
+
+- internal changes only
+
+### 2020-09-14_1.731.0
+
+- Add the optional `holder_category` and `is_verified` fields to the counterparty on `/wallet/transaction/execute`. `holder_category` tells payee verification whether the counterparty is a person or a company, and `is_verified` lets you declare that you have already verified the counterparty so Plaid skips its own payee verification check. Both apply to GBP payouts and remain hidden from public documentation.
+- `payee_verification_status` on e-wallet transactions is now also populated for GBP payouts.
+
+### 2020-09-14_1.730.4
+
+- Clarify that client-specific Link session model requests can use a major-version alias and that `/protect/compute` responses return the exact minor version used.
+
+### 2020-09-14_1.730.3
+
+### 2020-09-14_1.730.2
+
+- Hide the `require_extracted_data` field on Protect Link-session model inputs from the public API reference. The request contract is unchanged.
+
+### 2020-09-14_1.730.1
+
+- Noted that `merchant_category_code` on the Transaction object is in beta.
+
+### 2020-09-14_1.730.0
+
+- [Breaking] Renamed the `protect_session_id` field in the request of the deprecated `/protect/event/send` to `device_session_id`, both at the top level and within `event`.
+- [Breaking] Renamed the `sdk` model inputs object in the request of `/protect/compute` to `device`, and its `sdk_session_id` field to `device_session_id`. The `ProtectSDKModelInputs` schema is now `ProtectDeviceModelInputs`.
+
 # 50.0.0
 - Updating to OAS 2020-09-14_1.729.1
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    plaid (50.0.0)
+    plaid (51.0.0)
       faraday (>= 1.0.1, < 3.0)
       faraday-multipart (>= 1.0.1, < 2.0)
 

data/Makefile

@@ -1,5 +1,5 @@
 # Ruby embeds the version in the generator where as others don't so it's not possible to cat for it.
-RUBY_PACKAGE_VERSION=50.0.0
+RUBY_PACKAGE_VERSION=51.0.0
 
 .PHONY: release
 release:

data/lib/plaid/api/plaid_api.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0
@@ -3284,7 +3284,7 @@ module Plaid
     end
 
     # List webhook events
-    # The `/beta/webhook_events/list` endpoint returns webhook events Plaid sent to the calling client within the last 7 days. Results are ordered by `sent_time` ascending and cursor paginated so clients can recover missed webhook deliveries and deduplicate on `webhook_message_id`.  Filtering is optional. When multiple filter fields are set (`webhook_types`, `webhook_codes`, `item_ids`, `delivery_statuses`), they are combined with AND across fields and OR within each array (for example, `webhook_types: [\"TRANSACTIONS\", \"ITEM\"]` matches either type).  Recommended pagination workflow:  1. First call: omit `cursor`, and optionally set `start_time` within the last 7 days (or    omit `start_time` to begin at the oldest retained event). 2. Subsequent calls: pass `next_cursor` as `cursor`. Do not send `start_time` with    `cursor` — the two fields are mutually exclusive. 3. Persist `next_cursor` even when `has_more` is `false`, then reuse it on the next poll so    you only receive events newer than what you have already seen. 4. If a stored cursor is older than the 7-day retention window, the API returns    `WEBHOOK_EVENTS_CURSOR_EXPIRED`; restart with a `start_time` within the last 7 days.    Events older than the retention window are no longer available.
+    # The `/beta/webhook_events/list` endpoint returns webhook events Plaid sent to the calling client within the last 7 days. Results are ordered by `sent_time` ascending and cursor paginated so clients can recover missed webhook deliveries and deduplicate on `webhook_message_id`.  Filtering is optional. When multiple filter fields are set (`webhook_types`, `webhook_codes`, `item_ids`, `delivery_statuses`), they are combined with AND across fields and OR within each array (for example, `webhook_types: [\"ITEM\", \"AUTH\"]` matches either type).  Recommended pagination workflow:  1. First call: omit `cursor`, and optionally set `start_time` within the last 7 days (or    omit `start_time` to begin at the oldest retained event). 2. Subsequent calls: pass `next_cursor` as `cursor`. Do not send `start_time` with    `cursor` — the two fields are mutually exclusive. Sending both returns `INVALID_FIELD`. 3. Persist `next_cursor` even when `has_more` is `false`, then reuse it on the next poll so    you only receive events newer than what you have already seen. 4. If a stored cursor is older than the 7-day retention window, the API returns    `WEBHOOK_EVENTS_CURSOR_EXPIRED`; restart with a `start_time` within the last 7 days.    Events older than the retention window are no longer available.  Errors:  `WEBHOOK_EVENTS_START_TIME_OUT_OF_RANGE` (400) is returned when `start_time` is earlier than the 7-day retention window. Retry with a `start_time` within the last 7 days, or omit it.  `WEBHOOK_EVENTS_CURSOR_EXPIRED` (400) is returned when the cursor's position is older than the 7-day retention window and can no longer be resolved. Restart pagination with a `start_time` within the last 7 days.  `INVALID_FIELD` (400) is returned when `cursor` is not a properly formatted string, when both `cursor` and `start_time` are provided, or when the request is otherwise invalid.
     # @param beta_webhook_events_list_request [BetaWebhookEventsListRequest] 
     # @param [Hash] opts the optional parameters
     # @return [BetaWebhookEventsListResponse]
@@ -3294,7 +3294,7 @@ module Plaid
     end
 
     # List webhook events
-    # The `/beta/webhook_events/list` endpoint returns webhook events Plaid sent to the calling client within the last 7 days. Results are ordered by `sent_time` ascending and cursor paginated so clients can recover missed webhook deliveries and deduplicate on `webhook_message_id`.  Filtering is optional. When multiple filter fields are set (`webhook_types`, `webhook_codes`, `item_ids`, `delivery_statuses`), they are combined with AND across fields and OR within each array (for example, `webhook_types: [\"TRANSACTIONS\", \"ITEM\"]` matches either type).  Recommended pagination workflow:  1. First call: omit `cursor`, and optionally set `start_time` within the last 7 days (or    omit `start_time` to begin at the oldest retained event). 2. Subsequent calls: pass `next_cursor` as `cursor`. Do not send `start_time` with    `cursor` — the two fields are mutually exclusive. 3. Persist `next_cursor` even when `has_more` is `false`, then reuse it on the next poll so    you only receive events newer than what you have already seen. 4. If a stored cursor is older than the 7-day retention window, the API returns    `WEBHOOK_EVENTS_CURSOR_EXPIRED`; restart with a `start_time` within the last 7 days.    Events older than the retention window are no longer available.
+    # The `/beta/webhook_events/list` endpoint returns webhook events Plaid sent to the calling client within the last 7 days. Results are ordered by `sent_time` ascending and cursor paginated so clients can recover missed webhook deliveries and deduplicate on `webhook_message_id`.  Filtering is optional. When multiple filter fields are set (`webhook_types`, `webhook_codes`, `item_ids`, `delivery_statuses`), they are combined with AND across fields and OR within each array (for example, `webhook_types: [\"ITEM\", \"AUTH\"]` matches either type).  Recommended pagination workflow:  1. First call: omit `cursor`, and optionally set `start_time` within the last 7 days (or    omit `start_time` to begin at the oldest retained event). 2. Subsequent calls: pass `next_cursor` as `cursor`. Do not send `start_time` with    `cursor` — the two fields are mutually exclusive. Sending both returns `INVALID_FIELD`. 3. Persist `next_cursor` even when `has_more` is `false`, then reuse it on the next poll so    you only receive events newer than what you have already seen. 4. If a stored cursor is older than the 7-day retention window, the API returns    `WEBHOOK_EVENTS_CURSOR_EXPIRED`; restart with a `start_time` within the last 7 days.    Events older than the retention window are no longer available.  Errors:  `WEBHOOK_EVENTS_START_TIME_OUT_OF_RANGE` (400) is returned when `start_time` is earlier than the 7-day retention window. Retry with a `start_time` within the last 7 days, or omit it.  `WEBHOOK_EVENTS_CURSOR_EXPIRED` (400) is returned when the cursor's position is older than the 7-day retention window and can no longer be resolved. Restart pagination with a `start_time` within the last 7 days.  `INVALID_FIELD` (400) is returned when `cursor` is not a properly formatted string, when both `cursor` and `start_time` are provided, or when the request is otherwise invalid.
     # @param beta_webhook_events_list_request [BetaWebhookEventsListRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(BetaWebhookEventsListResponse, Integer, Hash)>] BetaWebhookEventsListResponse data, response status code and response headers
@@ -4983,8 +4983,8 @@ module Plaid
       return data, status_code, headers
     end
 
-    # Retrieve a Monitoring Insights Report
-    # This endpoint allows you to retrieve a Cash Flow Updates report by passing in the `user_id` referred to in the webhook you received.
+    # (Legacy) Retrieve a Cash Flow Updates report
+    # This endpoint allows you to retrieve a Cash Flow Updates report by passing in the `user_id` referred to in the webhook you received. This endpoint is part of the legacy Cash Flow Updates product and is available only to integrations already using it. CRA Servicing has no direct equivalent; other integrations should handle the `CRA_REPORT_UPDATED` webhook and pass its `report_id` to the relevant product `/get` endpoint, such as `/cra/check_report/base_report/get`.
     # @param cra_monitoring_insights_get_request [CraMonitoringInsightsGetRequest] 
     # @param [Hash] opts the optional parameters
     # @return [CraMonitoringInsightsGetResponse]
@@ -4993,8 +4993,8 @@ module Plaid
       data
     end
 
-    # Retrieve a Monitoring Insights Report
-    # This endpoint allows you to retrieve a Cash Flow Updates report by passing in the &#x60;user_id&#x60; referred to in the webhook you received.
+    # (Legacy) Retrieve a Cash Flow Updates report
+    # This endpoint allows you to retrieve a Cash Flow Updates report by passing in the &#x60;user_id&#x60; referred to in the webhook you received. This endpoint is part of the legacy Cash Flow Updates product and is available only to integrations already using it. CRA Servicing has no direct equivalent; other integrations should handle the &#x60;CRA_REPORT_UPDATED&#x60; webhook and pass its &#x60;report_id&#x60; to the relevant product &#x60;/get&#x60; endpoint, such as &#x60;/cra/check_report/base_report/get&#x60;.
     # @param cra_monitoring_insights_get_request [CraMonitoringInsightsGetRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(CraMonitoringInsightsGetResponse, Integer, Hash)>] CraMonitoringInsightsGetResponse data, response status code and response headers
@@ -5051,8 +5051,8 @@ module Plaid
       return data, status_code, headers
     end
 
-    # Subscribe to Monitoring Insights
-    # This endpoint allows you to subscribe to insights for a user's linked CRA Item, which are updated between one and four times per day (best-effort). In the current Cash Flow Updates beta experience, only one Item per user may be subscribed for monitoring updates.
+    # (Legacy) Subscribe to Cash Flow Updates
+    # This endpoint allows you to subscribe to insights for a user's linked CRA Item, which are updated between one and four times per day (best-effort). Only one Item per user may be subscribed. This endpoint is part of the legacy Cash Flow Updates product and is available only to integrations already using it; other integrations should use `/cra/servicing/subscription/create` instead.
     # @param cra_monitoring_insights_subscribe_request [CraMonitoringInsightsSubscribeRequest] 
     # @param [Hash] opts the optional parameters
     # @return [CraMonitoringInsightsSubscribeResponse]
@@ -5061,8 +5061,8 @@ module Plaid
       data
     end
 
-    # Subscribe to Monitoring Insights
-    # This endpoint allows you to subscribe to insights for a user&#39;s linked CRA Item, which are updated between one and four times per day (best-effort). In the current Cash Flow Updates beta experience, only one Item per user may be subscribed for monitoring updates.
+    # (Legacy) Subscribe to Cash Flow Updates
+    # This endpoint allows you to subscribe to insights for a user&#39;s linked CRA Item, which are updated between one and four times per day (best-effort). Only one Item per user may be subscribed. This endpoint is part of the legacy Cash Flow Updates product and is available only to integrations already using it; other integrations should use &#x60;/cra/servicing/subscription/create&#x60; instead.
     # @param cra_monitoring_insights_subscribe_request [CraMonitoringInsightsSubscribeRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(CraMonitoringInsightsSubscribeResponse, Integer, Hash)>] CraMonitoringInsightsSubscribeResponse data, response status code and response headers
@@ -5119,8 +5119,8 @@ module Plaid
       return data, status_code, headers
     end
 
-    # Unsubscribe from Monitoring Insights
-    # This endpoint allows you to unsubscribe from previously subscribed Monitoring Insights.
+    # (Legacy) Unsubscribe from Cash Flow Updates
+    # This endpoint allows you to remove a subscription created by `/cra/monitoring_insights/subscribe`. This endpoint is part of the legacy Cash Flow Updates product and is available only to integrations already using it; other integrations should use `/cra/servicing/subscription/delete` instead.
     # @param cra_monitoring_insights_unsubscribe_request [CraMonitoringInsightsUnsubscribeRequest] 
     # @param [Hash] opts the optional parameters
     # @return [CraMonitoringInsightsUnsubscribeResponse]
@@ -5129,8 +5129,8 @@ module Plaid
       data
     end
 
-    # Unsubscribe from Monitoring Insights
-    # This endpoint allows you to unsubscribe from previously subscribed Monitoring Insights.
+    # (Legacy) Unsubscribe from Cash Flow Updates
+    # This endpoint allows you to remove a subscription created by &#x60;/cra/monitoring_insights/subscribe&#x60;. This endpoint is part of the legacy Cash Flow Updates product and is available only to integrations already using it; other integrations should use &#x60;/cra/servicing/subscription/delete&#x60; instead.
     # @param cra_monitoring_insights_unsubscribe_request [CraMonitoringInsightsUnsubscribeRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(CraMonitoringInsightsUnsubscribeResponse, Integer, Hash)>] CraMonitoringInsightsUnsubscribeResponse data, response status code and response headers
@@ -10542,7 +10542,7 @@ module Plaid
     end
 
     # Retrieve Liabilities data
-    # The `/liabilities/get` endpoint returns various details about an Item with loan or credit accounts. Liabilities data is available primarily for US financial institutions, with some limited coverage of Canadian institutions. Supported account types are account type `credit` with account subtype `charge card`, `credit card`, or `paypal`; and account type `loan` with account subtype `auto`, `commercial`, `commercial line of credit`, `consumer`, `home equity`, `home equity loan`, `installment`, `line of credit`, `loan`, `mortgage`, or `student`. To limit accounts listed in Link to types and subtypes supported by Liabilities, you can use the `account_filters` parameter when [creating a Link token](https://plaid.com/docs/api/link/#linktokencreate).  The types of information returned by Liabilities can include balances and due dates, loan terms, and account details such as original loan amount and guarantor. Data is refreshed approximately once per day; the latest data can be retrieved by calling `/liabilities/get`.
+    # The `/liabilities/get` endpoint returns various details about an Item with loan or credit accounts. Liabilities data is available primarily for US financial institutions, with some limited coverage of Canadian institutions. Currently supported account types are account type `credit` with account subtype `credit card` or `paypal`, and account type `loan` with account subtype `student` or `mortgage`. To limit accounts listed in Link to types and subtypes supported by Liabilities, you can use the `account_filters` parameter when [creating a Link token](https://plaid.com/docs/api/link/#linktokencreate).  The types of information returned by Liabilities can include balances and due dates, loan terms, and account details such as original loan amount and guarantor. Data is refreshed approximately once per day; the latest data can be retrieved by calling `/liabilities/get`.
     # @param liabilities_get_request [LiabilitiesGetRequest] 
     # @param [Hash] opts the optional parameters
     # @return [LiabilitiesGetResponse]
@@ -10552,7 +10552,7 @@ module Plaid
     end
 
     # Retrieve Liabilities data
-    # The &#x60;/liabilities/get&#x60; endpoint returns various details about an Item with loan or credit accounts. Liabilities data is available primarily for US financial institutions, with some limited coverage of Canadian institutions. Supported account types are account type &#x60;credit&#x60; with account subtype &#x60;charge card&#x60;, &#x60;credit card&#x60;, or &#x60;paypal&#x60;; and account type &#x60;loan&#x60; with account subtype &#x60;auto&#x60;, &#x60;commercial&#x60;, &#x60;commercial line of credit&#x60;, &#x60;consumer&#x60;, &#x60;home equity&#x60;, &#x60;home equity loan&#x60;, &#x60;installment&#x60;, &#x60;line of credit&#x60;, &#x60;loan&#x60;, &#x60;mortgage&#x60;, or &#x60;student&#x60;. To limit accounts listed in Link to types and subtypes supported by Liabilities, you can use the &#x60;account_filters&#x60; parameter when [creating a Link token](https://plaid.com/docs/api/link/#linktokencreate).  The types of information returned by Liabilities can include balances and due dates, loan terms, and account details such as original loan amount and guarantor. Data is refreshed approximately once per day; the latest data can be retrieved by calling &#x60;/liabilities/get&#x60;.
+    # The &#x60;/liabilities/get&#x60; endpoint returns various details about an Item with loan or credit accounts. Liabilities data is available primarily for US financial institutions, with some limited coverage of Canadian institutions. Currently supported account types are account type &#x60;credit&#x60; with account subtype &#x60;credit card&#x60; or &#x60;paypal&#x60;, and account type &#x60;loan&#x60; with account subtype &#x60;student&#x60; or &#x60;mortgage&#x60;. To limit accounts listed in Link to types and subtypes supported by Liabilities, you can use the &#x60;account_filters&#x60; parameter when [creating a Link token](https://plaid.com/docs/api/link/#linktokencreate).  The types of information returned by Liabilities can include balances and due dates, loan terms, and account details such as original loan amount and guarantor. Data is refreshed approximately once per day; the latest data can be retrieved by calling &#x60;/liabilities/get&#x60;.
     # @param liabilities_get_request [LiabilitiesGetRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(LiabilitiesGetResponse, Integer, Hash)>] LiabilitiesGetResponse data, response status code and response headers
@@ -14350,7 +14350,7 @@ module Plaid
     end
 
     # Compute Protect Trust Index scores and subscores
-    # Compute a Protect Trust Index score for a user. The model selected determines what is scored and what additional fields the response contains. For example, `ti-link-session-2.0` scores a completed Link session for fraud risk; `cash-advance-onboarding-1.0` scores repayment risk for a first-time cash advance and additionally populates per-amount-bucket subscores. Cash-advance models require that the user have a Plaid Item with Transactions enabled, or an Assets Report, before scoring.  The endpoint returns HTTP 400 with `error_type` = `INVALID_REQUEST` and `error_code` = `FAILED_PRECONDITION` when a required precondition is not met: for link-session models, when the Link session has not completed; for cash-advance models, when the user has not successfully linked any Item.
+    # Compute a Protect Trust Index score for a user. The model selected determines what is scored and what additional fields the response contains. For example, `ti-link-session-3-<client>` scores a completed Link session for fraud risk; `cash-advance-onboarding-<client>-1.0` scores repayment risk for a first-time cash advance and `cash-advance-ongoing-<client>-1.0` scores subsequent advances, both additionally populating per-amount-bucket subscores. Cash-advance models require that the user have a Plaid Item with Transactions enabled, or an Assets Report, before scoring.  The endpoint returns HTTP 400 with `error_type` = `INVALID_REQUEST` and `error_code` = `FAILED_PRECONDITION` when a required precondition is not met: for link-session models, when the Link session has not completed; for cash-advance models, when the user has not successfully linked any Item.
     # @param protect_compute_request [ProtectComputeRequest] 
     # @param [Hash] opts the optional parameters
     # @return [ProtectComputeResponse]
@@ -14360,7 +14360,7 @@ module Plaid
     end
 
     # Compute Protect Trust Index scores and subscores
-    # Compute a Protect Trust Index score for a user. The model selected determines what is scored and what additional fields the response contains. For example, &#x60;ti-link-session-2.0&#x60; scores a completed Link session for fraud risk; &#x60;cash-advance-onboarding-1.0&#x60; scores repayment risk for a first-time cash advance and additionally populates per-amount-bucket subscores. Cash-advance models require that the user have a Plaid Item with Transactions enabled, or an Assets Report, before scoring.  The endpoint returns HTTP 400 with &#x60;error_type&#x60; &#x3D; &#x60;INVALID_REQUEST&#x60; and &#x60;error_code&#x60; &#x3D; &#x60;FAILED_PRECONDITION&#x60; when a required precondition is not met: for link-session models, when the Link session has not completed; for cash-advance models, when the user has not successfully linked any Item.
+    # Compute a Protect Trust Index score for a user. The model selected determines what is scored and what additional fields the response contains. For example, &#x60;ti-link-session-3-&lt;client&gt;&#x60; scores a completed Link session for fraud risk; &#x60;cash-advance-onboarding-&lt;client&gt;-1.0&#x60; scores repayment risk for a first-time cash advance and &#x60;cash-advance-ongoing-&lt;client&gt;-1.0&#x60; scores subsequent advances, both additionally populating per-amount-bucket subscores. Cash-advance models require that the user have a Plaid Item with Transactions enabled, or an Assets Report, before scoring.  The endpoint returns HTTP 400 with &#x60;error_type&#x60; &#x3D; &#x60;INVALID_REQUEST&#x60; and &#x60;error_code&#x60; &#x3D; &#x60;FAILED_PRECONDITION&#x60; when a required precondition is not met: for link-session models, when the Link session has not completed; for cash-advance models, when the user has not successfully linked any Item.
     # @param protect_compute_request [ProtectComputeRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(ProtectComputeResponse, Integer, Hash)>] ProtectComputeResponse data, response status code and response headers
@@ -14554,7 +14554,7 @@ module Plaid
     end
 
     # Create a Protect report
-    # Use this endpoint to create a Protect report to document fraud incidents, investigation outcomes, or other risk events. This endpoint allows you to report various types of incidents including account takeovers, identity fraud, unauthorized transactions, and other security events. The reported data helps improve fraud detection models and provides valuable feedback to enhance the overall security of the Plaid network. Reports can be created for confirmed incidents that have been fully investigated, or for suspected incidents that require further review. You can associate reports with specific users, sessions, or transactions to provide comprehensive context about the incident. Each report must include `user_id`, or an `incident_event` with at least one supported identifier: `link_session_id`, `idv_session_id`, `protect_event_id`, `signal_client_transaction_id`, or `access_token`. Context fields such as `internal_reference`, `time`, `amount`, and `bank_account` do not satisfy this identifier requirement.
+    # Use this endpoint to create a Protect report to document fraud incidents, investigation outcomes, or other risk events. This endpoint allows you to report various types of incidents including account takeovers, identity fraud, unauthorized transactions, and other security events. The reported data helps improve fraud detection models and provides valuable feedback to enhance the overall security of the Plaid network.  Reports can be created for confirmed incidents that have been fully investigated, or for suspected incidents that require further review. You can associate reports with specific users, sessions, or transactions to provide comprehensive context about the incident. Each report must include `user_id`, or an `incident_event` with at least one supported identifier: `link_session_id`, `idv_session_id`, `protect_event_id`, `signal_client_transaction_id`, or `access_token`. Context fields such as `internal_reference`, `time`, `amount`, and `bank_account` do not satisfy this identifier requirement.
     # @param protect_report_create_request [ProtectReportCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [ProtectReportCreateResponse]
@@ -14564,7 +14564,7 @@ module Plaid
     end
 
     # Create a Protect report
-    # Use this endpoint to create a Protect report to document fraud incidents, investigation outcomes, or other risk events. This endpoint allows you to report various types of incidents including account takeovers, identity fraud, unauthorized transactions, and other security events. The reported data helps improve fraud detection models and provides valuable feedback to enhance the overall security of the Plaid network. Reports can be created for confirmed incidents that have been fully investigated, or for suspected incidents that require further review. You can associate reports with specific users, sessions, or transactions to provide comprehensive context about the incident. Each report must include &#x60;user_id&#x60;, or an &#x60;incident_event&#x60; with at least one supported identifier: &#x60;link_session_id&#x60;, &#x60;idv_session_id&#x60;, &#x60;protect_event_id&#x60;, &#x60;signal_client_transaction_id&#x60;, or &#x60;access_token&#x60;. Context fields such as &#x60;internal_reference&#x60;, &#x60;time&#x60;, &#x60;amount&#x60;, and &#x60;bank_account&#x60; do not satisfy this identifier requirement.
+    # Use this endpoint to create a Protect report to document fraud incidents, investigation outcomes, or other risk events. This endpoint allows you to report various types of incidents including account takeovers, identity fraud, unauthorized transactions, and other security events. The reported data helps improve fraud detection models and provides valuable feedback to enhance the overall security of the Plaid network.  Reports can be created for confirmed incidents that have been fully investigated, or for suspected incidents that require further review. You can associate reports with specific users, sessions, or transactions to provide comprehensive context about the incident. Each report must include &#x60;user_id&#x60;, or an &#x60;incident_event&#x60; with at least one supported identifier: &#x60;link_session_id&#x60;, &#x60;idv_session_id&#x60;, &#x60;protect_event_id&#x60;, &#x60;signal_client_transaction_id&#x60;, or &#x60;access_token&#x60;. Context fields such as &#x60;internal_reference&#x60;, &#x60;time&#x60;, &#x60;amount&#x60;, and &#x60;bank_account&#x60; do not satisfy this identifier requirement.
     # @param protect_report_create_request [ProtectReportCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(ProtectReportCreateResponse, Integer, Hash)>] ProtectReportCreateResponse data, response status code and response headers
@@ -14894,7 +14894,7 @@ module Plaid
     end
 
     # Trigger an update for Cash Flow Updates
-    # Use the `/sandbox/cra/cashflow_updates/update` endpoint to manually trigger an update for Cash Flow Updates (Monitoring) in the Sandbox environment.
+    # Use the `/sandbox/cra/cashflow_updates/update` endpoint to manually trigger an update for the legacy Cash Flow Updates product in the Sandbox environment. To simulate a report generation for a CRA Servicing subscription, use `/sandbox/cra/servicing/simulate`.
     # @param sandbox_cra_cashflow_updates_update_request [SandboxCraCashflowUpdatesUpdateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [SandboxCraCashflowUpdatesUpdateResponse]
@@ -14904,7 +14904,7 @@ module Plaid
     end
 
     # Trigger an update for Cash Flow Updates
-    # Use the &#x60;/sandbox/cra/cashflow_updates/update&#x60; endpoint to manually trigger an update for Cash Flow Updates (Monitoring) in the Sandbox environment.
+    # Use the &#x60;/sandbox/cra/cashflow_updates/update&#x60; endpoint to manually trigger an update for the legacy Cash Flow Updates product in the Sandbox environment. To simulate a report generation for a CRA Servicing subscription, use &#x60;/sandbox/cra/servicing/simulate&#x60;.
     # @param sandbox_cra_cashflow_updates_update_request [SandboxCraCashflowUpdatesUpdateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(SandboxCraCashflowUpdatesUpdateResponse, Integer, Hash)>] SandboxCraCashflowUpdatesUpdateResponse data, response status code and response headers
@@ -20538,7 +20538,7 @@ module Plaid
     end
 
     # Create a refund
-    # Use the `/transfer/refund/create` endpoint to create a refund for a transfer. A transfer can be refunded if the transfer was initiated in the past 180 days.  Refunds come out of the available balance of the ledger used for the original debit transfer. If there are not enough funds in the available balance to cover the refund amount, the refund will be rejected. You can create a refund at any time. Plaid does not impose any hold time on refunds.  A refund can still be issued even if the Item's `access_token` is no longer valid (e.g. if the user revoked OAuth consent or the Item was deleted via `/item/remove`), as long as the account and routing number pair used to make the original transaction is still valid. A refund cannot be issued if the Item has an [invalidated TAN](https://plaid.com/docs/auth/#tokenized-account-numbers), which can occur at Chase or PNC.
+    # Use the `/transfer/refund/create` endpoint to create a refund for a transfer. A transfer can be refunded if the transfer was initiated in the past 180 days.  Refunds come out of the available balance of the ledger used for the original debit transfer. If there are not enough funds in the available balance to cover the refund amount, the refund will be rejected. Plaid does not impose a hold time before a refund can be created; you do not need to wait for the original transfer to settle.  A refund can still be issued even if the Item's `access_token` is no longer valid (e.g. if the user revoked OAuth consent or the Item was deleted via `/item/remove`), as long as the account and routing number pair used to make the original transaction is still valid. A refund cannot be issued if the Item has an [invalidated TAN](https://plaid.com/docs/auth/#tokenized-account-numbers), which can occur at Chase or PNC.
     # @param transfer_refund_create_request [TransferRefundCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [TransferRefundCreateResponse]
@@ -20548,7 +20548,7 @@ module Plaid
     end
 
     # Create a refund
-    # Use the &#x60;/transfer/refund/create&#x60; endpoint to create a refund for a transfer. A transfer can be refunded if the transfer was initiated in the past 180 days.  Refunds come out of the available balance of the ledger used for the original debit transfer. If there are not enough funds in the available balance to cover the refund amount, the refund will be rejected. You can create a refund at any time. Plaid does not impose any hold time on refunds.  A refund can still be issued even if the Item&#39;s &#x60;access_token&#x60; is no longer valid (e.g. if the user revoked OAuth consent or the Item was deleted via &#x60;/item/remove&#x60;), as long as the account and routing number pair used to make the original transaction is still valid. A refund cannot be issued if the Item has an [invalidated TAN](https://plaid.com/docs/auth/#tokenized-account-numbers), which can occur at Chase or PNC.
+    # Use the &#x60;/transfer/refund/create&#x60; endpoint to create a refund for a transfer. A transfer can be refunded if the transfer was initiated in the past 180 days.  Refunds come out of the available balance of the ledger used for the original debit transfer. If there are not enough funds in the available balance to cover the refund amount, the refund will be rejected. Plaid does not impose a hold time before a refund can be created; you do not need to wait for the original transfer to settle.  A refund can still be issued even if the Item&#39;s &#x60;access_token&#x60; is no longer valid (e.g. if the user revoked OAuth consent or the Item was deleted via &#x60;/item/remove&#x60;), as long as the account and routing number pair used to make the original transaction is still valid. A refund cannot be issued if the Item has an [invalidated TAN](https://plaid.com/docs/auth/#tokenized-account-numbers), which can occur at Chase or PNC.
     # @param transfer_refund_create_request [TransferRefundCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(TransferRefundCreateResponse, Integer, Hash)>] TransferRefundCreateResponse data, response status code and response headers
@@ -21567,7 +21567,7 @@ module Plaid
     end
 
     # Remove Items from a User
-    # Removes specific Items associated with a user. It is equivalent to calling `/item/remove` on each Item individually, but supports use cases (such as Plaid Check) where access tokens are not available. All specified Items must belong to the user or the entire operation fails. Similar to `/item/remove`, this deletes Item product data and terminates billing on the Item's products. Once removed, Items cannot be reconnected without going through Link again. This endpoint is not intended to remove all data for a user, as it will only remove Items and no other data for the user. If the user has any user-based recurring subscription products (Financial Management, Plaid Protect, or CRA Cash Flow Updates) and is deleting their account with your product, also call `/user/products/terminate` to end those subscriptions; per-Item billing is already terminated by this endpoint. For a user initiated data deletion request, see the [Consumer Service Center](https://plaid.com/check/consumer-service-center/) to revoke access to data.
+    # Removes specific Items associated with a user. It is equivalent to calling `/item/remove` on each Item individually, but supports use cases (such as Plaid Check) where access tokens are not available. All specified Items must belong to the user or the entire operation fails. Similar to `/item/remove`, this deletes Item product data and terminates billing on the Item's products. Once removed, Items cannot be reconnected without going through Link again. This endpoint is not intended to remove all data for a user, as it will only remove Items and no other data for the user. If the user has any user-based recurring subscription products (Financial Management, Plaid Protect, or CRA Servicing) and is deleting their account with your product, also call `/user/products/terminate` to end those subscriptions; per-Item billing is already terminated by this endpoint. For a user initiated data deletion request, see the [Consumer Service Center](https://plaid.com/check/consumer-service-center/) to revoke access to data.
     # @param user_items_remove_request [UserItemsRemoveRequest] 
     # @param [Hash] opts the optional parameters
     # @return [UserItemsRemoveResponse]
@@ -21577,7 +21577,7 @@ module Plaid
     end
 
     # Remove Items from a User
-    # Removes specific Items associated with a user. It is equivalent to calling &#x60;/item/remove&#x60; on each Item individually, but supports use cases (such as Plaid Check) where access tokens are not available. All specified Items must belong to the user or the entire operation fails. Similar to &#x60;/item/remove&#x60;, this deletes Item product data and terminates billing on the Item&#39;s products. Once removed, Items cannot be reconnected without going through Link again. This endpoint is not intended to remove all data for a user, as it will only remove Items and no other data for the user. If the user has any user-based recurring subscription products (Financial Management, Plaid Protect, or CRA Cash Flow Updates) and is deleting their account with your product, also call &#x60;/user/products/terminate&#x60; to end those subscriptions; per-Item billing is already terminated by this endpoint. For a user initiated data deletion request, see the [Consumer Service Center](https://plaid.com/check/consumer-service-center/) to revoke access to data.
+    # Removes specific Items associated with a user. It is equivalent to calling &#x60;/item/remove&#x60; on each Item individually, but supports use cases (such as Plaid Check) where access tokens are not available. All specified Items must belong to the user or the entire operation fails. Similar to &#x60;/item/remove&#x60;, this deletes Item product data and terminates billing on the Item&#39;s products. Once removed, Items cannot be reconnected without going through Link again. This endpoint is not intended to remove all data for a user, as it will only remove Items and no other data for the user. If the user has any user-based recurring subscription products (Financial Management, Plaid Protect, or CRA Servicing) and is deleting their account with your product, also call &#x60;/user/products/terminate&#x60; to end those subscriptions; per-Item billing is already terminated by this endpoint. For a user initiated data deletion request, see the [Consumer Service Center](https://plaid.com/check/consumer-service-center/) to revoke access to data.
     # @param user_items_remove_request [UserItemsRemoveRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(UserItemsRemoveResponse, Integer, Hash)>] UserItemsRemoveResponse data, response status code and response headers
@@ -21635,7 +21635,7 @@ module Plaid
     end
 
     # Terminate user-based products
-    # Terminates user-based recurring subscription bundles or products (Financial Management, Plaid Protect, and CRA Cash Flow Updates) associated with a `user_id`. After you call this endpoint, the user will no longer be billed for these products. For CRA Monitoring, the subscription is canceled but historical data remains available for future report requests.
+    # Terminates user-based recurring subscription bundles or products (Financial Management, Plaid Protect, and CRA Servicing) associated with a `user_id`. After you call this endpoint, the user will no longer be billed for these products. For CRA Servicing, the subscription is canceled but historical data remains available for future report requests.
     # @param user_products_terminate_request [UserProductsTerminateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [UserProductsTerminateResponse]
@@ -21645,7 +21645,7 @@ module Plaid
     end
 
     # Terminate user-based products
-    # Terminates user-based recurring subscription bundles or products (Financial Management, Plaid Protect, and CRA Cash Flow Updates) associated with a &#x60;user_id&#x60;. After you call this endpoint, the user will no longer be billed for these products. For CRA Monitoring, the subscription is canceled but historical data remains available for future report requests.
+    # Terminates user-based recurring subscription bundles or products (Financial Management, Plaid Protect, and CRA Servicing) associated with a &#x60;user_id&#x60;. After you call this endpoint, the user will no longer be billed for these products. For CRA Servicing, the subscription is canceled but historical data remains available for future report requests.
     # @param user_products_terminate_request [UserProductsTerminateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(UserProductsTerminateResponse, Integer, Hash)>] UserProductsTerminateResponse data, response status code and response headers

data/lib/plaid/api_client.rb

@@ -7,7 +7,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0
@@ -41,7 +41,7 @@ module Plaid
     # @option config [Configuration] Configuration for initializing the object, default to Configuration.default
     def initialize(config = Configuration.default)
       @config = config
-      @user_agent = "Plaid Ruby v50.0.0"
+      @user_agent = "Plaid Ruby v51.0.0"
       @default_headers = {
         'Content-Type' => 'application/json',
         'User-Agent' => @user_agent,

data/lib/plaid/api_error.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/configuration.rb

@@ -7,7 +7,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/aamva_analysis.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/aamva_detailed_match_result.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/aamva_match_result.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_access.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_assets.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_balance.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_base.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_base_nullable.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_filter.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_filters_response.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_holder_category.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_identity.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_identity_all_of.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_identity_document_upload.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_identity_document_upload_all_of.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_identity_match_score.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0

data/lib/plaid/models/account_identity_match_score_all_of.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.729.1
+The version of the OpenAPI document: 2020-09-14_1.740.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0