crypto_apis 1.0.0 → 1.1.0

data/lib/crypto_apis/models/xpub_not_synced.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 

data/lib/crypto_apis/models/xpub_not_synced_error.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 

data/lib/crypto_apis/models/xpub_sync_in_progress.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 

data/lib/crypto_apis/models/xpub_sync_in_progress_error.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 

data/lib/crypto_apis/version.rb

@@ -6,10 +6,10 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
 module CryptoApis
-  VERSION = '1.0.0'
+  VERSION = '1.1.0'
 end

data/spec/api/assets_api_spec.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
@@ -34,12 +34,14 @@ describe 'AssetsApi' do
 
   # unit tests for list_assets_details
   # List Assets Details
-  # This endpoint will return details on a requested asset. The asset could be a cryptocurrency or FIAT asset that we support. Each asset has a unique identifier - `assetId` and a unique symbol in the form of a string, e.g. \"BTC\".    The details returned could include information on the latest rate and rate fluctuation of different periods of time - 24 hours, a week, one hour, the encoding of the logo, and more.
+  # This endpoint will return details on a requested asset. The asset could be a cryptocurrency or FIAT asset that we support. Each asset has a unique identifier - `assetId` and a unique symbol in the form of a string, e.g. \"BTC\".    The details returned could include information on the latest rate and rate fluctuation of different periods of time - 24 hours, a week, one hour, the encoding of the logo, and more.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
   # @param [Hash] opts the optional parameters
   # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
   # @option opts [String] :asset_type Defines the type of the supported asset. This could be either \"crypto\" or \"fiat\".
+  # @option opts [String] :crypto_type Subtype of the crypto assets. Could be COIN or TOKEN
   # @option opts [Integer] :limit Defines how many items should be returned in the response per page basis.
   # @option opts [Integer] :offset The starting index of the response items, i.e. where the response should start listing the returned items.
+  # @option opts [Boolean] :waas_enabled Show only if WaaS is/not enabled
   # @return [ListAssetsDetailsR]
   describe 'list_assets_details test' do
     it 'should work' do

data/spec/api/automatic_coins_forwarding_api_spec.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
@@ -64,7 +64,7 @@ describe 'AutomaticCoinsForwardingApi' do
 
   # unit tests for list_coins_forwarding_automations
   # List Coins Forwarding Automations
-  # Through this endpoint customers can list all of their **coins** forwarding automations (**not** tokens).    Customers can set up automatic forwarding functions for coins by setting a `fromAddress` and a `toAddress`, and specifying the amount that can be transferred between addresses.     A `feePriority` will be returned which represents the fee priority of the automation whether it is \"SLOW\", \"STANDARD\" OR \"FAST\".    {warning}The subscription will work for all incoming transactions until it is deleted. There is no need to do that for every transaction.{/warning}
+  # Through this endpoint customers can list all of their **coins** forwarding automations (**not** tokens).    Customers can set up automatic forwarding functions for coins by setting a `fromAddress` and a `toAddress`, and specifying the amount that can be transferred between addresses.     A `feePriority` will be returned which represents the fee priority of the automation whether it is \"SLOW\", \"STANDARD\" OR \"FAST\".    {warning}The subscription will work for all incoming transactions until it is deleted. There is no need to do that for every transaction.{/warning}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
   # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
   # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
   # @param [Hash] opts the optional parameters

data/spec/api/automatic_tokens_forwarding_api_spec.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
@@ -93,7 +93,7 @@ describe 'AutomaticTokensForwardingApi' do
 
   # unit tests for list_tokens_forwarding_automations
   # List Tokens Forwarding Automations
-  # Through this endpoint customers can list all of their **tokens** forwarding automations (**not** coins).    Customers can set up automatic forwarding functions for tokens by setting a `fromAddress` and a `toAddress`, and specifying the amount that can be transferred between addresses.     A `feePriority` will be returned which represents the fee priority of the automation whether it is \"SLOW\", \"STANDARD\" OR \"FAST\".     {warning}The subscription will work for all incoming transactions until it is deleted. There is no need to do that for every transaction.{/warning}
+  # Through this endpoint customers can list all of their **tokens** forwarding automations (**not** coins).    Customers can set up automatic forwarding functions for tokens by setting a `fromAddress` and a `toAddress`, and specifying the amount that can be transferred between addresses.     A `feePriority` will be returned which represents the fee priority of the automation whether it is \"SLOW\", \"STANDARD\" OR \"FAST\".     {warning}The subscription will work for all incoming transactions until it is deleted. There is no need to do that for every transaction.{/warning}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
   # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
   # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
   # @param [Hash] opts the optional parameters

