mx-platform-ruby 1.10.0 → 1.10.1

data/spec/api/transactions_api_spec.rb

@@ -1,9 +1,9 @@
 =begin
 #MX Platform API
 
-#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.
+#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.  Just getting started? See our [use case guides](/use-cases/). 
 
-The version of the OpenAPI document: 0.1.0
+The version of the OpenAPI document: 20111101
 
 Generated by: https://openapi-generator.tech
 Generator version: 7.8.0
@@ -32,15 +32,267 @@ describe 'TransactionsApi' do
     end
   end
 
-  # unit tests for users_user_guid_accounts_account_guid_transactions_post
+  # unit tests for create_manual_transaction
   # Create manual transaction
   # This endpoint can only be used to create manual transactions that are under a manual account. This endpoint accepts the optional MX-Skip-Webhook header and skip_webhook parameter.
-  # @param user_guid The unique identifier for the user.
-  # @param account_guid The unique identifier for the account.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param account_guid The unique id for an `account`.
   # @param transaction_create_request_body 
   # @param [Hash] opts the optional parameters
   # @return [TransactionCreateResponseBody]
-  describe 'users_user_guid_accounts_account_guid_transactions_post test' do
+  describe 'create_manual_transaction test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for create_split_transactions
+  # Create split transactions
+  # This endpoint creates two or more child transactions that are branched from a previous transaction. This endpoint allows you to link multiple categories, descriptions, and amounts to a parent transaction.  When a split transaction is created, the parent transaction's `has_been_split` field will automatically be updated to true and the child transactions' `parent_guid` will have the transaction guid of the parent. The total amount of the child transactions must equal the amount of the parent transaction. Once a transaction has been split it can't be split again.    In order to re-split a transaction, it must first be un-split. This can be done by calling the Delete Split Transactions endpoint. Calling this endpoint will delete the existing child transactions and update the parent transaction's `has_been_split` field to false. You can then re-split the parent transaction by calling Create Split Transaction again. 
+  # @param transaction_guid The unique id for a `transaction`.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param [Hash] opts the optional parameters
+  # @option opts [SplitTransactionRequestBody] :split_transaction_request_body 
+  # @return [SplitTransactionsResponseBody]
+  describe 'create_split_transactions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_manual_transactions
+  # Delete manual transactions
+  # Delete a manual transaction. In the path, use the manual transaction guid as the `transaction_guid`, such as `MAN-810828b0-5210-4878-9bd3-f4ce514f90c4`.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param transaction_guid The unique id for a `transaction`.
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'delete_manual_transactions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_split_transactions
+  # Delete split transactions
+  # This endpoint deletes all split transactions linked to a parent transaction, but it leaves the parent transaction active. This request will also update the parent transaction's has_been_split field to false. This endpoint accepts the optional MX-Skip-Webhook header.
+  # @param transaction_guid The unique id for a `transaction`.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'delete_split_transactions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_transaction_rule
+  # Delete transaction rule
+  # Use this endpoint to permanently delete a transaction rule based on its unique GUID.
+  # @param transaction_rule_guid The unique id for a `transaction_rule`.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'delete_transaction_rule test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for enhance_transactions
+  # Enhance transactions
+  # Use this endpoint to categorize, cleanse, and classify transactions. These transactions are not persisted or stored on the MX platform. <br /><br />For more information on returned data, please see the [Enhanced Transactions fields guide](/api-reference/platform-api/reference/transactions-overview#enhanced-transactions).
+  # @param enhance_transactions_request_body Transaction object to be enhanced
+  # @param [Hash] opts the optional parameters
+  # @return [EnhanceTransactionsResponseBody]
+  describe 'enhance_transactions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for extend_history
+  # Extend history
+  # Some institutions allow developers to access an extended transaction history with up to 24 months of data associated with a particular member. The process for fetching and then reading this extended transaction history is much like standard aggregation, and it may trigger multi-factor authentication.
+  # @param member_guid The unique id for a `member`.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param [Hash] opts the optional parameters
+  # @return [MemberResponseBody]
+  describe 'extend_history test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_transactions
+  # List transactions
+  # Requests to this endpoint return a list of transactions associated with the specified `user`, across all members and accounts associated with that `user`. <br /><br />Enhanced transaction data may be requested using the `includes` parameter. To use this optional parameter, the value should include the optional metadata requested such as `repeating_transactions`, `merchants`, `classifications`, `geolocations`. For more information, see the [Optional Enhancement Query Parameter guide](/api-reference/platform-api/reference/transactions-overview#enhanced-transactions#optional-enhancement-query-parameter).
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :page Results are paginated. Specify current page.
+  # @option opts [Integer] :records_per_page This specifies the number of records to be returned on each page. Defaults to `25`. The valid range is from `10` to `1000`. If the value exceeds `1000`, the default value of `25` will be used instead.
+  # @option opts [String] :from_date Filter transactions from this date. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Defaults to 120 days ago if not provided.
+  # @option opts [String] :to_date Filter transactions to this date (at midnight). This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Defaults to 5 days forward from the day the request is made to capture pending transactions.
+  # @option opts [String] :from_created_at Filter transactions from the date the transaction was created. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :to_created_at Filter transaction to the date in which the transaction was created. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :from_updated_at Filter transactions from the date in which the transaction was updated. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :to_updated_at Filter transactions to the date in which the transaction was updated. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :category_guid Filter transactions belonging to specified `category_guid`.  For example, `?category_guid=CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874`.
+  # @option opts [Array<String>] :category_guid2 Filter transactions belonging to any specified &#x60;category_guid[]&#x60; in url.  For example, &#x60;?category_guid[]&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [String] :top_level_category_guid Filter transactions belonging to specified &#x60;top_level_category_guid&#x60;. This must be top level category guid, use &#x60;category_guid&#x60; for subcategory guid.  For example, &#x60;?top_level_category_guid&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [Array<String>] :top_level_category_guid2 Filter transactions belonging to any specified &#x60;top_level_category_guid[]&#x60; in url. This must be top level category guid(s), use &#x60;category_guid&#x60; for subcategory guid(s).  For example, &#x60;?top_level_category_guid[]&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [String] :use_case The use case associated with the member. Valid values are &#x60;PFM&#x60; and &#x60;MONEY_MOVEMENT&#x60;. For example, you can append either &#x60;?use_case&#x3D;PFM&#x60; or &#x60;?use_case&#x3D;MONEY_MOVEMENT&#x60;.
+  # @option opts [String] :includes Options for enhanced transactions. This query parameter is optional. Possible additional metadata: &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. The query value is format sensitive. To retrieve all available enhancements, append:  &#x60;?includes&#x3D;repeating_transactions,merchants,classifications,geolocations&#x60;.    The query options may be combined to specific enhancements. For example, to request Repeating Transactions and Geolocation data, use:   &#x60;?includes&#x3D;repeating_transactions,geolocations&#x60;.  - Repeating Transactions: Identifies transactions with predictable recurrence patterns (e.g., Bill, Income, Subscription). - Merchants: Enriches transactions with merchant name. - Classifications: Provides more insight into the type of money movement that is occurring on the transaction, whether it be retail or investments. - Geolocation: Provides geographic metadata. 
+  # @return [TransactionsResponseBodyIncludes]
+  describe 'list_transactions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_transactions_by_account
+  # List transactions by account
+  # Requests to this endpoint return a list of transactions associated with the specified account. &lt;br /&gt;&lt;br /&gt;Enhanced transaction data may be requested using the &#x60;includes&#x60; parameter.  To use this optional parameter, the value should include the optional metadata requested such as &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. For more information, see the [Optional Enhancement Query Parameter guide](/api-reference/platform-api/reference/transactions-overview#enhanced-transactions#optional-enhancement-query-parameter). 
+  # @param account_guid The unique id for an &#x60;account&#x60;.
+  # @param user_guid The unique identifier for a &#x60;user&#x60;, beginning with the prefix &#x60;USR-&#x60;.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :page Results are paginated. Specify current page.
+  # @option opts [Integer] :records_per_page This specifies the number of records to be returned on each page. Defaults to &#x60;25&#x60;. The valid range is from &#x60;10&#x60; to &#x60;1000&#x60;. If the value exceeds &#x60;1000&#x60;, the default value of &#x60;25&#x60; will be used instead.
+  # @option opts [String] :from_date Filter transactions from this date. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Defaults to 120 days ago if not provided.
+  # @option opts [String] :to_date Filter transactions to this date (at midnight). This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Defaults to 5 days forward from the day the request is made to capture pending transactions.
+  # @option opts [String] :from_created_at Filter transactions from the date the transaction was created. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :to_created_at Filter transaction to the date in which the transaction was created. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :from_updated_at Filter transactions from the date in which the transaction was updated. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :to_updated_at Filter transactions to the date in which the transaction was updated. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :category_guid Filter transactions belonging to specified &#x60;category_guid&#x60;.  For example, &#x60;?category_guid&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [Array<String>] :category_guid2 Filter transactions belonging to any specified &#x60;category_guid[]&#x60; in url.  For example, &#x60;?category_guid[]&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [String] :top_level_category_guid Filter transactions belonging to specified &#x60;top_level_category_guid&#x60;. This must be top level category guid, use &#x60;category_guid&#x60; for subcategory guid.  For example, &#x60;?top_level_category_guid&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [Array<String>] :top_level_category_guid2 Filter transactions belonging to any specified &#x60;top_level_category_guid[]&#x60; in url. This must be top level category guid(s), use &#x60;category_guid&#x60; for subcategory guid(s).  For example, &#x60;?top_level_category_guid[]&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [String] :includes Options for enhanced transactions. This query parameter is optional. Possible additional metadata: &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. The query value is format sensitive. To retrieve all available enhancements, append:  &#x60;?includes&#x3D;repeating_transactions,merchants,classifications,geolocations&#x60;.    The query options may be combined to specific enhancements. For example, to request Repeating Transactions and Geolocation data, use:   &#x60;?includes&#x3D;repeating_transactions,geolocations&#x60;.  - Repeating Transactions: Identifies transactions with predictable recurrence patterns (e.g., Bill, Income, Subscription). - Merchants: Enriches transactions with merchant name. - Classifications: Provides more insight into the type of money movement that is occurring on the transaction, whether it be retail or investments. - Geolocation: Provides geographic metadata. 
+  # @return [TransactionsResponseBodyIncludes]
+  describe 'list_transactions_by_account test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_transactions_by_member
+  # List transactions by member
+  # Requests to this endpoint return a list of transactions associated with the specified &#x60;member&#x60;, across all accounts associated with that &#x60;member&#x60;. &lt;br /&gt;&lt;br /&gt;Enhanced transaction data may be requested using the &#x60;includes&#x60; parameter. To use this optional parameter, the value should include the optional metadata requested such as &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. For more information, see the [Optional Enhancement Query Parameter guide](/api-reference/platform-api/reference/transactions-overview#enhanced-transactions#optional-enhancement-query-parameter).
+  # @param member_guid The unique id for a &#x60;member&#x60;.
+  # @param user_guid The unique identifier for a &#x60;user&#x60;, beginning with the prefix &#x60;USR-&#x60;.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :page Results are paginated. Specify current page.
+  # @option opts [Integer] :records_per_page This specifies the number of records to be returned on each page. Defaults to &#x60;25&#x60;. The valid range is from &#x60;10&#x60; to &#x60;1000&#x60;. If the value exceeds &#x60;1000&#x60;, the default value of &#x60;25&#x60; will be used instead.
+  # @option opts [String] :from_date Filter transactions from this date. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Defaults to 120 days ago if not provided.
+  # @option opts [String] :to_date Filter transactions to this date (at midnight). This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Defaults to 5 days forward from the day the request is made to capture pending transactions.
+  # @option opts [String] :from_created_at Filter transactions from the date the transaction was created. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :to_created_at Filter transaction to the date in which the transaction was created. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :from_updated_at Filter transactions from the date in which the transaction was updated. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :to_updated_at Filter transactions to the date in which the transaction was updated. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :category_guid Filter transactions belonging to specified &#x60;category_guid&#x60;.  For example, &#x60;?category_guid&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [Array<String>] :category_guid2 Filter transactions belonging to any specified &#x60;category_guid[]&#x60; in url.  For example, &#x60;?category_guid[]&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [String] :top_level_category_guid Filter transactions belonging to specified &#x60;top_level_category_guid&#x60;. This must be top level category guid, use &#x60;category_guid&#x60; for subcategory guid.  For example, &#x60;?top_level_category_guid&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [Array<String>] :top_level_category_guid2 Filter transactions belonging to any specified &#x60;top_level_category_guid[]&#x60; in url. This must be top level category guid(s), use &#x60;category_guid&#x60; for subcategory guid(s).  For example, &#x60;?top_level_category_guid[]&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [String] :includes Options for enhanced transactions. This query parameter is optional. Possible additional metadata: &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. The query value is format sensitive. To retrieve all available enhancements, append:  &#x60;?includes&#x3D;repeating_transactions,merchants,classifications,geolocations&#x60;.    The query options may be combined to specific enhancements. For example, to request Repeating Transactions and Geolocation data, use:   &#x60;?includes&#x3D;repeating_transactions,geolocations&#x60;.  - Repeating Transactions: Identifies transactions with predictable recurrence patterns (e.g., Bill, Income, Subscription). - Merchants: Enriches transactions with merchant name. - Classifications: Provides more insight into the type of money movement that is occurring on the transaction, whether it be retail or investments. - Geolocation: Provides geographic metadata. 
+  # @return [TransactionsResponseBodyIncludes]
+  describe 'list_transactions_by_member test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_transactions_by_tag
+  # List transactions by tag
+  # Use this endpoint to get a list of all transactions associated with a particular tag according to the tag&#39;s unique GUID. This lists all transactions that have been assigned to a particular tag using the create tagging endpoint. &lt;br /&gt;&lt;br /&gt;Enhanced transaction data may be requested using the &#x60;includes&#x60; parameter. To use this optional parameter, the value should include the optional metadata requested such as &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. For more information, see the [Optional Enhancement Query Parameter guide](/api-reference/platform-api/reference/transactions-overview#enhanced-transactions#optional-enhancement-query-parameter).
+  # @param user_guid The unique identifier for a &#x60;user&#x60;, beginning with the prefix &#x60;USR-&#x60;.
+  # @param tag_guid The unique id for a &#x60;tag&#x60;.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :page Results are paginated. Specify current page.
+  # @option opts [Integer] :records_per_page This specifies the number of records to be returned on each page. Defaults to &#x60;25&#x60;. The valid range is from &#x60;10&#x60; to &#x60;1000&#x60;. If the value exceeds &#x60;1000&#x60;, the default value of &#x60;25&#x60; will be used instead.
+  # @option opts [String] :from_date Filter transactions from this date. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Defaults to 120 days ago if not provided.
+  # @option opts [String] :to_date Filter transactions to this date (at midnight). This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Defaults to 5 days forward from the day the request is made to capture pending transactions.
+  # @option opts [String] :from_created_at Filter transactions from the date the transaction was created. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :to_created_at Filter transaction to the date in which the transaction was created. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :from_updated_at Filter transactions from the date in which the transaction was updated. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :to_updated_at Filter transactions to the date in which the transaction was updated. This only supports ISO 8601 format without timestamp (YYYY-MM-DD). Maximum date range limit is 6 months.
+  # @option opts [String] :category_guid Filter transactions belonging to specified &#x60;category_guid&#x60;.  For example, &#x60;?category_guid&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [Array<String>] :category_guid2 Filter transactions belonging to any specified &#x60;category_guid[]&#x60; in url.  For example, &#x60;?category_guid[]&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [String] :top_level_category_guid Filter transactions belonging to specified &#x60;top_level_category_guid&#x60;. This must be top level category guid, use &#x60;category_guid&#x60; for subcategory guid.  For example, &#x60;?top_level_category_guid&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [Array<String>] :top_level_category_guid2 Filter transactions belonging to any specified &#x60;top_level_category_guid[]&#x60; in url. This must be top level category guid(s), use &#x60;category_guid&#x60; for subcategory guid(s).  For example, &#x60;?top_level_category_guid[]&#x3D;CAT-7829f71c-2e8c-afa5-2f55-fa3634b89874&#x60;.
+  # @option opts [String] :use_case The use case associated with the member. Valid values are &#x60;PFM&#x60; and &#x60;MONEY_MOVEMENT&#x60;. For example, you can append either &#x60;?use_case&#x3D;PFM&#x60; or &#x60;?use_case&#x3D;MONEY_MOVEMENT&#x60;.
+  # @option opts [String] :includes Options for enhanced transactions. This query parameter is optional. Possible additional metadata: &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. The query value is format sensitive. To retrieve all available enhancements, append:  &#x60;?includes&#x3D;repeating_transactions,merchants,classifications,geolocations&#x60;.    The query options may be combined to specific enhancements. For example, to request Repeating Transactions and Geolocation data, use:   &#x60;?includes&#x3D;repeating_transactions,geolocations&#x60;.  - Repeating Transactions: Identifies transactions with predictable recurrence patterns (e.g., Bill, Income, Subscription). - Merchants: Enriches transactions with merchant name. - Classifications: Provides more insight into the type of money movement that is occurring on the transaction, whether it be retail or investments. - Geolocation: Provides geographic metadata. 
+  # @return [TransactionsResponseBodyIncludes]
+  describe 'list_transactions_by_tag test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for read_transaction
+  # Read transaction
+  # Requests to this endpoint will return the attributes of the specified &#x60;transaction&#x60;. To read a manual transaction, use the manual transaction guid in the path as the &#x60;transactionGuid&#x60;. &lt;br /&gt;&lt;br /&gt;Enhanced transaction data may be requested using the &#x60;includes&#x60; parameter. To use this optional parameter, the value should include the optional metadata requested such as &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. For more information, see the [Optional Enhancement Query Parameter guide](/api-reference/platform-api/reference/transactions-overview#enhanced-transactions#optional-enhancement-query-parameter).
+  # @param user_guid The unique identifier for a &#x60;user&#x60;, beginning with the prefix &#x60;USR-&#x60;.
+  # @param transaction_guid The unique id for a &#x60;transaction&#x60;.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :includes Options for enhanced transactions. This query parameter is optional. Possible additional metadata: &#x60;repeating_transactions&#x60;, &#x60;merchants&#x60;, &#x60;classifications&#x60;, &#x60;geolocations&#x60;. The query value is format sensitive. To retrieve all available enhancements, append:  &#x60;?includes&#x3D;repeating_transactions,merchants,classifications,geolocations&#x60;.    The query options may be combined to specific enhancements. For example, to request Repeating Transactions and Geolocation data, use:   &#x60;?includes&#x3D;repeating_transactions,geolocations&#x60;.  - Repeating Transactions: Identifies transactions with predictable recurrence patterns (e.g., Bill, Income, Subscription). - Merchants: Enriches transactions with merchant name. - Classifications: Provides more insight into the type of money movement that is occurring on the transaction, whether it be retail or investments. - Geolocation: Provides geographic metadata. 
+  # @return [TransactionsResponseBodyIncludes]
+  describe 'read_transaction test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for repeating_transactions
+  # List Repeating Transactions
+  # Retrieve a list of all recurring transactions for a user. &lt;br /&gt;&lt;br /&gt;For more see the [Repeating Transactions guide](repeating-transactions-overview.mdx).
+  # @param user_guid The unique identifier for a &#x60;user&#x60;, beginning with the prefix &#x60;USR-&#x60;.
+  # @param [Hash] opts the optional parameters
+  # @return [RepeatingTransactionsResponseBody]
+  describe 'repeating_transactions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for specific_repeating_transaction
+  # Get a Repeating Transaction
+  # Get a Specific Repeating Transaction. &lt;br /&gt;&lt;br /&gt;List For more see the [Repeating Transactions guide](repeating-transactions-overview.mdx)
+  # @param user_guid The unique identifier for a &#x60;user&#x60;, beginning with the prefix &#x60;USR-&#x60;.
+  # @param repeating_transaction_guid The unique id for a recurring transaction.
+  # @param [Hash] opts the optional parameters
+  # @return [RepeatingTransactionsResponseBody]
+  describe 'specific_repeating_transaction test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_transaction
+  # Update transaction
+  # Use this endpoint to update a specific transaction according to its unique GUID.
+  # @param user_guid The unique identifier for a &#x60;user&#x60;, beginning with the prefix &#x60;USR-&#x60;.
+  # @param transaction_guid The unique id for a &#x60;transaction&#x60;.
+  # @param transaction_update_request_body Transaction object with the fields to be updated.
+  # @param [Hash] opts the optional parameters
+  # @return [TransactionResponseBody]
+  describe 'update_transaction test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_transaction_by_account
+  # Update Transaction by Account
+  # Use this endpoint to update a specific transaction according to its unique GUID.
+  # @param user_guid The unique identifier for a &#x60;user&#x60;, beginning with the prefix &#x60;USR-&#x60;.
+  # @param member_guid The unique id for a &#x60;member&#x60;.
+  # @param account_guid The unique id for an &#x60;account&#x60;.
+  # @param transaction_guid The unique id for a &#x60;transaction&#x60;.
+  # @param transaction_update_request_body Transaction object to be updated
+  # @param [Hash] opts the optional parameters
+  # @return [TransactionResponseBody]
+  describe 'update_transaction_by_account test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/users_api_spec.rb

