crypto_apis 1.0.0

data/spec/api/exchange_rates_api_spec.rb

@@ -0,0 +1,63 @@
+=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.1.1-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CryptoApis::ExchangeRatesApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'ExchangeRatesApi' do
+  before do
+    # run before each test
+    @api_instance = CryptoApis::ExchangeRatesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ExchangeRatesApi' do
+    it 'should create an instance of ExchangeRatesApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::ExchangeRatesApi)
+    end
+  end
+
+  # unit tests for get_exchange_rate_by_asset_symbols
+  # Get Exchange Rate By Asset Symbols
+  # Through this endpoint customers can obtain exchange rates by asset symbols. The process represents the exchange rate value of a single unit of one asset versus another one. Data is provided per unique asset symbol.
+  # @param from_asset_symbol Defines the base asset symbol to get a rate for.
+  # @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.
+  # @return [GetExchangeRateByAssetSymbolsR]
+  describe 'get_exchange_rate_by_asset_symbols 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_exchange_rate_by_assets_ids
+  # Get Exchange Rate By Assets IDs
+  # Through this endpoint customers can obtain exchange rates by asset IDs. The process represents the exchange rate value of a single unit of one asset versus another one. Data is provided per unique asset Reference ID.
+  # @param from_asset_id Defines the base asset Reference ID to get a rate for.
+  # @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.
+  # @return [GetExchangeRateByAssetsIDsR]
+  describe 'get_exchange_rate_by_assets_ids 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

@@ -0,0 +1,66 @@
+=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.1.1-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CryptoApis::ManageSubscriptionsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'ManageSubscriptionsApi' do
+  before do
+    # run before each test
+    @api_instance = CryptoApis::ManageSubscriptionsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ManageSubscriptionsApi' do
+    it 'should create an instance of ManageSubscriptionsApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::ManageSubscriptionsApi)
+    end
+  end
+
+  # unit tests for delete_blockchain_event_subscription
+  # Delete Blockchain Event Subscription
+  # Through this endpoint the customer can delete blockchain event subscriptions they have by attributes `referenceId` and `network`.    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}
+  # @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 reference_id Represents a unique ID used to reference the specific callback subscription.
+  # @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 [DeleteBlockchainEventSubscriptionR]
+  describe 'delete_blockchain_event_subscription 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_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}
+  # @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 [ListBlockchainEventsSubscriptionsR]
+  describe 'list_blockchain_events_subscriptions 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/metadata_api_spec.rb

@@ -0,0 +1,50 @@
+=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.1.1-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CryptoApis::MetadataApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'MetadataApi' do
+  before do
+    # run before each test
+    @api_instance = CryptoApis::MetadataApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of MetadataApi' do
+    it 'should create an instance of MetadataApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::MetadataApi)
+    end
+  end
+
+  # 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\".
+  # @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 [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 [ListSupportedAssetsR]
+  describe 'list_supported_assets 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/omni_layer_api_spec.rb

@@ -0,0 +1,165 @@
+=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.1.1-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CryptoApis::OmniLayerApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'OmniLayerApi' do
+  before do
+    # run before each test
+    @api_instance = CryptoApis::OmniLayerApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of OmniLayerApi' do
+    it 'should create an instance of OmniLayerApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::OmniLayerApi)
+    end
+  end
+
+  # unit tests for get_omni_transaction_details_by_transaction_id__txid
+  # Get Omni Transaction Details By Transaction ID (Txid)
+  # Through this endpoint customers can obtain details about an Omni transaction by the transaction's unique identifier. The transaction can return information such as hash, height, time of creation in Unix timestamp, 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 blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @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 [GetOmniTransactionDetailsByTransactionIDTxidR]
+  describe 'get_omni_transaction_details_by_transaction_id__txid 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_unconfirmed_omni_transaction_by_transaction_id__txid
+  # Get Unconfirmed Omni Transaction By Transaction ID (Txid)
+  # Through this endpoint customers can obtain information on unconfirmed Omni transactions by an attribute `transactionId`. The transaction can have information such as hash, height, time of creation in Unix timestamp, etc.    Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.
+  # @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 blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @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 [GetUnconfirmedOmniTransactionByTransactionIDTxidR]
+  describe 'get_unconfirmed_omni_transaction_by_transaction_id__txid 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_omni_tokens_by_address
+  # List Omni Tokens By Address
+  # Through this endpoint the customer can receive basic information about a given Omni 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.
+  # @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 blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @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 [ListOmniTokensByAddressR]
+  describe 'list_omni_tokens_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_omni_transactions_by_address
+  # List Omni Transactions By Address
+  # This endpoint will list Omni transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, 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 blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @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 [ListOmniTransactionsByAddressR]
+  describe 'list_omni_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_omni_transactions_by_block_hash
+  # List Omni Transactions By Block Hash
+  # This endpoint will list Omni transactions by an attribute `transactionHash`. The transactions listed will detail additional information such as addresses, height, time of creation in Unix timestamp, 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 blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @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.
+  # @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 [ListOmniTransactionsByBlockHashR]
+  describe 'list_omni_transactions_by_block_hash 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_omni_transactions_by_block_height
+  # List Omni Transactions By Block Height
+  # This endpoint will list Omni transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, 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 blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @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.
+  # @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 [ListOmniTransactionsByBlockHeightR]
+  describe 'list_omni_transactions_by_block_height 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_unconfirmed_omni_transactions_by_address
+  # List Unconfirmed Omni Transactions By Address
+  # This endpoint will list unconfirmed Omni transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.
+  # @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 blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @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 [ListUnconfirmedOmniTransactionsByAddressR]
+  describe 'list_unconfirmed_omni_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_unconfirmed_omni_transactions_by_property_id
+  # List Unconfirmed Omni Transactions By Property ID
+  # This endpoint will list unconfirmed Omni transactions by an attribute `propertyId`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.
+  # @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 blockchain Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+  # @param property_id Represents the identifier of the tokens to send.
+  # @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 [ListUnconfirmedOmniTransactionsByPropertyIDR]
+  describe 'list_unconfirmed_omni_transactions_by_property_id 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/tokens_api_spec.rb

