melio-platform-api-client 3.0.1

data/spec/api/delivery_methods_api_spec.rb

@@ -0,0 +1,115 @@
+=begin
+#Platform API
+
+#Melio Platform API enables partners to perform partner-related operations in Melio's system, for themselves, and on behalf of their system's users.  ## Definitions & entities #### Partner Represents a party that has high-level access level and can manage Accounts and performing action on them. Partners authenticate using a Partner secret API key, and are permitted to perform only on Accounts that belong to them.  #### Account Represents a business / company that is connected to the Partners system. Partners can have multiple Accounts.  #### Delivery Method A payment destination that is used to receive funds. Accounts can have multiple Delivery Methods.  #### Funding Source A payment source that is used to send funds. Accounts can have multiple Funding Sources.  #### Vendor A business entity that can receive funds from an Account. Vendors are Account-specific.  #### Payment Intent This main entity holds the general bill information (e.g. amount to pay, Vendor to pay to, due date, etc.), and acts as a utility / factory for creating Payments with selected configuration.  #### Payment This core entity facilitates Melio's main use case of transferring funds *from* an Account's Delivery Method *to* a Vendor / Account's Delivery Method on a certain date, along with additional relevant information.  #### Merchant Represents an Account's configuration as a seller, along with its additional data and options.  #### Checkout Represents a checkout session that is performed by the buyer, along with the cart and additional required details.  #### Charge Represnets a charging order for a Checkout, created when a Checkout is captured.  #### FileInfo Wraps around a file in the platform - generic and can be uplaoded and associated with other objects per request.  ## `Melio-Account` header The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It conains the Account'd ID which returned when creating the Account, or when retrieving all of the Partner's Accounts.  Note that most operations are not permitted without the presence of this header. 
+
+The version of the OpenAPI document: 1.0
+Contact: platform@melio.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.1
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MelioPlatformApiClient::DeliveryMethodsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'DeliveryMethodsApi' do
+  before do
+    # run before each test
+    @api_instance = MelioPlatformApiClient::DeliveryMethodsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of DeliveryMethodsApi' do
+    it 'should create an instance of DeliveryMethodsApi' do
+      expect(@api_instance).to be_instance_of(MelioPlatformApiClient::DeliveryMethodsApi)
+    end
+  end
+
+  # unit tests for delete_delivery_methods_delivery_method_id
+  # Delete a Delivery Method
+  # Remove a Delivery Method from the Account
+  # @param delivery_method_id 
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [DeletedResponse]
+  describe 'delete_delivery_methods_delivery_method_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_delivery_methods
+  # Retrieve all Delivery Methods
+  # Retrieve a list of all Delivery Methods the Account has
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetDeliveryMethodsResponse]
+  describe 'get_delivery_methods test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_delivery_methods_delivery_method_id
+  # Retrieve a Delivery Method
+  # Retrieve the details about a specific Delivery Method the Account has
+  # @param delivery_method_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetDeliveryMethodsDeliveryMethodIdResponse]
+  describe 'get_delivery_methods_delivery_method_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_vendors_vendor_id_delivery_methods
+  # Retrieve a Vendor's Delivery Methods
+  # Get a list of a Vendor's Delivery Methods, that can be used to sent funds to.
+  # @param vendor_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetVendorsVendorIdDeliveryMethodsResponse]
+  describe 'get_vendors_vendor_id_delivery_methods test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_delivery_methods
+  # Create a Delivery Method
+  # Add a new Delivery Method for the Account.  The `type` field determines the contents of the `details` field, according to the following mapping: * `bank-account` => `BankAccount` * `paper-check` => `PaperCheck` * `virtual-account` => `VirtualAccount`
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PostDeliveryMethodsRequest] :post_delivery_methods_request 
+  # @return [PostDeliveryMethodsResponse]
+  describe 'post_delivery_methods test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_vendors_vendor_id_delivery_methods
+  # Create a Vendor's Delivery Method
+  # @param vendor_id 
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PostDeliveryMethodsRequest] :body 
+  # @return [PostVendorsVendorIdDeliveryMethodsResponse]
+  describe 'post_vendors_vendor_id_delivery_methods test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/files_api_spec.rb