data/spec/api/create_subscriptions_for_api_spec.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
@@ -92,6 +92,36 @@ describe 'CreateSubscriptionsForApi' do
     end
   end
 
+  # unit tests for new_confirmed_internal_transactions
+  # New confirmed internal transactions
+  # Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new confirmed internal transactions. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs.    Being confirmed means that the transactions are verified by miners and added to the next block.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @option opts [NewConfirmedInternalTransactionsRB] :new_confirmed_internal_transactions_rb 
+  # @return [NewConfirmedInternalTransactionsR]
+  describe 'new_confirmed_internal_transactions test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for new_confirmed_internal_transactions_and_each_confirmation
+  # New confirmed internal transactions and each confirmation
+  # Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new confirmed internal transactions. Includes also a response at each confirmation the transaction receives until the specified confirmations limit is reached. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs.     Being confirmed means that the transactions are verified by miners and added to the next block.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @option opts [NewConfirmedInternalTransactionsAndEachConfirmationRB] :new_confirmed_internal_transactions_and_each_confirmation_rb 
+  # @return [NewConfirmedInternalTransactionsAndEachConfirmationR]
+  describe 'new_confirmed_internal_transactions_and_each_confirmation test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for new_confirmed_tokens_transactions
   # New confirmed tokens transactions
   # Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new incoming or outgoing confirmed transactions for tokens from/to the customer's address. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.     Being confirmed means that the transactions are verified by miners and added to the next block. This endpoint refers to **tokens transactions only, not coins**.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
@@ -124,7 +154,7 @@ describe 'CreateSubscriptionsForApi' do
 
   # unit tests for new_unconfirmed_coins_transactions
   # New unconfirmed coins transactions
-  # Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed coins transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed coins transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+  # Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed coins transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed coins transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {warning}We cannot guarantee at 100% that webhooks for unconfirmed transactions will always be received. Some may **not get received** due to the possibility of some nodes not being updated with that information. This can occur in networks with low activity and/or not many nodes, e.g. Testnet networks and rarely Mainnets.{/warning}    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
   # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
   # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
   # @param [Hash] opts the optional parameters
@@ -139,7 +169,7 @@ describe 'CreateSubscriptionsForApi' do
 
   # unit tests for new_unconfirmed_tokens_transactions
   # New unconfirmed tokens transactions
-  # Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed tokens transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed tokens transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+  # Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed tokens transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed tokens transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {warning}We cannot guarantee at 100% that webhooks for unconfirmed transactions will always be received. Some may **not get received** due to the possibility of some nodes not being updated with that information. This can occur in networks with low activity and/or not many nodes, e.g. Testnet networks and rarely Mainnets.{/warning}    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
   # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
   # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
   # @param [Hash] opts the optional parameters

data/spec/api/exchange_rates_api_spec.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
@@ -39,6 +39,7 @@ describe 'ExchangeRatesApi' do
   # @param to_asset_symbol Defines the relation asset symbol in which the base asset rate will be displayed.
   # @param [Hash] opts the optional parameters
   # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @option opts [Integer] :calculation_timestamp Defines the time of the market data used to calculate the exchange rate in UNIX Timestamp.
   # @return [GetExchangeRateByAssetSymbolsR]
   describe 'get_exchange_rate_by_asset_symbols test' do
     it 'should work' do
@@ -53,6 +54,7 @@ describe 'ExchangeRatesApi' do
   # @param to_asset_id Defines the relation asset Reference ID in which the base asset rate will be displayed.
   # @param [Hash] opts the optional parameters
   # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @option opts [Integer] :calculation_timestamp Defines the time of the market data used to calculate the exchange rate in UNIX Timestamp.
   # @return [GetExchangeRateByAssetsIDsR]
   describe 'get_exchange_rate_by_assets_ids test' do
     it 'should work' do

