melio-platform-api-client 3.0.1

data/spec/models/get_files_file_id_data_response_data_spec.rb

@@ -0,0 +1,58 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetFilesFileIdDataResponseData
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetFilesFileIdDataResponseData do
+  let(:instance) { MelioPlatformApiClient::GetFilesFileIdDataResponseData.new }
+
+  describe 'test an instance of GetFilesFileIdDataResponseData' do
+    it 'should create an instance of GetFilesFileIdDataResponseData' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetFilesFileIdDataResponseData)
+    end
+  end
+  describe 'test attribute "amount"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "due_date"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "customer_info"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "vendor_info"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "invoice_info"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_files_file_id_data_response_data_vendor_info_spec.rb

@@ -0,0 +1,40 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetFilesFileIdDataResponseDataVendorInfo
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetFilesFileIdDataResponseDataVendorInfo do
+  let(:instance) { MelioPlatformApiClient::GetFilesFileIdDataResponseDataVendorInfo.new }
+
+  describe 'test an instance of GetFilesFileIdDataResponseDataVendorInfo' do
+    it 'should create an instance of GetFilesFileIdDataResponseDataVendorInfo' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetFilesFileIdDataResponseDataVendorInfo)
+    end
+  end
+  describe 'test attribute "name"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "matched_name"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_files_file_id_data_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetFilesFileIdDataResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetFilesFileIdDataResponse do
+  let(:instance) { MelioPlatformApiClient::GetFilesFileIdDataResponse.new }
+
+  describe 'test an instance of GetFilesFileIdDataResponse' do
+    it 'should create an instance of GetFilesFileIdDataResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetFilesFileIdDataResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_files_file_id_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetFilesFileIdResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetFilesFileIdResponse do
+  let(:instance) { MelioPlatformApiClient::GetFilesFileIdResponse.new }
+
+  describe 'test an instance of GetFilesFileIdResponse' do
+    it 'should create an instance of GetFilesFileIdResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetFilesFileIdResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_files_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetFilesResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetFilesResponse do
+  let(:instance) { MelioPlatformApiClient::GetFilesResponse.new }
+
+  describe 'test an instance of GetFilesResponse' do
+    it 'should create an instance of GetFilesResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetFilesResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_financing_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetFinancingResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetFinancingResponse do
+  let(:instance) { MelioPlatformApiClient::GetFinancingResponse.new }
+
+  describe 'test an instance of GetFinancingResponse' do
+    it 'should create an instance of GetFinancingResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetFinancingResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_funding_sources_funding_source_id_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetFundingSourcesFundingSourceIdResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetFundingSourcesFundingSourceIdResponse do
+  let(:instance) { MelioPlatformApiClient::GetFundingSourcesFundingSourceIdResponse.new }
+
+  describe 'test an instance of GetFundingSourcesFundingSourceIdResponse' do
+    it 'should create an instance of GetFundingSourcesFundingSourceIdResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetFundingSourcesFundingSourceIdResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_funding_sources_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetFundingSourcesResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetFundingSourcesResponse do
+  let(:instance) { MelioPlatformApiClient::GetFundingSourcesResponse.new }
+
+  describe 'test an instance of GetFundingSourcesResponse' do
+    it 'should create an instance of GetFundingSourcesResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetFundingSourcesResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_payment_intents_payment_intent_id_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetPaymentIntentsPaymentIntentIdResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetPaymentIntentsPaymentIntentIdResponse do
+  let(:instance) { MelioPlatformApiClient::GetPaymentIntentsPaymentIntentIdResponse.new }
+
+  describe 'test an instance of GetPaymentIntentsPaymentIntentIdResponse' do
+    it 'should create an instance of GetPaymentIntentsPaymentIntentIdResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetPaymentIntentsPaymentIntentIdResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_payment_intents_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetPaymentIntentsResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetPaymentIntentsResponse do
+  let(:instance) { MelioPlatformApiClient::GetPaymentIntentsResponse.new }
+
+  describe 'test an instance of GetPaymentIntentsResponse' do
+    it 'should create an instance of GetPaymentIntentsResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetPaymentIntentsResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_payments_payment_id_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetPaymentsPaymentIdResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetPaymentsPaymentIdResponse do
+  let(:instance) { MelioPlatformApiClient::GetPaymentsPaymentIdResponse.new }
+
+  describe 'test an instance of GetPaymentsPaymentIdResponse' do
+    it 'should create an instance of GetPaymentsPaymentIdResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetPaymentsPaymentIdResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_payments_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetPaymentsResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetPaymentsResponse do
+  let(:instance) { MelioPlatformApiClient::GetPaymentsResponse.new }
+
+  describe 'test an instance of GetPaymentsResponse' do
+    it 'should create an instance of GetPaymentsResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetPaymentsResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_vendor_directory_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetVendorDirectoryResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetVendorDirectoryResponse do
+  let(:instance) { MelioPlatformApiClient::GetVendorDirectoryResponse.new }
+
+  describe 'test an instance of GetVendorDirectoryResponse' do
+    it 'should create an instance of GetVendorDirectoryResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetVendorDirectoryResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_vendors_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetVendorsResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetVendorsResponse do
+  let(:instance) { MelioPlatformApiClient::GetVendorsResponse.new }
+
+  describe 'test an instance of GetVendorsResponse' do
+    it 'should create an instance of GetVendorsResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetVendorsResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_vendors_vendor_id_delivery_methods_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetVendorsVendorIdDeliveryMethodsResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetVendorsVendorIdDeliveryMethodsResponse do
+  let(:instance) { MelioPlatformApiClient::GetVendorsVendorIdDeliveryMethodsResponse.new }
+
+  describe 'test an instance of GetVendorsVendorIdDeliveryMethodsResponse' do
+    it 'should create an instance of GetVendorsVendorIdDeliveryMethodsResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetVendorsVendorIdDeliveryMethodsResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/get_vendors_vendor_id_response_spec.rb

@@ -0,0 +1,34 @@
+=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'
+require 'date'
+
+# Unit tests for MelioPlatformApiClient::GetVendorsVendorIdResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::GetVendorsVendorIdResponse do
+  let(:instance) { MelioPlatformApiClient::GetVendorsVendorIdResponse.new }
+
+  describe 'test an instance of GetVendorsVendorIdResponse' do
+    it 'should create an instance of GetVendorsVendorIdResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::GetVendorsVendorIdResponse)
+    end
+  end
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end