@@ -0,0 +1,85 @@
+=begin
+#Platform API
+
+#Melio Platform API enables partners to perform partner-related operations in Melio's system, for themselves, and on behalf of their system's users.  ## Definitions & entities #### Partner Represents a party that has high-level access level and can manage Accounts and performing action on them. Partners authenticate using a Partner secret API key, and are permitted to perform only on Accounts that belong to them.  #### Account Represents a business / company that is connected to the Partners system. Partners can have multiple Accounts.  #### Delivery Method A payment destination that is used to receive funds. Accounts can have multiple Delivery Methods.  #### Funding Source A payment source that is used to send funds. Accounts can have multiple Funding Sources.  #### Vendor A business entity that can receive funds from an Account. Vendors are Account-specific.  #### Payment Intent This main entity holds the general bill information (e.g. amount to pay, Vendor to pay to, due date, etc.), and acts as a utility / factory for creating Payments with selected configuration.  #### Payment This core entity facilitates Melio's main use case of transferring funds *from* an Account's Delivery Method *to* a Vendor / Account's Delivery Method on a certain date, along with additional relevant information.  #### Merchant Represents an Account's configuration as a seller, along with its additional data and options.  #### Checkout Represents a checkout session that is performed by the buyer, along with the cart and additional required details.  #### Charge Represnets a charging order for a Checkout, created when a Checkout is captured.  #### FileInfo Wraps around a file in the platform - generic and can be uplaoded and associated with other objects per request.  ## `Melio-Account` header The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It conains the Account'd ID which returned when creating the Account, or when retrieving all of the Partner's Accounts.  Note that most operations are not permitted without the presence of this header. 
+
+The version of the OpenAPI document: 1.0
+Contact: platform@melio.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.1
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MelioPlatformApiClient::FilesApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'FilesApi' do
+  before do
+    # run before each test
+    @api_instance = MelioPlatformApiClient::FilesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of FilesApi' do
+    it 'should create an instance of FilesApi' do
+      expect(@api_instance).to be_instance_of(MelioPlatformApiClient::FilesApi)
+    end
+  end
+
+  # unit tests for get_files
+  # Retrieve files
+  # Retrieve the list of Files the Account uploaded to Melio
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetFilesResponse]
+  describe 'get_files test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_files_file_id
+  # Retrieve a File
+  # Get a File object with a details and a URL for the actual file to download.
+  # @param file_id 
+  # @param [Hash] opts the optional parameters
+  # @return [GetFilesFileIdResponse]
+  describe 'get_files_file_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_files_file_id_data
+  # Retrieve data from a File using OCR
+  # @param file_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetFilesFileIdDataResponse]
+  describe 'get_files_file_id_data test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_files
+  # Create / upload a File
+  # Upload a file as a File object, to be used by other operations
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [File] :file 
+  # @return [PostFilesResponse]
+  describe 'post_files test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/financing_api_spec.rb

