crypto_apis 1.2.1 → 1.5.0

data/spec/api/transactions_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.2.1-SNAPSHOT
+OpenAPI Generator version: 6.0.0-SNAPSHOT
 
 =end
 
@@ -32,12 +32,29 @@ describe 'TransactionsApi' do
     end
   end
 
+  # unit tests for create_coins_transaction_from_address_for_whole_amount
+  # Create Coins Transaction From Address For Whole Amount
+  # Through this endpoint customers can create a new transaction from address for **coins** specifically, which will transfer over the entire available amount.
+  # @param address Defines the source address.
+  # @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\" are test networks.
+  # @param wallet_id Represents the sender's specific and unique Wallet ID of the sender.
+  # @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 [CreateCoinsTransactionFromAddressForWholeAmountRB] :create_coins_transaction_from_address_for_whole_amount_rb 
+  # @return [CreateCoinsTransactionFromAddressForWholeAmountR]
+  describe 'create_coins_transaction_from_address_for_whole_amount 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 create_coins_transaction_request_from_address
   # Create Coins Transaction Request from Address
   # Through this endpoint users can create a new single transaction request from one address to another.
-  # @param address Defines the specific source address for the transaction.
+  # @param address Defines the specific source address for the transaction. For XRP we also support the X-address format.
   # @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 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\" are test networks.
   # @param wallet_id Represents the sender's specific and unique Wallet ID of the sender.
   # @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.
@@ -53,7 +70,7 @@ describe 'TransactionsApi' do
   # Create Coins Transaction Request from Wallet
   # Through this endpoint users can create a new transaction request from the entire Wallet instead from just a specific address. This endpoint can generate transactions from multiple to multiple addresses.    {warning}This is available **only** for UTXO-based protocols such as Bitcoin, Bitcoin Cash, Litecoin, etc. It **is not** available for Account-based protocols like Ethereum.{/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 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\" are test networks.
   # @param wallet_id Represents the sender's specific and unique Wallet ID of the sender.
   # @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.
@@ -65,18 +82,18 @@ describe 'TransactionsApi' do
     end
   end
 
-  # unit tests for create_tokens_transaction_request_from_address
-  # Create Tokens Transaction Request from Address
-  # Through this endpoint users can make a single token transaction.    {warning}This applies only to **fungible** tokens, **not** NFTs (non-fungible tokens).{/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}    {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}
+  # unit tests for create_fungible_tokens_transaction_request_from_address
+  # Create Fungible Tokens Transaction Request from Address
+  # Through this endpoint users can make a single token transaction.    {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 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\" are test networks.
   # @param sender_address Defines the specific source address for the transaction.
   # @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.
-  # @option opts [CreateTokensTransactionRequestFromAddressRB] :create_tokens_transaction_request_from_address_rb 
-  # @return [CreateTokensTransactionRequestFromAddressR]
-  describe 'create_tokens_transaction_request_from_address test' do
+  # @option opts [CreateFungibleTokensTransactionRequestFromAddressRB] :create_fungible_tokens_transaction_request_from_address_rb 
+  # @return [CreateFungibleTokensTransactionRequestFromAddressR]
+  describe 'create_fungible_tokens_transaction_request_from_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/unified_endpoints_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.2.1-SNAPSHOT
+OpenAPI Generator version: 6.0.0-SNAPSHOT
 
 =end
 
@@ -32,11 +32,27 @@ describe 'UnifiedEndpointsApi' do
     end
   end
 
+  # unit tests for estimate_transaction_smart_fee
+  # Estimate Transaction Smart Fee
+  # Through this endpoint, customers can estimate the approximate fee per kilobyte needed for a transaction to begin confirmation within the `confirmationTarget` blocks when possible. After which it will return the number of blocks for which the estimate is valid.
+  # @param blockchain 
+  # @param network 
+  # @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] :confirmation_target Integer representation of confirmation target in blocks that estimation will be valid for
+  # @option opts [String] :estimate_mode String representation of the address
+  # @return [EstimateTransactionSmartFeeR]
+  describe 'estimate_transaction_smart_fee test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for get_address_details
   # Get Address Details
