plaid 42.0.0 → 43.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 571ee5b17b9030293b15149428809a3c82c6133387a30ce0bb4653e204114d86
-  data.tar.gz: 579f724a21cb742c44679937daa8a3e4b40e35b53b89baeafaaff5d0791dbebd
+  metadata.gz: a18a58b0999a91c77587ffa61ff36afca269249d433d23e1a132012e95a50016
+  data.tar.gz: 900e05a33429ca0b35feb1209dc130082a4869fef33438996d978510d7a55946
 SHA512:
-  metadata.gz: 1cab1fe2ab942e9066b152c1def164c53dac607b643e939ae5132ba108138797db8b743054c59929cc14ebdbf52019f97f99cad51ca82fb7cf1d6dc4c3927c9a
-  data.tar.gz: 7a38f17797ffe687d92e6a8a78de8d2c480e6d7d007d918b03a7a2035ec7cc361547856ab0b8933a783fc0b85e05853dbd2e4f90f00d2bbef71f8d95e9e3a4bd
+  metadata.gz: 035c9a2818134086c1d837a488d0a1ac85e03e7ad458b0501557bccab8c88b3ec5d96f645a0596e37873aecc8db1f1d1868442af572408374dd6812286c89238
+  data.tar.gz: ced2be66090a4219758fa803f7f61444e124184d172535a8c2749d4627bf5a0090cc41664b9dafcb4e8213c92619d992b85f6c5109a1218819f2f6463fb598af

data/CHANGELOG.md