@@ -0,0 +1,75 @@
+=begin
+#Platform API
+
+#Melio Platform API enables partners to perform partner-related operations in Melio's system, for themselves, and on behalf of their system's users.  ## Definitions & entities #### Partner Represents a party that has high-level access level and can manage Accounts and performing action on them. Partners authenticate using a Partner secret API key, and are permitted to perform only on Accounts that belong to them.  #### Account Represents a business / company that is connected to the Partners system. Partners can have multiple Accounts.  #### Delivery Method A payment destination that is used to receive funds. Accounts can have multiple Delivery Methods.  #### Funding Source A payment source that is used to send funds. Accounts can have multiple Funding Sources.  #### Vendor A business entity that can receive funds from an Account. Vendors are Account-specific.  #### Payment Intent This main entity holds the general bill information (e.g. amount to pay, Vendor to pay to, due date, etc.), and acts as a utility / factory for creating Payments with selected configuration.  #### Payment This core entity facilitates Melio's main use case of transferring funds *from* an Account's Delivery Method *to* a Vendor / Account's Delivery Method on a certain date, along with additional relevant information.  #### Merchant Represents an Account's configuration as a seller, along with its additional data and options.  #### Checkout Represents a checkout session that is performed by the buyer, along with the cart and additional required details.  #### Charge Represnets a charging order for a Checkout, created when a Checkout is captured.  #### FileInfo Wraps around a file in the platform - generic and can be uplaoded and associated with other objects per request.  ## `Melio-Account` header The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It conains the Account'd ID which returned when creating the Account, or when retrieving all of the Partner's Accounts.  Note that most operations are not permitted without the presence of this header. 
+
+The version of the OpenAPI document: 1.0
+Contact: platform@melio.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.1
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MelioPlatformApiClient::FinancingApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'FinancingApi' do
+  before do
+    # run before each test
+    @api_instance = MelioPlatformApiClient::FinancingApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of FinancingApi' do
+    it 'should create an instance of FinancingApi' do
+      expect(@api_instance).to be_instance_of(MelioPlatformApiClient::FinancingApi)
+    end
+  end
+
+  # unit tests for get_financing_status
+  # Retrieve an Account's financing status
+  # Return the current status and balance of an account's financing qualification. The account may be in one of a few steps, defined by the response's `status` enum: - Undetermined (`undetermined` status): The account hasn't qualified yet, or the qualification has expired - Pending (`pending` status): The account has requested qualification, and awaiting for response. - Ineligible (`ineligible` status): The account is currently not eligible for financing. - Eligible (`eligible` status): The account is eligibile for financing. In this case, the additional `balance` field would be populated with the remaining credit balance.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetFinancingResponse]
+  describe 'get_financing_status test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_financing
+  # Apply for financing for an Account
+  # Accounts that wish to use financing must qualify for it. Call this method with values collected based on the result of `GET /financing`  This operation may take a long time (30 seconds).
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PostFinancingRequest] :post_financing_request 
+  # @return [PostFinancingResponse]
+  describe 'post_financing test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_financing_transaction
+  # Request Transactional Financing
+  # An eligible Account must request transactional approval for each financed transaction they intend to perform. The result of this operation returns a token that should be used when completing other payments through Melio.  This operation may take a long time (10 seconds).
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PostFinancingTransactionalRequest] :post_financing_transactional_request 
+  # @return [PostFinancingTransactionalResponse]
+  describe 'post_financing_transaction test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/funding_sources_api_spec.rb