@@ -0,0 +1,101 @@
+=begin
+#MX Platform API
+
+#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.  Just getting started? See our [use case guides](/use-cases/). 
+
+The version of the OpenAPI document: 20111101
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.8.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MxPlatformRuby::UsersApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'UsersApi' do
+  before do
+    # run before each test
+    @api_instance = MxPlatformRuby::UsersApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of UsersApi' do
+    it 'should create an instance of UsersApi' do
+      expect(@api_instance).to be_instance_of(MxPlatformRuby::UsersApi)
+    end
+  end
+
+  # unit tests for create_user
+  # Create user
+  # Use this endpoint to create a new user. The API will respond with the newly-created user object if successful, containing a `guid` that you'll set as the `user_guid` in other requests when required. Disabling a user means that accounts and transactions associated with it will not be updated in the background by MX. It will also restrict access to that user’s data until they are no longer disabled.
+  # @param user_create_request_body User object to be created. (None of these parameters are required, but the user object cannot be empty)
+  # @param [Hash] opts the optional parameters
+  # @return [UserResponseBody]
+  describe 'create_user test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_user
+  # Delete user
+  # Use this endpoint to delete the specified `user`. The response will have a status of `204 No Content` without an object.  :::warning Deleting a user is permanent. Deleted users can never be restored. For more info, see [Deleting Objects](https://docs.mx.com/api-reference/platform-api/overview/deleting-objects). ::: 
+  # @param accept Specifies the media type expected in the response.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'delete_user test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_users
+  # List users
+  # Use this endpoint to list every user you've created in the MX Platform API.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :page Results are paginated. Specify current page.
+  # @option opts [Integer] :records_per_page This specifies the number of records to be returned on each page. Defaults to `25`. The valid range is from `10` to `1000`. If the value exceeds `1000`, the default value of `25` will be used instead.
+  # @option opts [String] :id The user `id` to search for.
+  # @option opts [String] :email The user `email` to search for.
+  # @option opts [Boolean] :is_disabled Search for users that are diabled.
+  # @return [UsersResponseBody]
+  describe 'list_users test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for read_user
+  # Read user
+  # Use this endpoint to read the attributes of a specific user.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param [Hash] opts the optional parameters
+  # @return [UserResponseBody]
+  describe 'read_user test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_user
+  # Update user
+  # Use this endpoint to update the attributes of the specified user.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param user_update_request_body User object to be updated (None of these parameters are required, but the user object cannot be empty.)
+  # @param [Hash] opts the optional parameters
+  # @return [UserResponseBody]
+  describe 'update_user test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/verifiable_credentials_api_spec.rb