-  # Through this endpoint the customer can receive basic information about a given address based on confirmed/synced blocks only. In the case where there are any incoming or outgoing **unconfirmed** transactions for the specific address, they **will not** be counted or calculated here.
+  # Through this endpoint the customer can receive basic information about a given address based on confirmed/synced blocks only. In the case where there are any incoming or outgoing **unconfirmed** transactions for the specific address, they **will not** be counted or calculated here. Applies only for coins.
   # @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 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\" are test networks.
   # @param address Represents the public address, which is a compressed and shortened form of a public key.
   # @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.
@@ -51,7 +67,7 @@ describe 'UnifiedEndpointsApi' do
   # Get Block Details By Block Hash
   # Through this endpoint customers can obtain basic information about a given mined block, specifically by using the `hash` parameter. These block details could include the hash of the specific, the previous and the next block, its transactions count, its height, etc.     Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
   # @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 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\" are test networks.
   # @param block_hash Represents the hash of the block, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
   # @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.
@@ -66,7 +82,7 @@ describe 'UnifiedEndpointsApi' do
   # Get Block Details By Block Height
   # Through this endpoint customers can obtain basic information about a given mined block, specifically by using the `height` parameter. These block details could include the hash of the specific, the previous and the next block, its transactions count, its height, etc.     Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
   # @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 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\" are test networks.
   # @param height Represents the number of blocks in the blockchain preceding this specific block. Block numbers have no gaps. A blockchain usually starts with block 0 called the \"Genesis block\".
   # @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.
@@ -81,7 +97,7 @@ describe 'UnifiedEndpointsApi' do
   # Get Fee Recommendations
   # Through this endpoint customers can obtain fee recommendations. Our fees recommendations are based on Mempool data which makes them much more accurate than fees based on already mined blocks. Calculations are done in real time live. Using this endpoint customers can get gas price for Ethereum, fee per byte for Bitcoin, etc.
   # @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 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\" 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.
   # @return [GetFeeRecommendationsR]
@@ -91,15 +107,45 @@ describe 'UnifiedEndpointsApi' do
     end
   end
 
-  # unit tests for get_latest_mined_block
-  # Get Latest Mined Block
+  # unit tests for get_last_mined_block
+  # Get Last Mined Block
   # Through this endpoint customers can fetch the last mined block in a specific blockchain network, along with its details. These could include the hash of the specific, the previous and the next block, its transactions count, its height, etc.     Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
   # @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 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\" 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.
+  # @return [GetLastMinedBlockR]
+  describe 'get_last_mined_block test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_next_available_nonce
+  # Get Next Available Nonce
+  # Through this endpoint customers can get information about the next available nonce by providing the specific blockchain, network and address.
+  # @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\" are test networks.
+  # @param address Represents the public address, which is a compressed and shortened form of a public key.
+  # @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 [GetNextAvailableNonceR]
+  describe 'get_next_available_nonce test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_raw_transaction_data
+  # Get Raw Transaction Data
+  # Through this endpoint customers can get information on a transaction in its raw format by providing its `transactionId`.
+  # @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\" are test networks.
+  # @param transaction_id Represents the unique identifier of a transaction, i.e. it could be transactionId in UTXO-based protocols like Bitcoin, and transaction hash in Ethereum blockchain.
   # @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 [GetLatestMinedBlockR]
-  describe 'get_latest_mined_block test' do
+  # @return [GetRawTransactionDataR]
+  describe 'get_raw_transaction_data test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -109,7 +155,7 @@ describe 'UnifiedEndpointsApi' do
   # Get Transaction Details By Transaction ID
   # Through this endpoint customers can obtain details about a transaction by the transaction's unique identifier. In UTXO-based protocols like BTC there are attributes such as `transactionId` and transaction `hash`. They still could be different. In protocols like Ethereum there is only one unique value and it's `hash`.
   # @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 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\" are test networks.
   # @param transaction_id Represents the unique identifier of a transaction, i.e. it could be `transactionId` in UTXO-based protocols like Bitcoin, and transaction `hash` in Ethereum blockchain.
   # @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.
@@ -120,18 +166,106 @@ describe 'UnifiedEndpointsApi' do
     end
   end
 