@@ -0,0 +1,88 @@
+=begin
+#Platform API
+
+#Melio Platform API enables partners to perform partner-related operations in Melio's system, for themselves, and on behalf of their system's users.  ## Definitions & entities #### Partner Represents a party that has high-level access level and can manage Accounts and performing action on them. Partners authenticate using a Partner secret API key, and are permitted to perform only on Accounts that belong to them.  #### Account Represents a business / company that is connected to the Partners system. Partners can have multiple Accounts.  #### Delivery Method A payment destination that is used to receive funds. Accounts can have multiple Delivery Methods.  #### Funding Source A payment source that is used to send funds. Accounts can have multiple Funding Sources.  #### Vendor A business entity that can receive funds from an Account. Vendors are Account-specific.  #### Payment Intent This main entity holds the general bill information (e.g. amount to pay, Vendor to pay to, due date, etc.), and acts as a utility / factory for creating Payments with selected configuration.  #### Payment This core entity facilitates Melio's main use case of transferring funds *from* an Account's Delivery Method *to* a Vendor / Account's Delivery Method on a certain date, along with additional relevant information.  #### Merchant Represents an Account's configuration as a seller, along with its additional data and options.  #### Checkout Represents a checkout session that is performed by the buyer, along with the cart and additional required details.  #### Charge Represnets a charging order for a Checkout, created when a Checkout is captured.  #### FileInfo Wraps around a file in the platform - generic and can be uplaoded and associated with other objects per request.  ## `Melio-Account` header The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It conains the Account'd ID which returned when creating the Account, or when retrieving all of the Partner's Accounts.  Note that most operations are not permitted without the presence of this header. 
+
+The version of the OpenAPI document: 1.0
+Contact: platform@melio.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.1
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MelioPlatformApiClient::FundingSourcesApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'FundingSourcesApi' do
+  before do
+    # run before each test
+    @api_instance = MelioPlatformApiClient::FundingSourcesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of FundingSourcesApi' do
+    it 'should create an instance of FundingSourcesApi' do
+      expect(@api_instance).to be_instance_of(MelioPlatformApiClient::FundingSourcesApi)
+    end
+  end
+
+  # unit tests for delete_funding_sources_funding_source_id
+  # Delete a Funding Source
+  # Remove a Funding Source from the Account
+  # @param funding_source_id 
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [DeletedResponse]
+  describe 'delete_funding_sources_funding_source_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_funding_sources
+  # Get all Funding Sources
+  # Retrieve the Funding Sources of an Account
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetFundingSourcesResponse]
+  describe 'get_funding_sources test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_funding_sources_funding_source_id
+  # Retrieve a Funding Source
+  # Retrieve details about a specific Funding Source
+  # @param funding_source_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetFundingSourcesFundingSourceIdResponse]
+  describe 'get_funding_sources_funding_source_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_funding_sources
+  # Create a Funding Source
+  # Create a new Funding Source for the Account.  The `type` field determines the contents of the `details` field, according to the following mapping: * `bank-account` => `BankAccount` * `plaid` => `PlaidDetails` * `card` => `Card`
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PostFundingSourcesRequest] :post_funding_sources_request 
+  # @return [PostFundingSourcesResponse]
+  describe 'post_funding_sources test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/merchants_api_spec.rb

@@ -0,0 +1,49 @@
+=begin
+#Platform API
+
+#Melio Platform API enables partners to perform partner-related operations in Melio's system, for themselves, and on behalf of their system's users.  ## Definitions & entities #### Partner Represents a party that has high-level access level and can manage Accounts and performing action on them. Partners authenticate using a Partner secret API key, and are permitted to perform only on Accounts that belong to them.  #### Account Represents a business / company that is connected to the Partners system. Partners can have multiple Accounts.  #### Delivery Method A payment destination that is used to receive funds. Accounts can have multiple Delivery Methods.  #### Funding Source A payment source that is used to send funds. Accounts can have multiple Funding Sources.  #### Vendor A business entity that can receive funds from an Account. Vendors are Account-specific.  #### Payment Intent This main entity holds the general bill information (e.g. amount to pay, Vendor to pay to, due date, etc.), and acts as a utility / factory for creating Payments with selected configuration.  #### Payment This core entity facilitates Melio's main use case of transferring funds *from* an Account's Delivery Method *to* a Vendor / Account's Delivery Method on a certain date, along with additional relevant information.  #### Merchant Represents an Account's configuration as a seller, along with its additional data and options.  #### Checkout Represents a checkout session that is performed by the buyer, along with the cart and additional required details.  #### Charge Represnets a charging order for a Checkout, created when a Checkout is captured.  #### FileInfo Wraps around a file in the platform - generic and can be uplaoded and associated with other objects per request.  ## `Melio-Account` header The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It conains the Account'd ID which returned when creating the Account, or when retrieving all of the Partner's Accounts.  Note that most operations are not permitted without the presence of this header. 
+
+The version of the OpenAPI document: 1.0
+Contact: platform@melio.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.1
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MelioPlatformApiClient::MerchantsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'MerchantsApi' do
+  before do
+    # run before each test
+    @api_instance = MelioPlatformApiClient::MerchantsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of MerchantsApi' do
+    it 'should create an instance of MerchantsApi' do
+      expect(@api_instance).to be_instance_of(MelioPlatformApiClient::MerchantsApi)
+    end
+  end
+
+  # unit tests for post_merchants
+  # Create a Merchant
+  # Create a new Merchant for the Account
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PostMerchantsRequest] :post_merchants_request 
+  # @return [PostMerchantsResponse]
+  describe 'post_merchants test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/payment_intents_api_spec.rb