@@ -1,8 +1,65 @@
 See full changelog for the OpenAPI schema (OAS) [here](https://github.com/plaid/plaid-openapi/blob/master/CHANGELOG.md).
 
+# 43.0.0
+- Updating to OAS 2020-09-14_1.658.0
+
+## Breaking changes in this version
+
+- [BREAKING] To improve consistency and resolve a bug in a third-party client library, changed `MonitoringConsumerReportPermissiblePurpose` schema object title from `ConsumerReportPermissiblePurpose` to `MonitoringConsumerReportPermissiblePurpose`. This may be a breaking change for certain client libraries.
+
+## OpenAPI Schema Changes
+### 2020-09-14_1.658.0
+- (beta) Add `user_id` field to `/session/token/create` request.
+- [BREAKING for Go] (beta) Make `user` object optional in `/session/token/create` if `user_id` is included.
+
+### 2020-09-14_1.657.0
+Add Add `subtype` property to the `Security` model.
+
+### 2020-09-14_1.656.1
+- Renamed `protect_sdk_session_id` field in the request of `/protect/event/send` to `protect_session_id` for consistency across endpoints.
+
+### 2020-09-14_1.656.0
+- Added `aamva_verification` object in the responses of `documentary_verification.documents[].analysis`. This impacts the following endpoints: 
+    - `identity_verification/create`
+    - `identity_verification/get`
+    - `identity_verification/list`
+    - `identity_verification/retry`
+
+### 2020-09-14_1.655.0
+- Add `max_amount` and `iso_currency_code` to `rfp` in `/transfer/capabilitied/get` response
+
+### 2020-09-14_1.654.0
+- [BREAKING] To improve consistency and resolve a bug in a third-party client library, changed `MonitoringConsumerReportPermissiblePurpose` schema object title from `ConsumerReportPermissiblePurpose` to `MonitoringConsumerReportPermissiblePurpose`. This may be a breaking change for certain client libraries.
+
+### 2020-09-14_1.653.0
+- (beta) Add optional `user_id` field to `identity_verification/create` and `identity_verification/list` requests. When `user_id` is present during creation and `client_user_id` is not, the `client_user_id` from the associated user will be set on the created identity verification. If `user_id` is present during creation, the `user` object may not also be present. Modifying user data should be done via the `user/update` endpoint.
+- [BREAKING for Go] (beta) Make `client_user_id` optional in `identity_verification/list` if `user_id` is included.
+- (beta) Add nullable `user_id` to the response of all of the identity verification endpoints:
+   - `identity_verification/create`
+   - `identity_verification/get`
+   - `identity_verification/list`
+   - `identity_verification/retry`
+
+### 2020-09-14_1.652.3
+- Added support for `cra_monitoring` to `Products` array.
+
+### 2020-09-14_1.652.2
+- (beta) Add `/user/items/list` endpoint
+
+### 2020-09-14_1.652.1
+- Add `/transfer/ledger/event/list` endpoint
+
 # 42.0.0
 - Updating to OAS 2020-09-14_1.652.0
 
+## Breaking changes in this version
+
+- [Breaking] Replacing `voe` references to instead be `employment_refresh` in `/cra/check_report/verification/get` and `/cra/check_report/create`
+  - `/cra/check_report/verification/get`'s `reports_requested` options are now `VOA` and `employment_refresh`
+  - `voe_options` in the request is now `employment_refresh_options`
+  - `/cra/check_report/verification/get`'s response now has `report.employment_refresh` instead of `report.voe`
+  - `gse_options.report_type` in `/cra/check_report/create` are now `VOA` and `employment_refresh` 
+
 ## OpenAPI Schema Changes
 ### 2020-09-14_1.652.0
 - Add optional `cursor` and `count` fields to the `/payment_initiation/recipient/list` request and `next_cursor` to its response
@@ -62,6 +119,12 @@ See full changelog for the OpenAPI schema (OAS) [here](https://github.com/plaid/
 # 41.0.0
 - Updating to OAS 2020-09-14_1.645.0
 
+## Breaking changes in this version
+
+- [Breaking] For Signal, remove enum values `REAL_TIME_PAYMENTS` and `DEBIT_CARD` as these payment methods are not supported by the Signal product.
+- [Breaking] Rename client library `/cra/check_report/create`'s `partner_insights` object to type `CraCheckReportCreatePartnerInsightsOptions` instead of `CraCheckReportPartnerInsightsGetOptions`. All the object fields are identical.
+- [Breaking] Rename client library `/cra/check_report/partner_insights/get`'s `option.prism_versions` object to type `PrismVersionsDeprecated` instead of `PrismVersions`. All the object fields' are identical.
+
 ## OpenAPI Schema Changes
 ### 2020-09-14_1.645.0
 - Removes the `payment_details` field from `/accounts/balance/get` request
@@ -142,8 +205,8 @@ See full changelog for the OpenAPI schema (OAS) [here](https://github.com/plaid/
 - Add missing `unsent` value as a possible `verification_status` to reflect actual API behavior.
 
 ### 2020-09-14_1.637.3
-- (beta) Add `PLAID-NEW-USER-API-ENABLED` as a header parameter to `/user/create`
-- (beta) Add `PLAID-NEW-USER-API-ENABLED` as a header parameter to `/user/remove`
+- (beta) Add `PLAID-NEW-USER-API-ENABLED` as a header parameter to `/user/create`. This header is only for the use of customers in the new user API beta; customers should *not* use this parameter unless they have been advised to do so by Plaid. 
+- (beta) Add `PLAID-NEW-USER-API-ENABLED` as a header parameter to `/user/remove`. This header is only for the use of customers in the new user API beta; customers should *not* use this parameter unless they have been advised to do so by Plaid. 
 
 ### 2020-09-14_1.637.2
 - (beta) Add `user_id` to `/session/token/create` response

data/Dockerfile

@@ -1,4 +1,5 @@
 # Note: This image is also built in CircleCI, so limit references to internal repositories.
+# Keep this in sync with the image in plaid-ruby-release Jenkinsfile
 FROM ruby:3.2.0
 
 # Create app directory

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    plaid (42.0.0)
+    plaid (43.0.0)
       faraday (>= 1.0.1, < 3.0)
       faraday-multipart (>= 1.0.1, < 2.0)
 
@@ -11,7 +11,7 @@ GEM
     ast (2.4.1)
     diff-lcs (1.4.4)
     dotenv (2.7.6)
-    faraday (2.13.2)
+    faraday (2.13.4)
       faraday-net_http (>= 2.0, < 3.5)
       json
       logger
@@ -19,7 +19,7 @@ GEM
       multipart-post (~> 2.0)
     faraday-net_http (3.4.1)
       net-http (>= 0.5.0)
-    json (2.13.0)
+    json (2.13.2)
     logger (1.7.0)
     minitest (5.25.4)
     minitest-around (0.5.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=42.0.0
+RUBY_PACKAGE_VERSION=43.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.652.0
+The version of the OpenAPI document: 2020-09-14_1.658.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0
@@ -903,6 +903,74 @@ module Plaid
       return data, status_code, headers
     end
 
+    # Verify auth data
+    # The `/auth/verify` endpoint verifies bank account numbers against Plaid's database via Database Auth.
+    # @param auth_verify_request [AuthVerifyRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [AuthVerifyResponse]
+    def auth_verify(auth_verify_request, opts = {})
+      data, _status_code, _headers = auth_verify_with_http_info(auth_verify_request, opts)
+      data
+    end
+
+    # Verify auth data
+    # The `/auth/verify` endpoint verifies bank account numbers against Plaid's database via Database Auth.
+    # @param auth_verify_request [AuthVerifyRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(AuthVerifyResponse, Integer, Hash)>] AuthVerifyResponse data, response status code and response headers
+    def auth_verify_with_http_info(auth_verify_request, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: PlaidApi.auth_verify ...'
+      end
+      # verify the required parameter 'auth_verify_request' is set
+      if @api_client.config.client_side_validation && auth_verify_request.nil?
+        fail ArgumentError, "Missing the required parameter 'auth_verify_request' when calling PlaidApi.auth_verify"
+      end
+      # resource path
+      local_var_path = '/auth/verify'
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      # HTTP header 'Content-Type'
+      content_type = @api_client.select_header_content_type(['application/json'])
+      if !content_type.nil?
+          header_params['Content-Type'] = content_type
+      end
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(auth_verify_request)
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'AuthVerifyResponse'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['clientId', 'plaidVersion', 'secret']
+
+      new_options = opts.merge(
+        :operation => :"PlaidApi.auth_verify",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: PlaidApi#auth_verify\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Get balance of your Bank Transfer account
     # Use the `/bank_transfer/balance/get` endpoint to see the available balance in your bank transfer account. Debit transfers increase this balance once their status is posted. Credit transfers decrease this balance when they are created.  The transactable balance shows the amount in your account that you are able to use for transfers, and is essentially your available balance minus your minimum balance.  Note that this endpoint can only be used with FBO accounts, when using Bank Transfers in the Full Service configuration. It cannot be used on your own account when using Bank Transfers in the BTS Platform configuration.
     # @param bank_transfer_balance_get_request [BankTransferBalanceGetRequest] 
@@ -6467,7 +6535,7 @@ module Plaid
     end
 
     # Create a new Identity Verification
-    # Create a new Identity Verification for the user specified by the `client_user_id` field. The requirements and behavior of the verification are determined by the `template_id` provided. If you don't know whether the associated user already has an active Identity Verification, you can specify `\"is_idempotent\": true` in the request body. With idempotency enabled, a new Identity Verification will only be created if one does not already exist for the associated `client_user_id` and `template_id`. If an Identity Verification is found, it will be returned unmodified with an `200 OK` HTTP status code.  You can also use this endpoint to supply information you already have collected about the user; if any of these fields are specified, the screens prompting the user to enter them will be skipped during the Link flow. 
+    # Create a new Identity Verification for the user specified by the `client_user_id` and/or `user_id` field. At least one of these two fields must be provided. The requirements and behavior of the verification are determined by the `template_id` provided. If `user_id` is provided, there must be an associated user otherwise an error will be returned. If you don't know whether an active Identity Verification exists for a given `client_user_id` and/or `user_id`, you can specify `\"is_idempotent\": true` in the request body. With idempotency enabled, a new Identity Verification will only be created if one does not already exist for the associated `client_user_id` and/or `user_id`, and `template_id`. If an Identity Verification is found, it will be returned unmodified with a `200 OK` HTTP status code. If `user_id` is not provided, you can also use this endpoint to supply information you already have collected about the user; if any of these fields are specified, the screens prompting the user to enter them will be skipped during the Link flow. If `user_id` is provided, user information can not be included in the request body. Please use the `/user/update` endpoint to update user data instead. 
     # @param identity_verification_create_request [IdentityVerificationCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [IdentityVerificationCreateResponse]
@@ -6477,7 +6545,7 @@ module Plaid
     end
 
     # Create a new Identity Verification
-    # Create a new Identity Verification for the user specified by the &#x60;client_user_id&#x60; field. The requirements and behavior of the verification are determined by the &#x60;template_id&#x60; provided. If you don&#39;t know whether the associated user already has an active Identity Verification, you can specify &#x60;\&quot;is_idempotent\&quot;: true&#x60; in the request body. With idempotency enabled, a new Identity Verification will only be created if one does not already exist for the associated &#x60;client_user_id&#x60; and &#x60;template_id&#x60;. If an Identity Verification is found, it will be returned unmodified with an &#x60;200 OK&#x60; HTTP status code.  You can also use this endpoint to supply information you already have collected about the user; if any of these fields are specified, the screens prompting the user to enter them will be skipped during the Link flow. 
+    # Create a new Identity Verification for the user specified by the &#x60;client_user_id&#x60; and/or &#x60;user_id&#x60; field. At least one of these two fields must be provided. The requirements and behavior of the verification are determined by the &#x60;template_id&#x60; provided. If &#x60;user_id&#x60; is provided, there must be an associated user otherwise an error will be returned. If you don&#39;t know whether an active Identity Verification exists for a given &#x60;client_user_id&#x60; and/or &#x60;user_id&#x60;, you can specify &#x60;\&quot;is_idempotent\&quot;: true&#x60; in the request body. With idempotency enabled, a new Identity Verification will only be created if one does not already exist for the associated &#x60;client_user_id&#x60; and/or &#x60;user_id&#x60;, and &#x60;template_id&#x60;. If an Identity Verification is found, it will be returned unmodified with a &#x60;200 OK&#x60; HTTP status code. If &#x60;user_id&#x60; is not provided, you can also use this endpoint to supply information you already have collected about the user; if any of these fields are specified, the screens prompting the user to enter them will be skipped during the Link flow. If &#x60;user_id&#x60; is provided, user information can not be included in the request body. Please use the &#x60;/user/update&#x60; endpoint to update user data instead. 
     # @param identity_verification_create_request [IdentityVerificationCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(IdentityVerificationCreateResponse, Integer, Hash)>] IdentityVerificationCreateResponse data, response status code and response headers
@@ -8371,7 +8439,7 @@ module Plaid
     end
 
     # Remove an Item
-    # The `/item/remove` endpoint allows you to remove an Item. Once removed, the `access_token`, as well as any processor tokens or bank account tokens associated with the Item, is no longer valid and cannot be used to access any data that was associated with the Item.  Calling `/item/remove` is a recommended best practice when offboarding users or if a user chooses to disconnect an account linked via Plaid. For subscription products, such as Transactions, Liabilities, and Investments, calling `/item/remove` is required to end subscription billing for the Item, unless the end user revoked permission (e.g. via [https://my.plaid.com/](https://my.plaid.com/). For more details, see [Subscription fee model](https://plaid.com/docs/account/billing/#subscription-fee).  In Limited Production, calling `/item/remove` does not impact the number of remaining Limited Production Items you have available.  Removing an Item does not affect any Asset Reports or Audit Copies you have already created, which will remain accessible until you remove access to them specifically using the `/asset_report/remove` endpoint.  Also note that for certain OAuth-based institutions, an Item removed via `/item/remove` may still show as an active connection in the institution's OAuth permission manager.  API versions 2019-05-29 and earlier return a `removed` boolean as part of the response.
+    # The `/item/remove` endpoint allows you to remove an Item. Once removed, the `access_token`, as well as any processor tokens or bank account tokens associated with the Item, is no longer valid and cannot be used to access any data that was associated with the Item.  Calling `/item/remove` is a recommended best practice when offboarding users or if a user chooses to disconnect an account linked via Plaid. For subscription products, such as Transactions, Liabilities, and Investments, calling `/item/remove` is required to end subscription billing for the Item, unless the end user revoked permission (e.g. via [https://my.plaid.com/](https://my.plaid.com/)). For more details, see [Subscription fee model](https://plaid.com/docs/account/billing/#subscription-fee).  In Limited Production, calling `/item/remove` does not impact the number of remaining Limited Production Items you have available.  Removing an Item does not affect any Asset Reports or Audit Copies you have already created, which will remain accessible until you remove access to them specifically using the `/asset_report/remove` endpoint.  Also note that for certain OAuth-based institutions, an Item removed via `/item/remove` may still show as an active connection in the institution's OAuth permission manager.  API versions 2019-05-29 and earlier return a `removed` boolean as part of the response.
     # @param item_remove_request [ItemRemoveRequest] 
     # @param [Hash] opts the optional parameters
     # @return [ItemRemoveResponse]
@@ -8381,7 +8449,7 @@ module Plaid
     end
 
     # Remove an Item
-    # The &#x60;/item/remove&#x60; endpoint allows you to remove an Item. Once removed, the &#x60;access_token&#x60;, as well as any processor tokens or bank account tokens associated with the Item, is no longer valid and cannot be used to access any data that was associated with the Item.  Calling &#x60;/item/remove&#x60; is a recommended best practice when offboarding users or if a user chooses to disconnect an account linked via Plaid. For subscription products, such as Transactions, Liabilities, and Investments, calling &#x60;/item/remove&#x60; is required to end subscription billing for the Item, unless the end user revoked permission (e.g. via [https://my.plaid.com/](https://my.plaid.com/). For more details, see [Subscription fee model](https://plaid.com/docs/account/billing/#subscription-fee).  In Limited Production, calling &#x60;/item/remove&#x60; does not impact the number of remaining Limited Production Items you have available.  Removing an Item does not affect any Asset Reports or Audit Copies you have already created, which will remain accessible until you remove access to them specifically using the &#x60;/asset_report/remove&#x60; endpoint.  Also note that for certain OAuth-based institutions, an Item removed via &#x60;/item/remove&#x60; may still show as an active connection in the institution&#39;s OAuth permission manager.  API versions 2019-05-29 and earlier return a &#x60;removed&#x60; boolean as part of the response.
+    # The &#x60;/item/remove&#x60; endpoint allows you to remove an Item. Once removed, the &#x60;access_token&#x60;, as well as any processor tokens or bank account tokens associated with the Item, is no longer valid and cannot be used to access any data that was associated with the Item.  Calling &#x60;/item/remove&#x60; is a recommended best practice when offboarding users or if a user chooses to disconnect an account linked via Plaid. For subscription products, such as Transactions, Liabilities, and Investments, calling &#x60;/item/remove&#x60; is required to end subscription billing for the Item, unless the end user revoked permission (e.g. via [https://my.plaid.com/](https://my.plaid.com/)). For more details, see [Subscription fee model](https://plaid.com/docs/account/billing/#subscription-fee).  In Limited Production, calling &#x60;/item/remove&#x60; does not impact the number of remaining Limited Production Items you have available.  Removing an Item does not affect any Asset Reports or Audit Copies you have already created, which will remain accessible until you remove access to them specifically using the &#x60;/asset_report/remove&#x60; endpoint.  Also note that for certain OAuth-based institutions, an Item removed via &#x60;/item/remove&#x60; may still show as an active connection in the institution&#39;s OAuth permission manager.  API versions 2019-05-29 and earlier return a &#x60;removed&#x60; boolean as part of the response.
     # @param item_remove_request [ItemRemoveRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(ItemRemoveResponse, Integer, Hash)>] ItemRemoveResponse data, response status code and response headers
@@ -8847,7 +8915,7 @@ module Plaid
     end
 
     # Get Link Token
-    # The `/link/token/get` endpoint gets information about a Link session, including all callbacks fired during the session along with their metadata, including the public token. This endpoint is used with Link flows that don't provide a public token via frontend callbacks, such as the [Hosted Link flow](https://plaid.com/docs/link/hosted-link/) and the [Multi-Item Link flow](https://plaid.com/docs/link/multi-item-link/). It also can be useful for debugging purposes.
+    # The `/link/token/get` endpoint gets information about a Link session, including all callbacks fired during the session along with their metadata, including the public token. This endpoint is used with Link flows that don't provide a public token via frontend callbacks, such as the [Hosted Link flow](https://plaid.com/docs/link/hosted-link/) and the [Multi-Item Link flow](https://plaid.com/docs/link/multi-item-link/). It also can be useful for debugging purposes.  By default, this endpoint will only return complete event data for Hosted Link sessions. To use `/link/token/get` to retrieve event data for non-Hosted-Link sessions, contact your account manager to request that your account be enabled for Link events. If you do not have an account manager, you can submit this request via a support ticket. Enablement for Link events will also cause you to receive additional webhooks related to Link events, such as the `SESSION_FINISHED` and `EVENTS` webhook. 
     # @param link_token_get_request [LinkTokenGetRequest] 
     # @param [Hash] opts the optional parameters
     # @return [LinkTokenGetResponse]
@@ -8857,7 +8925,7 @@ module Plaid
     end
 
     # Get Link Token
-    # The &#x60;/link/token/get&#x60; endpoint gets information about a Link session, including all callbacks fired during the session along with their metadata, including the public token. This endpoint is used with Link flows that don&#39;t provide a public token via frontend callbacks, such as the [Hosted Link flow](https://plaid.com/docs/link/hosted-link/) and the [Multi-Item Link flow](https://plaid.com/docs/link/multi-item-link/). It also can be useful for debugging purposes.
+    # The &#x60;/link/token/get&#x60; endpoint gets information about a Link session, including all callbacks fired during the session along with their metadata, including the public token. This endpoint is used with Link flows that don&#39;t provide a public token via frontend callbacks, such as the [Hosted Link flow](https://plaid.com/docs/link/hosted-link/) and the [Multi-Item Link flow](https://plaid.com/docs/link/multi-item-link/). It also can be useful for debugging purposes.  By default, this endpoint will only return complete event data for Hosted Link sessions. To use &#x60;/link/token/get&#x60; to retrieve event data for non-Hosted-Link sessions, contact your account manager to request that your account be enabled for Link events. If you do not have an account manager, you can submit this request via a support ticket. Enablement for Link events will also cause you to receive additional webhooks related to Link events, such as the &#x60;SESSION_FINISHED&#x60; and &#x60;EVENTS&#x60; webhook. 
     # @param link_token_get_request [LinkTokenGetRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(LinkTokenGetResponse, Integer, Hash)>] LinkTokenGetResponse data, response status code and response headers
@@ -13267,7 +13335,7 @@ module Plaid
     end
 
     # Create sandbox transactions
-    # Use the `/sandbox/transactions/create` endpoint to create new transactions for an existing Item. This endpoint can be used to add up to 10 transactions to any Item at a time.  This endpoint is only available in the Sandbox environment, thus can only be used with Items that were created in the Sandbox. You can use this to add transactions to test the `/transactions/get` and `/transactions/sync` endpoints.  For Items created in the Production environment, real transactions will be available once the transactions product is enabled.
+    # Use the `/sandbox/transactions/create` endpoint to create new transactions for an existing Item. This endpoint can be used to add up to 10 transactions to any Item at a time.  This endpoint can only be used with Items that were created in the Sandbox environment using the `user_transactions_dynamic` test user. You can use this to add transactions to test the `/transactions/get` and `/transactions/sync` endpoints.
     # @param sandbox_transactions_create_request [SandboxTransactionsCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [SandboxTransactionsCreateResponse]
@@ -13277,7 +13345,7 @@ module Plaid
     end
 
     # Create sandbox transactions
-    # Use the &#x60;/sandbox/transactions/create&#x60; endpoint to create new transactions for an existing Item. This endpoint can be used to add up to 10 transactions to any Item at a time.  This endpoint is only available in the Sandbox environment, thus can only be used with Items that were created in the Sandbox. You can use this to add transactions to test the &#x60;/transactions/get&#x60; and &#x60;/transactions/sync&#x60; endpoints.  For Items created in the Production environment, real transactions will be available once the transactions product is enabled.
+    # Use the &#x60;/sandbox/transactions/create&#x60; endpoint to create new transactions for an existing Item. This endpoint can be used to add up to 10 transactions to any Item at a time.  This endpoint can only be used with Items that were created in the Sandbox environment using the &#x60;user_transactions_dynamic&#x60; test user. You can use this to add transactions to test the &#x60;/transactions/get&#x60; and &#x60;/transactions/sync&#x60; endpoints.
     # @param sandbox_transactions_create_request [SandboxTransactionsCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(SandboxTransactionsCreateResponse, Integer, Hash)>] SandboxTransactionsCreateResponse data, response status code and response headers
@@ -14830,74 +14898,6 @@ module Plaid
       return data, status_code, headers
     end
 
-    # Receive token notifications from The Clearing House (TCH).
-    # This endpoint allows us to receive token notifications from The Clearing House (TCH). The schema is defined by TCH.
-    # @param tch_notification [TCHNotification] 
-    # @param [Hash] opts the optional parameters
-    # @return [TCHNotificationResponse]
-    def tch_notifications(tch_notification, opts = {})
-      data, _status_code, _headers = tch_notifications_with_http_info(tch_notification, opts)
-      data
-    end
-
-    # Receive token notifications from The Clearing House (TCH).
-    # This endpoint allows us to receive token notifications from The Clearing House (TCH). The schema is defined by TCH.
-    # @param tch_notification [TCHNotification] 
-    # @param [Hash] opts the optional parameters
-    # @return [Array<(TCHNotificationResponse, Integer, Hash)>] TCHNotificationResponse data, response status code and response headers
-    def tch_notifications_with_http_info(tch_notification, opts = {})
-      if @api_client.config.debugging
-        @api_client.config.logger.debug 'Calling API: PlaidApi.tch_notifications ...'
-      end
-      # verify the required parameter 'tch_notification' is set
-      if @api_client.config.client_side_validation && tch_notification.nil?
-        fail ArgumentError, "Missing the required parameter 'tch_notification' when calling PlaidApi.tch_notifications"
-      end
-      # resource path
-      local_var_path = '/tch/notifications'
-
-      # query parameters
-      query_params = opts[:query_params] || {}
-
-      # header parameters
-      header_params = opts[:header_params] || {}
-      # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
-      # HTTP header 'Content-Type'
-      content_type = @api_client.select_header_content_type(['application/json'])
-      if !content_type.nil?
-          header_params['Content-Type'] = content_type
-      end
-
-      # form parameters
-      form_params = opts[:form_params] || {}
-
-      # http body (model)
-      post_body = opts[:debug_body] || @api_client.object_to_http_body(tch_notification)
-
-      # return_type
-      return_type = opts[:debug_return_type] || 'TCHNotificationResponse'
-
-      # auth_names
-      auth_names = opts[:debug_auth_names] || ['clientId', 'plaidVersion', 'secret']
-
-      new_options = opts.merge(
-        :operation => :"PlaidApi.tch_notifications",
-        :header_params => header_params,
-        :query_params => query_params,
-        :form_params => form_params,
-        :body => post_body,
-        :auth_names => auth_names,
-        :return_type => return_type
-      )
-
-      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
-      if @api_client.config.debugging
-        @api_client.config.logger.debug "API called: PlaidApi#tch_notifications\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
-      end
-      return data, status_code, headers
-    end
-
     # enhance locally-held transaction data
     # The `/beta/transactions/v1/enhance` endpoint enriches raw transaction data provided directly by clients.  The product is currently in beta.
     # @param transactions_enhance_get_request [TransactionsEnhanceGetRequest] 
@@ -16666,6 +16666,74 @@ module Plaid
       return data, status_code, headers
     end
 
+    # List transfer ledger events
+    # Use the `/transfer/ledger/event/list` endpoint to get a list of ledger events for a specific ledger based on specified filter criteria.
+    # @param transfer_ledger_event_list_request [TransferLedgerEventListRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [TransferLedgerEventListResponse]
+    def transfer_ledger_event_list(transfer_ledger_event_list_request, opts = {})
+      data, _status_code, _headers = transfer_ledger_event_list_with_http_info(transfer_ledger_event_list_request, opts)
+      data
+    end
+
+    # List transfer ledger events
+    # Use the &#x60;/transfer/ledger/event/list&#x60; endpoint to get a list of ledger events for a specific ledger based on specified filter criteria.
+    # @param transfer_ledger_event_list_request [TransferLedgerEventListRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(TransferLedgerEventListResponse, Integer, Hash)>] TransferLedgerEventListResponse data, response status code and response headers
+    def transfer_ledger_event_list_with_http_info(transfer_ledger_event_list_request, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: PlaidApi.transfer_ledger_event_list ...'
+      end
+      # verify the required parameter 'transfer_ledger_event_list_request' is set
+      if @api_client.config.client_side_validation && transfer_ledger_event_list_request.nil?
+        fail ArgumentError, "Missing the required parameter 'transfer_ledger_event_list_request' when calling PlaidApi.transfer_ledger_event_list"
+      end
+      # resource path
+      local_var_path = '/transfer/ledger/event/list'
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      # HTTP header 'Content-Type'
+      content_type = @api_client.select_header_content_type(['application/json'])
+      if !content_type.nil?
+          header_params['Content-Type'] = content_type
+      end
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(transfer_ledger_event_list_request)
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'TransferLedgerEventListResponse'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['clientId', 'plaidVersion', 'secret']
+
+      new_options = opts.merge(
+        :operation => :"PlaidApi.transfer_ledger_event_list",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: PlaidApi#transfer_ledger_event_list\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Retrieve Plaid Ledger balance
     # Use the `/transfer/ledger/get` endpoint to view a balance on the ledger held with Plaid.
     # @param transfer_ledger_get_request [TransferLedgerGetRequest] 
@@ -18641,6 +18709,74 @@ module Plaid
       return data, status_code, headers
     end
 
+    # List Items associated with a User
+    # Returns Items associated with a User along with their corresponding statuses.
+    # @param user_items_list_request [UserItemsListRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [UserItemsListResponse]
+    def user_items_list(user_items_list_request, opts = {})
+      data, _status_code, _headers = user_items_list_with_http_info(user_items_list_request, opts)
+      data
+    end
+
+    # List Items associated with a User
+    # Returns Items associated with a User along with their corresponding statuses.
+    # @param user_items_list_request [UserItemsListRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(UserItemsListResponse, Integer, Hash)>] UserItemsListResponse data, response status code and response headers
+    def user_items_list_with_http_info(user_items_list_request, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: PlaidApi.user_items_list ...'
+      end
+      # verify the required parameter 'user_items_list_request' is set
+      if @api_client.config.client_side_validation && user_items_list_request.nil?
+        fail ArgumentError, "Missing the required parameter 'user_items_list_request' when calling PlaidApi.user_items_list"
+      end
+      # resource path
+      local_var_path = '/user/items/list'
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      # HTTP header 'Content-Type'
+      content_type = @api_client.select_header_content_type(['application/json'])
+      if !content_type.nil?
+          header_params['Content-Type'] = content_type
+      end
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(user_items_list_request)
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'UserItemsListResponse'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['clientId', 'plaidVersion', 'secret']
+
+      new_options = opts.merge(
+        :operation => :"PlaidApi.user_items_list",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: PlaidApi#user_items_list\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Remove user
     # `/user/remove` deletes a user token and and associated information, including any Items associated with the token. Any subsequent calls to retrieve information using the same user token will result in an error stating the user does not exist. If a user is created for a given `client_user_id` using `/user/create` and that user is then deleted with `/user/remove`, the `client_user_id` cannot be reused for another `/user/create` request.
     # @param user_remove_request [UserRemoveRequest] 

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.652.0
+The version of the OpenAPI document: 2020-09-14_1.658.0
 
 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 v42.0.0"
+      @user_agent = "Plaid Ruby v43.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.652.0
+The version of the OpenAPI document: 2020-09-14_1.658.0
 
 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.652.0
+The version of the OpenAPI document: 2020-09-14_1.658.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.3.0