@@ -0,0 +1,76 @@
+=begin
+#MX Platform API
+
+#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.  Just getting started? See our [use case guides](/use-cases/). 
+
+The version of the OpenAPI document: 20111101
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.8.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MxPlatformRuby::VerifiableCredentialsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'VerifiableCredentialsApi' do
+  before do
+    # run before each test
+    @api_instance = MxPlatformRuby::VerifiableCredentialsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of VerifiableCredentialsApi' do
+    it 'should create an instance of VerifiableCredentialsApi' do
+      expect(@api_instance).to be_instance_of(MxPlatformRuby::VerifiableCredentialsApi)
+    end
+  end
+
+  # unit tests for get_accounts_data
+  # Get Accounts Data
+  # Get an MX-issued verifiable credential of a user's accounts data.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param member_guid The unique id for a `member`.
+  # @param [Hash] opts the optional parameters
+  # @return [VCResponse]
+  describe 'get_accounts_data test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_identity_data
+  # Get Identity Data
+  # Get an MX-issued verifiable credential of a user's identity data.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param member_guid The unique id for a `member`.
+  # @param [Hash] opts the optional parameters
+  # @return [VCResponse]
+  describe 'get_identity_data test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_transactions_data
+  # Get Transactions Data
+  # Get an MX-issued verifiable credential of a user's transaction data.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param account_guid The unique id for an `account`.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :start_time Filter transactions from this date. Must be in the format YYYY-MM-DD. The range is limited to 1 year.
+  # @option opts [String] :end_time Filter transactions to this date. Must be in the format YYYY-MM-DD. The range is limited to 1 year.
+  # @return [VCResponse]
+  describe 'get_transactions_data test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/widgets_api_spec.rb