@@ -0,0 +1,114 @@
+=begin
+#Platform API
+
+#Melio Platform API enables partners to perform partner-related operations in Melio's system, for themselves, and on behalf of their system's users.  ## Definitions & entities #### Partner Represents a party that has high-level access level and can manage Accounts and performing action on them. Partners authenticate using a Partner secret API key, and are permitted to perform only on Accounts that belong to them.  #### Account Represents a business / company that is connected to the Partners system. Partners can have multiple Accounts.  #### Delivery Method A payment destination that is used to receive funds. Accounts can have multiple Delivery Methods.  #### Funding Source A payment source that is used to send funds. Accounts can have multiple Funding Sources.  #### Vendor A business entity that can receive funds from an Account. Vendors are Account-specific.  #### Payment Intent This main entity holds the general bill information (e.g. amount to pay, Vendor to pay to, due date, etc.), and acts as a utility / factory for creating Payments with selected configuration.  #### Payment This core entity facilitates Melio's main use case of transferring funds *from* an Account's Delivery Method *to* a Vendor / Account's Delivery Method on a certain date, along with additional relevant information.  #### Merchant Represents an Account's configuration as a seller, along with its additional data and options.  #### Checkout Represents a checkout session that is performed by the buyer, along with the cart and additional required details.  #### Charge Represnets a charging order for a Checkout, created when a Checkout is captured.  #### FileInfo Wraps around a file in the platform - generic and can be uplaoded and associated with other objects per request.  ## `Melio-Account` header The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It conains the Account'd ID which returned when creating the Account, or when retrieving all of the Partner's Accounts.  Note that most operations are not permitted without the presence of this header. 
+
+The version of the OpenAPI document: 1.0
+Contact: platform@melio.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.1
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MelioPlatformApiClient::PaymentIntentsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'PaymentIntentsApi' do
+  before do
+    # run before each test
+    @api_instance = MelioPlatformApiClient::PaymentIntentsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of PaymentIntentsApi' do
+    it 'should create an instance of PaymentIntentsApi' do
+      expect(@api_instance).to be_instance_of(MelioPlatformApiClient::PaymentIntentsApi)
+    end
+  end
+
+  # unit tests for get_payment_intents
+  # Retrieve all Payment Intents
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetPaymentIntentsResponse]
+  describe 'get_payment_intents test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_payment_intents_payment_intent_id
+  # Retrieve a Payment Intent
+  # @param payment_intent_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetPaymentIntentsPaymentIntentIdResponse]
+  describe 'get_payment_intents_payment_intent_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for patch_payment_intents_payment_intent_id
+  # Update a Payment Intent
+  # Update an existing Payment Intent.  The request's body can be partial, and only provided fields will be overwritten. Set a field to `null` in order to remove its contents.
+  # @param payment_intent_id 
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PatchPaymentIntentsPaymentIntentIdRequest] :patch_payment_intents_payment_intent_id_request 
+  # @return [PatchPaymentIntentsPaymentIntentIdResponse]
+  describe 'patch_payment_intents_payment_intent_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_payment_intents
+  # Create a Payment Intent
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PostPaymentIntentsRequest] :post_payment_intents_request 
+  # @return [PostPaymentIntentsResponse]
+  describe 'post_payment_intents test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_payment_intents_bulk
+  # Create multiple Payment Intents
+  # Create multiple Payment Intents based on a provided list.
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [PostPaymentIntentsBulkRequest] :post_payment_intents_bulk_request 
+  # @return [PostPaymentIntentsBulkResponse]
+  describe 'post_payment_intents_bulk test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for post_payment_intents_payment_intent_id_confirm
+  # Confirm a Payment Intent
+  # Confirm this Payment Intent and produce a Payment based on the current configuration.
+  # @param payment_intent_id 
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [PostPaymentIntentsPaymentIntentIdPaymentResponse]
+  describe 'post_payment_intents_payment_intent_id_confirm test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/payments_api_spec.rb