data/spec/api/{default_api_spec.rb → generating_api_spec.rb}

@@ -6,42 +6,43 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
 require 'spec_helper'
 require 'json'
 
-# Unit tests for CryptoApis::DefaultApi
+# Unit tests for CryptoApis::GeneratingApi
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
-describe 'DefaultApi' do
+describe 'GeneratingApi' do
   before do
     # run before each test
-    @api_instance = CryptoApis::DefaultApi.new
+    @api_instance = CryptoApis::GeneratingApi.new
   end
 
   after do
     # run after each test
   end
 
-  describe 'test an instance of DefaultApi' do
-    it 'should create an instance of DefaultApi' do
-      expect(@api_instance).to be_instance_of(CryptoApis::DefaultApi)
+  describe 'test an instance of GeneratingApi' do
+    it 'should create an instance of GeneratingApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::GeneratingApi)
     end
   end
 
-  # unit tests for get_contract_details_by_address
-  # Get Contract Details by Address
-  # This endpoint will return a smart contract details by address, this address is the address of the smart contract. It's not the same as the smart contract creator address.
-  # @param blockchain 
-  # @param network 
-  # @param contract_address String identifier of the token
+  # unit tests for generate_receiving_address
+  # Generate Receiving Address
+  # Through this endpoint customers can generate a new Receiving/Deposit Addresses into their Wallet.
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
+  # @param wallet_id Represents the unique ID of the specific Wallet.
   # @param [Hash] opts the optional parameters
   # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
-  # @return [GetContractDetailsByAddressR]
-  describe 'get_contract_details_by_address test' do
+  # @option opts [GenerateReceivingAddressRB] :generate_receiving_address_rb 
+  # @return [GenerateReceivingAddressR]
+  describe 'generate_receiving_address test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end

data/spec/api/informative_api_spec.rb

@@ -0,0 +1,81 @@
+=begin
+#CryptoAPIs
+
+#Crypto APIs 2.0 is a complex and innovative infrastructure layer that radically simplifies the development of any Blockchain and Crypto related applications. Organized around REST, Crypto APIs 2.0 can assist both novice Bitcoin/Ethereum enthusiasts and crypto experts with the development of their blockchain applications. Crypto APIs 2.0 provides unified endpoints and data, raw data, automatic tokens and coins forwardings, callback functionalities, and much more.
+
+The version of the OpenAPI document: 2.0.0
+Contact: developers@cryptoapis.io
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.2.1-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CryptoApis::InformativeApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'InformativeApi' do
+  before do
+    # run before each test
+    @api_instance = CryptoApis::InformativeApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of InformativeApi' do
+    it 'should create an instance of InformativeApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::InformativeApi)
+    end
+  end
+
+  # unit tests for get_wallet_asset_details
+  # Get Wallet Asset Details
+  # Through this endpoint customers can obtain details about a specific Wallet/Vault.
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
+  # @param wallet_id Defines the unique ID of the Wallet.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @return [GetWalletAssetDetailsR]
+  describe 'get_wallet_asset_details test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_receiving_addresses
+  # List Receiving Addresses
+  # Through this endpoint customers can pull a list of Deposit Addresses they have already generated. Deposit addresses are listed with their specific details such as unique ID.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
+  # @param wallet_id Represents the unique ID of the specific Wallet.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @return [ListReceivingAddressesR]
+  describe 'list_receiving_addresses test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_supported_tokens
+  # List Supported Tokens
+  # Through this endpoint customers can obtain information on multiple tokens at once.     {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @option opts [Integer] :limit Defines how many items should be returned in the response per page basis.
+  # @option opts [Integer] :offset The starting index of the response items, i.e. where the response should start listing the returned items.
+  # @return [ListSupportedTokensR]
+  describe 'list_supported_tokens test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/internal_api_spec.rb