@@ -0,0 +1,86 @@
+=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.1.1-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CryptoApis::TokensApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'TokensApi' do
+  before do
+    # run before each test
+    @api_instance = CryptoApis::TokensApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of TokensApi' do
+    it 'should create an instance of TokensApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::TokensApi)
+    end
+  end
+
+  # unit tests for list_tokens_by_address
+  # List Tokens By Address
+  # Through this endpoint customers can obtain token data by providing an attribute - `address`.  The information that can be returned can include the contract address, the token symbol, type and balance.
+  # @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 \"ropsten\", \"rinkeby\" 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 [ListTokensByAddressR]
+  describe 'list_tokens_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_tokens_transfers_by_address
+  # List Tokens Transfers By Address
+  # Through this endpoint customers can obtain a list with token transfers by the `address` attribute. Token transfers may include information such as addresses of the sender and recipient, token name, token symbol, etc.    {note}This refers only to transfers done for **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 \"ropsten\", \"rinkeby\" 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 [ListTokensTransfersByAddressR]
+  describe 'list_tokens_transfers_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_tokens_transfers_by_transaction_hash
+  # List Tokens Transfers By Transaction Hash
+  # Through this endpoint customers can obtain a list with token transfers by the `transactionHash` attribute. Token transfers may include information such as addresses of the sender and recipient, token name, token symbol, etc.    {note}This refers only to transfers done for **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 \"ropsten\", \"rinkeby\" are test networks.
+  # @param transaction_hash Represents the hash of the transaction, 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.
+  # @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 [ListTokensTransfersByTransactionHashR]
+  describe 'list_tokens_transfers_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/unified_endpoints_api_spec.rb

@@ -0,0 +1,174 @@
+=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.1.1-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CryptoApis::UnifiedEndpointsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'UnifiedEndpointsApi' do
+  before do
+    # run before each test
+    @api_instance = CryptoApis::UnifiedEndpointsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of UnifiedEndpointsApi' do
+    it 'should create an instance of UnifiedEndpointsApi' do
+      expect(@api_instance).to be_instance_of(CryptoApis::UnifiedEndpointsApi)
+    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.
+  # @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 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 [GetAddressDetailsR]
+  describe 'get_address_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 get_block_details_by_block_hash
+  # 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 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.
+  # @return [GetBlockDetailsByBlockHashR]
+  describe 'get_block_details_by_block_hash 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_block_details_by_block_height
+  # 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 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.
+  # @return [GetBlockDetailsByBlockHeightR]
+  describe 'get_block_details_by_block_height 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_fee_recommendations
+  # 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 [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]
+  describe 'get_fee_recommendations 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_latest_mined_block
+  # Get Latest 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 [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
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_transaction_details_by_transaction_id
+  # 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 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 [GetTransactionDetailsByTransactionIDR]
+  describe 'get_transaction_details_by_transaction_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_transactions_by_address
+  # List 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 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 [ListTransactionsByAddressR]
+  describe 'list_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_transactions_by_block_hash
+  # 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 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.
+  # @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 [ListTransactionsByBlockHashR]
+  describe 'list_transactions_by_block_hash 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_transactions_by_block_height
+  # 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 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.
+  # @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 [ListTransactionsByBlockHeightR]
+  describe 'list_transactions_by_block_height test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end