@@ -0,0 +1,81 @@
+=begin
+#MX Platform API
+
+#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.  Just getting started? See our [use case guides](/use-cases/). 
+
+The version of the OpenAPI document: 20111101
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.8.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MxPlatformRuby::WidgetsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'WidgetsApi' do
+  before do
+    # run before each test
+    @api_instance = MxPlatformRuby::WidgetsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of WidgetsApi' do
+    it 'should create an instance of WidgetsApi' do
+      expect(@api_instance).to be_instance_of(MxPlatformRuby::WidgetsApi)
+    end
+  end
+
+  # unit tests for request_connect_widget_url
+  # (Deprecated) Request connect widget URL
+  # This endpoint will return a URL for an embeddable version of MX Connect.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param connect_widget_request_body Optional config options for WebView (is_mobile_webview, current_institution_code, current_member_guid, update_credentials)
+  # @param [Hash] opts the optional parameters
+  # @return [ConnectWidgetResponseBody]
+  describe 'request_connect_widget_url test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for request_o_auth_window_uri
+  # Request oauth window uri
+  # This endpoint will generate an `oauth_window_uri` for the specified `member`.
+  # @param member_guid The unique id for a `member`.
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :client_redirect_url A URL that MX will redirect to at the end of OAuth with additional query parameters. Only available with `referral_source=APP`.
+  # @option opts [String] :enable_app2app This indicates whether OAuth app2app behavior is enabled for institutions that support it. Defaults to `true`. When set to `false`, any `oauth_window_uri` generated will **not** direct the end user to the institution's mobile application. This setting is not persistent. This setting currently only affects Chase institutions.
+  # @option opts [String] :referral_source Must be either `BROWSER` or `APP` depending on the implementation. Defaults to `BROWSER`.
+  # @option opts [Boolean] :skip_aggregation Setting this parameter to `true` will prevent the member from automatically aggregating after being redirected from the authorization page.
+  # @option opts [String] :ui_message_webview_url_scheme A scheme for routing the user back to the application state they were previously in. Only available with `referral_source=APP`.
+  # @return [OAuthWindowResponseBody]
+  describe 'request_o_auth_window_uri test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for request_widget_url
+  # Request widget URL
+  # Get an embeddable URL for integrating a widget into your website or app. The URL expires after ten minutes or upon first use, whichever occurs first. You'll need to obtain a new URL each time the page loads or reloads.  Include the `widget_type` in the request body to specify which widget you want to embed—the Connect Widget, a Personal Financial Management widget, or an Insights widget. Some request parameters are specific to certain widget types.  To embed the Connect Widget, set `widget_type` to `connect_widget`.  For a full list of available widget types, see [Widget Types](/api-reference/platform-api/reference/widgets#widget-types). 
+  # @param user_guid The unique identifier for a `user`, beginning with the prefix `USR-`.
+  # @param widget_request_body The widget url configuration options.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :accept_language The desired language of the widget.
+  # @option opts [String] :x_callback_payload The base64 encoded string defined in this header will be returned in the [Member](/resources/webhooks/member/) and [Member Data Updated](/resources/webhooks/member#member-data-updated) webhooks. This allows you to trace user interactions and workflows initiated externally and internally in the MX Platform. Max 1024 characters.
+  # @return [WidgetResponseBody]
+  describe 'request_widget_url test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/account_create_request_body_spec.rb

