melio-platform-api-client 3.0.1

data/spec/models/post_payments_payment_id_recover_request_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::PostPaymentsPaymentIdRecoverRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostPaymentsPaymentIdRecoverRequest do
+  let(:instance) { MelioPlatformApiClient::PostPaymentsPaymentIdRecoverRequest.new }
+
+  describe 'test an instance of PostPaymentsPaymentIdRecoverRequest' do
+    it 'should create an instance of PostPaymentsPaymentIdRecoverRequest' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostPaymentsPaymentIdRecoverRequest)
+    end
+  end
+  describe 'test attribute "funding_source_id"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "delivery_method_id"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "note"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "scheduled_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 "selected_delivery_preference"' 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/post_payments_payment_id_recover_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::PostPaymentsPaymentIdRecoverResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostPaymentsPaymentIdRecoverResponse do
+  let(:instance) { MelioPlatformApiClient::PostPaymentsPaymentIdRecoverResponse.new }
+
+  describe 'test an instance of PostPaymentsPaymentIdRecoverResponse' do
+    it 'should create an instance of PostPaymentsPaymentIdRecoverResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostPaymentsPaymentIdRecoverResponse)
+    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/post_vendors_bulk_request_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::PostVendorsBulkRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostVendorsBulkRequest do
+  let(:instance) { MelioPlatformApiClient::PostVendorsBulkRequest.new }
+
+  describe 'test an instance of PostVendorsBulkRequest' do
+    it 'should create an instance of PostVendorsBulkRequest' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostVendorsBulkRequest)
+    end
+  end
+  describe 'test attribute "vendors"' 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/post_vendors_bulk_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::PostVendorsBulkResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostVendorsBulkResponse do
+  let(:instance) { MelioPlatformApiClient::PostVendorsBulkResponse.new }
+
+  describe 'test an instance of PostVendorsBulkResponse' do
+    it 'should create an instance of PostVendorsBulkResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostVendorsBulkResponse)
+    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/post_vendors_from_vendor_directory_request_delivery_method_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::PostVendorsFromVendorDirectoryRequestDeliveryMethod
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostVendorsFromVendorDirectoryRequestDeliveryMethod do
+  let(:instance) { MelioPlatformApiClient::PostVendorsFromVendorDirectoryRequestDeliveryMethod.new }
+
+  describe 'test an instance of PostVendorsFromVendorDirectoryRequestDeliveryMethod' do
+    it 'should create an instance of PostVendorsFromVendorDirectoryRequestDeliveryMethod' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostVendorsFromVendorDirectoryRequestDeliveryMethod)
+    end
+  end
+  describe 'test attribute "type"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "biller_account_identifier"' 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/post_vendors_from_vendor_directory_request_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::PostVendorsFromVendorDirectoryRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostVendorsFromVendorDirectoryRequest do
+  let(:instance) { MelioPlatformApiClient::PostVendorsFromVendorDirectoryRequest.new }
+
+  describe 'test an instance of PostVendorsFromVendorDirectoryRequest' do
+    it 'should create an instance of PostVendorsFromVendorDirectoryRequest' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostVendorsFromVendorDirectoryRequest)
+    end
+  end
+  describe 'test attribute "vendor_directory_id"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "delivery_method"' 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/post_vendors_from_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::PostVendorsFromVendorDirectoryResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostVendorsFromVendorDirectoryResponse do
+  let(:instance) { MelioPlatformApiClient::PostVendorsFromVendorDirectoryResponse.new }
+
+  describe 'test an instance of PostVendorsFromVendorDirectoryResponse' do
+    it 'should create an instance of PostVendorsFromVendorDirectoryResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostVendorsFromVendorDirectoryResponse)
+    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/post_vendors_request_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::PostVendorsRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostVendorsRequest do
+  let(:instance) { MelioPlatformApiClient::PostVendorsRequest.new }
+
+  describe 'test an instance of PostVendorsRequest' do
+    it 'should create an instance of PostVendorsRequest' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostVendorsRequest)
+    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 "contact"' 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/post_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::PostVendorsResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostVendorsResponse do
+  let(:instance) { MelioPlatformApiClient::PostVendorsResponse.new }
+
+  describe 'test an instance of PostVendorsResponse' do
+    it 'should create an instance of PostVendorsResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostVendorsResponse)
+    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/post_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::PostVendorsVendorIdDeliveryMethodsResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostVendorsVendorIdDeliveryMethodsResponse do
+  let(:instance) { MelioPlatformApiClient::PostVendorsVendorIdDeliveryMethodsResponse.new }
+
+  describe 'test an instance of PostVendorsVendorIdDeliveryMethodsResponse' do
+    it 'should create an instance of PostVendorsVendorIdDeliveryMethodsResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostVendorsVendorIdDeliveryMethodsResponse)
+    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/post_webhooks_checkouts_request_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::PostWebhooksCheckoutsRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostWebhooksCheckoutsRequest do
+  let(:instance) { MelioPlatformApiClient::PostWebhooksCheckoutsRequest.new }
+
+  describe 'test an instance of PostWebhooksCheckoutsRequest' do
+    it 'should create an instance of PostWebhooksCheckoutsRequest' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostWebhooksCheckoutsRequest)
+    end
+  end
+  describe 'test attribute "url"' 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/post_webhooks_checkouts_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::PostWebhooksCheckoutsResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostWebhooksCheckoutsResponse do
+  let(:instance) { MelioPlatformApiClient::PostWebhooksCheckoutsResponse.new }
+
+  describe 'test an instance of PostWebhooksCheckoutsResponse' do
+    it 'should create an instance of PostWebhooksCheckoutsResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostWebhooksCheckoutsResponse)
+    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/post_webhooks_payments_request_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::PostWebhooksPaymentsRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostWebhooksPaymentsRequest do
+  let(:instance) { MelioPlatformApiClient::PostWebhooksPaymentsRequest.new }
+
+  describe 'test an instance of PostWebhooksPaymentsRequest' do
+    it 'should create an instance of PostWebhooksPaymentsRequest' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostWebhooksPaymentsRequest)
+    end
+  end
+  describe 'test attribute "url"' 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/post_webhooks_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::PostWebhooksPaymentsResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe MelioPlatformApiClient::PostWebhooksPaymentsResponse do
+  let(:instance) { MelioPlatformApiClient::PostWebhooksPaymentsResponse.new }
+
+  describe 'test an instance of PostWebhooksPaymentsResponse' do
+    it 'should create an instance of PostWebhooksPaymentsResponse' do
+      expect(instance).to be_instance_of(MelioPlatformApiClient::PostWebhooksPaymentsResponse)
+    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