-  # unit tests for list_transactions_by_address
-  # List Transactions By Address
+  # unit tests for list_all_unconfirmed_transactions
+  # List All Unconfirmed Transactions
+  # Through this endpoint customers can list all **unconfirmed**  transactions for a specified blockchain and network.
+  # @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\" 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 [ListAllUnconfirmedTransactionsR]
+  describe 'list_all_unconfirmed_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 list_confirmed_tokens_transfers_by_address_and_time_range
+  # List Confirmed Tokens Transfers By Address And Time Range
+  # Through this endpoint customers can obtain a list with **confirmed** token transfers by the `address` attribute and the query parameters `fromTimestamp` and `toTimestamp` which gives customers the opportunity to filter the results by a specified time period.    {note}This refers only to transfers done for **confirmed tokens** not coins.{/note}
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Ethereum Classic, 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\" are test networks.
+  # @param address Represents the public address, which is a compressed and shortened form of a public key.
+  # @param from_timestamp Defines the specific time/date from which the results will start being listed.
+  # @param to_timestamp Defines the specific time/date to which the results will be listed.
+  # @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 [ListConfirmedTokensTransfersByAddressAndTimeRangeR]
+  describe 'list_confirmed_tokens_transfers_by_address_and_time_range 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_confirmed_transactions_by_address
+  # List Confirmed Transactions By Address
   # This endpoint will list transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.
   # @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 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\" are test networks.
+  # @param address Represents the public address, which is a compressed and shortened form of a public key.
+  # @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 [ListConfirmedTransactionsByAddressR]
+  describe 'list_confirmed_transactions_by_address 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_confirmed_transactions_by_address_and_time_range
+  # List Confirmed Transactions By Address And Time Range
+  # This endpoint will list confirmed transactions by the attribute `address` and the query parameters `fromTimestamp` and `toTimestamp` which gives customers the opportunity to filter the results by a specified time period.
+  # @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\" are test networks.
   # @param address Represents the public address, which is a compressed and shortened form of a public key.
+  # @param from_timestamp Defines the specific time/date from which the results will start being listed.
+  # @param to_timestamp Defines the specific time/date to which the results will be listed.
+  # @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 [ListConfirmedTransactionsByAddressAndTimeRangeR]
+  describe 'list_confirmed_transactions_by_address_and_time_range 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_transactions_by_address_and_time_range
+  # List Internal Transactions By Address And Time Range
+  # Through this endpoint customers can list internal transactions by the `address` attribute and the query parameters `fromTimestamp` and `toTimestamp`  which gives customers the opportunity to filter the results by a specified time period.
+  # @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\" are test networks.
+  # @param address String identifier of the address document represented in CryptoAPIs
+  # @param from_timestamp Defines the specific time/date from which the results will start being listed.
+  # @param to_timestamp Defines the specific time/date to which the results will be listed.
   # @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 [ListTransactionsByAddressR]
-  describe 'list_transactions_by_address test' do
+  # @return [ListInternalTransactionsByAddressAndTimeRangeR]
+  describe 'list_internal_transactions_by_address_and_time_range 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_latest_mined_blocks
+  # List Latest Mined Blocks
+  # Through this endpoint customers can list **up to 50** from the latest blocks that were mined.
+  # @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\" are test networks
+  # @param blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param count Specifies how many records were requested.
+  # @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 [ListLatestMinedBlocksR]
+  describe 'list_latest_mined_blocks test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -141,7 +275,7 @@ describe 'UnifiedEndpointsApi' do
   # List Transactions by Block Hash
   # This endpoint will list transactions by an attribute `transactionHash`. The transactions listed will detail additional information such as addresses, height, time of creation in Unix timestamp, etc.
   # @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 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\" are test networks.
   # @param block_hash Represents the hash of the block, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
   # @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.
@@ -158,7 +292,7 @@ describe 'UnifiedEndpointsApi' do
   # List Transactions by Block Height
   # This endpoint will list transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.
   # @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 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\" are test networks.
   # @param height Represents the number of blocks in the blockchain preceding this specific block. Block numbers have no gaps. A blockchain usually starts with block 0 called the \"Genesis block\".
   # @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.
@@ -171,4 +305,38 @@ describe 'UnifiedEndpointsApi' do
     end
   end
 