@@ -1,9 +1,9 @@
 =begin
 #MX Platform API
 
-#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.
+#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.  Just getting started? See our [use case guides](/use-cases/). 
 
-The version of the OpenAPI document: 0.1.0
+The version of the OpenAPI document: 20111101
 
 Generated by: https://openapi-generator.tech
 Generator version: 7.8.0

data/spec/models/account_create_request_spec.rb

@@ -1,9 +1,9 @@
 =begin
 #MX Platform API
 
-#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.
+#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.  Just getting started? See our [use case guides](/use-cases/). 
 
-The version of the OpenAPI document: 0.1.0
+The version of the OpenAPI document: 20111101
 
 Generated by: https://openapi-generator.tech
 Generator version: 7.8.0

data/spec/models/account_number_response_spec.rb

@@ -1,9 +1,9 @@
 =begin
 #MX Platform API
 
-#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.
+#The MX Platform API is a powerful, fully-featured API designed to make aggregating and enhancing financial data easy and reliable. It can seamlessly connect your app or website to tens of thousands of financial institutions.  Just getting started? See our [use case guides](/use-cases/). 
 
-The version of the OpenAPI document: 0.1.0
+The version of the OpenAPI document: 20111101
 
 Generated by: https://openapi-generator.tech
 Generator version: 7.8.0
@@ -45,19 +45,19 @@ describe MxPlatformRuby::AccountNumberResponse do
     end
   end
 
-  describe 'test attribute "loan_guarantor"' do
+  describe 'test attribute "institution_number"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  describe 'test attribute "loan_reference_number"' do
+  describe 'test attribute "loan_guarantor"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  describe 'test attribute "institution_number"' do
+  describe 'test attribute "loan_reference_number"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end