@@ -0,0 +1,68 @@
+=begin
+#CryptoAPIs
+
+#Crypto APIs 2.0 is a complex and innovative infrastructure layer that radically simplifies the development of any Blockchain and Crypto related applications. Organized around REST, Crypto APIs 2.0 can assist both novice Bitcoin/Ethereum enthusiasts and crypto experts with the development of their blockchain applications. Crypto APIs 2.0 provides unified endpoints and data, raw data, automatic tokens and coins forwardings, callback functionalities, and much more.
+
+The version of the OpenAPI document: 2.0.0
+Contact: developers@cryptoapis.io
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.2.1-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CryptoApis::InternalApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'InternalApi' do
+  before do
+    # run before each test
+    @api_instance = CryptoApis::InternalApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of InternalApi' do
+    it 'should create an instance of InternalApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::InternalApi)
+    end
+  end
+
+  # unit tests for get_internal_transaction_by_transaction_hash_and_operation_id
+  # Get Internal Transaction by Transaction Hash and Operation Id
+  # Through this endpoint customers can obtain detailed information about a specific Internal Transaction by using the attributes `transactionHash`  (the parent transaction's Hash) and `operationId` (type trace address).    An internal transaction is the result of a smart contract being triggered by an EOA or a subsequent contract call.
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
+  # @param operation_id Represents the unique internal transaction ID in regards to the parent transaction (type trace address).
+  # @param transaction_hash String identifier of the parent transaction of the internal transaction represented in CryptoAPIs.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @return [GetInternalTransactionByTransactionHashAndOperationIdR]
+  describe 'get_internal_transaction_by_transaction_hash_and_operation_id test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_internal_transaction_details_by_transaction_hash
+  # List Internal Transaction Details by Transaction Hash
+  # Through this endpoint customers can list internal transactions along with their details by a specific attribute `transactionHash`, which is the parent transaction's Hash.    An internal transaction is the result of a smart contract being triggered by an EOA or a subsequent contract call.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
+  # @param transaction_hash String identifier of the parent transaction of the internal transaction represented in CryptoAPIs.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
+  # @option opts [Integer] :limit Defines how many items should be returned in the response per page basis.
+  # @option opts [Integer] :offset The starting index of the response items, i.e. where the response should start listing the returned items.
+  # @return [ListInternalTransactionDetailsByTransactionHashR]
+  describe 'list_internal_transaction_details_by_transaction_hash test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/manage_subscriptions_api_spec.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
@@ -49,7 +49,7 @@ describe 'ManageSubscriptionsApi' do
 
   # unit tests for list_blockchain_events_subscriptions
   # List Blockchain Events Subscriptions
-  # Through this endpoint the customer can obtain a list of their callback subscriptions for the available Blockchain events.    Currently Crypto APIs 2.0 offers certain Blockchain event endpoints which allow the user to subscribe for one/a few/all and receive callback notifications when the specific event occurs.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+  # Through this endpoint the customer can obtain a list of their callback subscriptions for the available Blockchain events.    Currently Crypto APIs 2.0 offers certain Blockchain event endpoints which allow the user to subscribe for one/a few/all and receive callback notifications when the specific event occurs.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
   # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
   # @param network Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \"mainnet\" is the live network with actual data while networks like \"testnet\", \"ropsten\", \"rinkeby\" are test networks.
   # @param [Hash] opts the optional parameters

data/spec/api/metadata_api_spec.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 2.0.0
 Contact: developers@cryptoapis.io
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.1.1-SNAPSHOT
+OpenAPI Generator version: 5.2.1-SNAPSHOT
 
 =end
 
@@ -34,7 +34,7 @@ describe 'MetadataApi' do
 
   # unit tests for list_supported_assets
   # List Supported Assets
-  # This endpoint will return a list of supported assets. The asset could be a cryptocurrency or FIAT assets that we support. Each asset has a unique identifier - `assetId` and a unique symbol in the form of a string, e.g. \"BTC\".
+  # This endpoint will return a list of supported assets. The asset could be a cryptocurrency or FIAT assets that we support. Each asset has a unique identifier - `assetId` and a unique symbol in the form of a string, e.g. \"BTC\".    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
   # @param [Hash] opts the optional parameters
   # @option opts [String] :context In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
   # @option opts [String] :asset_type Defines the type of the supported asset. This could be either \"crypto\" or \"fiat\".