@@ -0,0 +1,88 @@
+=begin
+#Platform API
+
+#Melio Platform API enables partners to perform partner-related operations in Melio's system, for themselves, and on behalf of their system's users.  ## Definitions & entities #### Partner Represents a party that has high-level access level and can manage Accounts and performing action on them. Partners authenticate using a Partner secret API key, and are permitted to perform only on Accounts that belong to them.  #### Account Represents a business / company that is connected to the Partners system. Partners can have multiple Accounts.  #### Delivery Method A payment destination that is used to receive funds. Accounts can have multiple Delivery Methods.  #### Funding Source A payment source that is used to send funds. Accounts can have multiple Funding Sources.  #### Vendor A business entity that can receive funds from an Account. Vendors are Account-specific.  #### Payment Intent This main entity holds the general bill information (e.g. amount to pay, Vendor to pay to, due date, etc.), and acts as a utility / factory for creating Payments with selected configuration.  #### Payment This core entity facilitates Melio's main use case of transferring funds *from* an Account's Delivery Method *to* a Vendor / Account's Delivery Method on a certain date, along with additional relevant information.  #### Merchant Represents an Account's configuration as a seller, along with its additional data and options.  #### Checkout Represents a checkout session that is performed by the buyer, along with the cart and additional required details.  #### Charge Represnets a charging order for a Checkout, created when a Checkout is captured.  #### FileInfo Wraps around a file in the platform - generic and can be uplaoded and associated with other objects per request.  ## `Melio-Account` header The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It conains the Account'd ID which returned when creating the Account, or when retrieving all of the Partner's Accounts.  Note that most operations are not permitted without the presence of this header. 
+
+The version of the OpenAPI document: 1.0
+Contact: platform@melio.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.1
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for MelioPlatformApiClient::PaymentsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'PaymentsApi' do
+  before do
+    # run before each test
+    @api_instance = MelioPlatformApiClient::PaymentsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of PaymentsApi' do
+    it 'should create an instance of PaymentsApi' do
+      expect(@api_instance).to be_instance_of(MelioPlatformApiClient::PaymentsApi)
+    end
+  end
+
+  # unit tests for delete_payments_payment_id
+  # Delete a Payment
+  # Delete / cancel a Payment.
+  # @param payment_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [DeletedResponse]
+  describe 'delete_payments_payment_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_payments
+  # Retrieve all Payments of a PaymentIntent
+  # Retrieve a list of all Payments of a PaymentIntent
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :payment_intent_id 
+  # @return [GetPaymentsResponse]
+  describe 'get_payments test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_payments_payment_id
+  # Retrieve a Payment
+  # Retrieve a Payment using its ID.
+  # @param payment_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @return [GetPaymentsPaymentIdResponse]
+  describe 'get_payments_payment_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recover_payment_payment_id
+  # Recover a Payment
+  # Recover a Payment by providing alternative details, hence restarting the Payment's lifecycle.
+  # @param payment_id 
+  # @param idempotency_key Unique idempotency key
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :melio_account The `Melio-Account` header is used when a Partner wants to perform an operation on behalf of one of its Accounts. It contains the Account's ID which returned when creating the Account, or when retrieving all of the Partner's Accounts. Note that most operations are not permitted without the presence of this header.
+  # @option opts [RecoverPaymentRequest] :recover_payment_request 
+  # @return [RecoverPaymentResponse]
+  describe 'recover_payment_payment_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end