+  # unit tests for list_unconfirmed_transactions_by_address
+  # List Unconfirmed Transactions by Address
+  # Through this endpoint customers can list transactions by `address` that are **unconfirmed**.
+  # @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\" are test networks.
+  # @param address Represents the public address, which is a compressed and shortened form of a public key.
+  # @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 [ListUnconfirmedTransactionsByAddressR]
+  describe 'list_unconfirmed_transactions_by_address 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_unspent_transaction_outputs_by_address
+  # List Unspent Transaction Outputs By Address
+  # Through this endpoint customers can list their transactions' unspent outputs by `address`.
+  # @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\" are test networks.
+  # @param address Represents the address that has unspend funds per which the result is returned.
+  # @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 [ListUnspentTransactionOutputsByAddressR]
+  describe 'list_unspent_transaction_outputs_by_address 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/xrp_ripple_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.2.1-SNAPSHOT
+OpenAPI Generator version: 6.0.0-SNAPSHOT
 
 =end
 
@@ -35,7 +35,7 @@ describe 'XRPRippleApi' do
   # unit tests for get_latest_mined_xrp__ripple_block
   # Get Latest Mined XRP (Ripple) Block
   # Through this endpoint customers can fetch the last mined XRP block in the blockchain, along with its details. These could include the hash of the specific, the previous and the next block, its transactions count, its height, etc.     Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
-  # @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 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\" 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.
   # @return [GetLatestMinedXRPRippleBlockR]
@@ -62,7 +62,7 @@ describe 'XRPRippleApi' do
   # unit tests for get_xrp__ripple_block_details_by_block_hash
   # Get XRP (Ripple) Block Details By Block Hash
   # Through this endpoint customers can obtain basic information about a given XRP block (a block on the XRP blockchain), specifically by using the `hash` parameter. These block details could include the hash of the specific, the previous and the next block, the number of included transactions, etc.     Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
-  # @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\",  are test networks.
+  # @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\" are test networks.
   # @param block_hash Represents the hash of the block, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
   # @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.
@@ -90,7 +90,7 @@ describe 'XRPRippleApi' do
   # unit tests for get_xrp__ripple_transaction_details_by_transaction_id
   # Get XRP (Ripple) Transaction Details By Transaction ID
   # Through this endpoint customers can obtain details about a XRP transaction by the transaction's unique identifier.     Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
-  # @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 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\" are test networks.
   # @param transaction_hash Represents the same as `transactionId` for account-based protocols like Ethereum, while it could be different in UTXO-based protocols like Bitcoin. E.g., in UTXO-based protocols `hash` is different from `transactionId` for SegWit transactions.
   # @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.
@@ -104,7 +104,7 @@ describe 'XRPRippleApi' do
   # unit tests for list_xrp__ripple_transactions_by_address
   # List XRP (Ripple) Transactions by Address
   # This endpoint will list XRP transactions by a attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
-  # @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\",  are test networks.
+  # @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\" are test networks.
   # @param address Represents the public address, which is a compressed and shortened form of a public key.
   # @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.
@@ -118,10 +118,29 @@ describe 'XRPRippleApi' do
     end
   end
 
+  # unit tests for list_xrp__ripple_transactions_by_address_and_time_range
+  # List XRP (Ripple) Transactions By Address And Time Range
+  # Тhis endpoint lists XRP transactions by the attribute `address` and the query parameters `fromTimestamp` and `toTimestamp`  which gives customers the opportunity to filter the results by a specified time period.
+  # @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\" are test networks.
+  # @param address Represents the public address, which is a compressed and shortened form of a public key.
+  # @param from_timestamp Defines the specific time/date from which the results will start being listed.
+  # @param to_timestamp Defines the specific time/date to which the results will be listed.
+  # @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.
+  # @option opts [String] :transaction_type Defines the transaction type.
+  # @return [ListXRPRippleTransactionsByAddressAndTimeRangeR]
+  describe 'list_xrp__ripple_transactions_by_address_and_time_range 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_xrp__ripple_transactions_by_block_hash
   # List XRP (Ripple) Transactions By Block Hash
   # This endpoint will list transactions by an attribute `blockHash`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
-  # @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 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\" are test networks.
   # @param block_hash Represents the hash of the block, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
   # @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.
@@ -137,7 +156,7 @@ describe 'XRPRippleApi' do
   # unit tests for list_xrp__ripple_transactions_by_block_height
   # List XRP (Ripple) Transactions By Block Height
   # This endpoint will list transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
-  # @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 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\" are test networks.
   # @param block_height 
   # @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.

data/spec/api/zilliqa_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.2.1-SNAPSHOT
+OpenAPI Generator version: 6.0.0-SNAPSHOT
 
 =end
 
@@ -35,7 +35,7 @@ describe 'ZilliqaApi' do
   # unit tests for get_latest_mined_zilliqa_block
   # Get Latest Mined Zilliqa Block
   # Through this endpoint users can obtain information on the latest block that has been mined on the Zilliqa blockchain. Data could include the current and previous block hashes, transaction count, and more.
-  # @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 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\" 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.
   # @return [GetLatestMinedZilliqaBlockR]
@@ -48,7 +48,7 @@ describe 'ZilliqaApi' do
   # unit tests for get_zilliqa_address_details
   # Get Zilliqa Address Details
   # Through this endpoint customers can obtain information address details from the Zilliqa blockchain.
-  # @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 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\" are test networks.
   # @param address Defines the specific transaction's address.
   # @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.
@@ -62,7 +62,7 @@ describe 'ZilliqaApi' do
   # unit tests for get_zilliqa_block_details_by_block_hash
   # Get Zilliqa Block Details By Block Hash
   # Through this endpoint customers can obtain block details from the Zilliqa blockchain by providing the block Hash parameter.
-  # @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 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\" are test networks.
   # @param block_hash Represents the hash of the block, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
   # @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.
@@ -76,7 +76,7 @@ describe 'ZilliqaApi' do
   # unit tests for get_zilliqa_block_details_by_block_height
   # Get Zilliqa Block Details By Block Height
   # Through this endpoint customers can obtain block details from the Zilliqa blockchain by providing the block Height parameter.
-  # @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\",  are test networks.
+  # @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\" are test networks.
   # @param block_height Represents the number of blocks in the blockchain preceding this specific block. Block numbers have no gaps. A blockchain usually starts with block 0 called the \"Genesis block\".
   # @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.
@@ -90,7 +90,7 @@ describe 'ZilliqaApi' do
   # unit tests for get_zilliqa_transaction_details_by_transaction_id
   # Get Zilliqa Transaction Details by Transaction ID
   # Through this endpoint customers can obtain transaction details on the Zilliqa blockchain by providing a Transaction ID parameter.
-  # @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 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\" are test networks.
   # @param transaction_hash String identifier of the transaction
   # @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.
@@ -104,7 +104,7 @@ describe 'ZilliqaApi' do
   # unit tests for list_zilliqa_transactions_by_address
   # List Zilliqa Transactions by Address
   # Through this endpoint customers can list transactions on the Zilliqa blockchain by the address parameter.
-  # @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 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\" are test networks.
   # @param address Defines the specific address of the sender.
   # @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.
@@ -120,7 +120,7 @@ describe 'ZilliqaApi' do
   # unit tests for list_zilliqa_transactions_by_block_hash
   # List Zilliqa Transactions By Block Hash
   # Through this endpoint customers can list transactions on the Zilliqa blockchain by the block hash parameter.
-  # @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 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\" are test networks.
   # @param block_hash Represents the hash of the block, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
   # @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.
@@ -136,7 +136,7 @@ describe 'ZilliqaApi' do
   # unit tests for list_zilliqa_transactions_by_block_height
   # List Zilliqa Transactions By Block Height
   # Through this endpoint customers can list transactions on the Zilliqa blockchain by the block height parameter.
-  # @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 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\" are test networks.
   # @param block_height Represents the number of blocks in the blockchain preceding this specific block. Block numbers have no gaps. A blockchain usually starts with block 0 called the \"Genesis block\".
   # @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.

data/spec/api_client_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.2.1-SNAPSHOT
+OpenAPI Generator version: 6.0.0-SNAPSHOT
 
 =end
 
@@ -197,8 +197,8 @@ describe CryptoApis::ApiClient do
     let(:api_client) { CryptoApis::ApiClient.new }
 
     it 'works' do
-      expect(api_client.select_header_content_type(nil)).to eq('application/json')
-      expect(api_client.select_header_content_type([])).to eq('application/json')
+      expect(api_client.select_header_content_type(nil)).to be_nil
+      expect(api_client.select_header_content_type([])).to be_nil
 
       expect(api_client.select_header_content_type(['application/json'])).to eq('application/json')
       expect(api_client.select_header_content_type(['application/xml', 'application/json; charset=UTF8'])).to eq('application/json; charset=UTF8')

data/spec/configuration_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.2.1-SNAPSHOT
+OpenAPI Generator version: 6.0.0-SNAPSHOT
 
 =end