crypto_apis 1.0.0

data/docs/CreateAutomaticTokensForwardingRData.md

@@ -0,0 +1,18 @@
+# CryptoApis::CreateAutomaticTokensForwardingRData
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **item** | [**CreateAutomaticTokensForwardingRI**](CreateAutomaticTokensForwardingRI.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateAutomaticTokensForwardingRData.new(
+  item: null
+)
+```
+

data/docs/CreateAutomaticTokensForwardingRI.md

@@ -0,0 +1,36 @@
+# CryptoApis::CreateAutomaticTokensForwardingRI
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **callback_url** | **String** | Represents the URL that is set by the customer where the callback will be received at. The callback notification will be received only if and when the event occurs. |  |
+| **confirmations_count** | **Integer** | Represents the number of confirmations, i.e. the amount of blocks that have been built on top of this block. |  |
+| **created_timestamp** | **Integer** | Defines the specific time/date when the automatic forwarding was created in Unix Timestamp. |  |
+| **fee_address** | **String** | Represents the specific fee address, which is always automatically generated. Users must fund it. |  |
+| **fee_priority** | **String** | Represents the fee priority of the automation, whether it is \"SLOW\", \"STANDARD\" or \"FAST\". |  |
+| **from_address** | **String** | Represents the hash of the address that forwards the tokens. |  |
+| **minimum_transfer_amount** | **String** | Represents the minimum transfer amount of the tokens in the `fromAddress` that can be allowed for an automatic forwarding. |  |
+| **reference_id** | **String** | Represents a unique ID used to reference the specific callback subscription. |  |
+| **to_address** | **String** | Represents the hash of the address the tokens are forwarded to. |  |
+| **token_data** | [**CreateAutomaticTokensForwardingRITS**](CreateAutomaticTokensForwardingRITS.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateAutomaticTokensForwardingRI.new(
+  callback_url: https://example.com,
+  confirmations_count: 2,
+  created_timestamp: 1611238648,
+  fee_address: mojjR51gMXLJ4B3SBPhEXXRFDX7U5UWXNQ,
+  fee_priority: standard,
+  from_address: ms4KNsbNpoU8g424pzmEjbkFbfAHae1msB,
+  minimum_transfer_amount: 0.5,
+  reference_id: 6017dd02a309213863be9e55,
+  to_address: tb1q54j7qcu7kgsrx87yn0r9zjdvsxrnvxg4qua2z6,
+  token_data: null
+)
+```
+

data/docs/CreateAutomaticTokensForwardingRITS.md

@@ -0,0 +1,49 @@
+# CryptoApis::CreateAutomaticTokensForwardingRITS
+
+## Class instance methods
+
+### `openapi_one_of`
+
+Returns the list of classes defined in oneOf.
+
+#### Example
+
+```ruby
+require 'crypto_apis'
+
+CryptoApis::CreateAutomaticTokensForwardingRITS.openapi_one_of
+# =>
+# [
+#   :'CreateAutomaticTokensForwardingRITSBOT',
+#   :'CreateAutomaticTokensForwardingRITSET'
+# ]
+```
+
+### build
+
+Find the appropriate object from the `openapi_one_of` list and casts the data into it.
+
+#### Example
+
+```ruby
+require 'crypto_apis'
+
+CryptoApis::CreateAutomaticTokensForwardingRITS.build(data)
+# => #<CreateAutomaticTokensForwardingRITSBOT:0x00007fdd4aab02a0>
+
+CryptoApis::CreateAutomaticTokensForwardingRITS.build(data_that_doesnt_match)
+# => nil
+```
+
+#### Parameters
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| **data** | **Mixed** | data to be matched against the list of oneOf items |
+
+#### Return type
+
+- `CreateAutomaticTokensForwardingRITSBOT`
+- `CreateAutomaticTokensForwardingRITSET`
+- `nil` (if no type matches)
+

data/docs/CreateAutomaticTokensForwardingRITSBOT.md

@@ -0,0 +1,18 @@
+# CryptoApis::CreateAutomaticTokensForwardingRITSBOT
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **property_id** | **Integer** | Defines the `propertyId` of the Omni Layer token. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateAutomaticTokensForwardingRITSBOT.new(
+  property_id: 31
+)
+```
+

data/docs/CreateAutomaticTokensForwardingRITSET.md

@@ -0,0 +1,18 @@
+# CryptoApis::CreateAutomaticTokensForwardingRITSET
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **contract_address** | **String** | Represents the specific `contractAddress` of the Token that will be forwarded. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateAutomaticTokensForwardingRITSET.new(
+  contract_address: 0xdac17f958d2ee523a2206206994597c13d831ec7
+)
+```
+

data/docs/CreateSubscriptionsForApi.md

@@ -0,0 +1,647 @@
+# CryptoApis::CreateSubscriptionsForApi
+
+All URIs are relative to *https://rest.cryptoapis.io/v2*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**mined_transaction**](CreateSubscriptionsForApi.md#mined_transaction) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/transaction-mined | Mined transaction |
+| [**new_block**](CreateSubscriptionsForApi.md#new_block) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/block-mined | New Block |
+| [**new_confirmed_coins_transactions**](CreateSubscriptionsForApi.md#new_confirmed_coins_transactions) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/address-coins-transactions-confirmed | New confirmed coins transactions |
+| [**new_confirmed_coins_transactions_and_each_confirmation**](CreateSubscriptionsForApi.md#new_confirmed_coins_transactions_and_each_confirmation) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/address-coins-transactions-confirmed-each-confirmation | New confirmed coins transactions and each confirmation |
+| [**new_confirmed_tokens_transactions**](CreateSubscriptionsForApi.md#new_confirmed_tokens_transactions) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/address-tokens-transactions-confirmed | New confirmed tokens transactions |
+| [**new_confirmed_tokens_transactions_and_each_confirmation**](CreateSubscriptionsForApi.md#new_confirmed_tokens_transactions_and_each_confirmation) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/address-tokens-transactions-confirmed-each-confirmation | New confirmed tokens transactions and each confirmation |
+| [**new_unconfirmed_coins_transactions**](CreateSubscriptionsForApi.md#new_unconfirmed_coins_transactions) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/address-coins-transactions-unconfirmed | New unconfirmed coins transactions |
+| [**new_unconfirmed_tokens_transactions**](CreateSubscriptionsForApi.md#new_unconfirmed_tokens_transactions) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/address-tokens-transactions-unconfirmed | New unconfirmed tokens transactions |
+
+
+## mined_transaction
+
+> <MinedTransactionR> mined_transaction(blockchain, network, opts)
+
+Mined transaction
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when a specific transaction is mined. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified `transactionId`.    A transaction is mined when it is included in a new block in the blockchain.    {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}
+
+### Examples
+
+```ruby
+require 'time'
+require 'crypto_apis'
+# setup authorization
+CryptoApis.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = CryptoApis::CreateSubscriptionsForApi.new
+blockchain = 'bitcoin' # String | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+network = 'mainnet' # String | 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.
+opts = {
+  context: 'context_example', # String | 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.
+  mined_transaction_rb: CryptoApis::MinedTransactionRB.new({data: CryptoApis::MinedTransactionRBData.new({item: CryptoApis::MinedTransactionRBDataItem.new({callback_url: 'http://example.com', transaction_id: 'df2690ff97e72c1f8b0f2102a8cb5c1d0fa8fb8754d543c9bc0edc4d4bc34bfc'})})}) # MinedTransactionRB | 
+}
+
+begin
+  # Mined transaction
+  result = api_instance.mined_transaction(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->mined_transaction: #{e}"
+end
+```
+
+#### Using the mined_transaction_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<MinedTransactionR>, Integer, Hash)> mined_transaction_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # Mined transaction
+  data, status_code, headers = api_instance.mined_transaction_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <MinedTransactionR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->mined_transaction_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. |  |
+| **network** | **String** | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \&quot;mainnet\&quot; is the live network with actual data while networks like \&quot;testnet\&quot;, \&quot;ropsten\&quot;, \&quot;rinkeby\&quot; are test networks. |  |
+| **context** | **String** | 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. &#x60;context&#x60; is specified by the user. | [optional] |
+| **mined_transaction_rb** | [**MinedTransactionRB**](MinedTransactionRB.md) |  | [optional] |
+
+### Return type
+
+[**MinedTransactionR**](MinedTransactionR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## new_block
+
+> <NewBlockR> new_block(blockchain, network, opts)
+
+New Block
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when a new block is mined in the specific blockchain. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    A new block is mined when it is added to the chain once a consensus is reached by the majority of the miners, which is when the block gets validated and added to the blockchain.    {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}
+
+### Examples
+
+```ruby
+require 'time'
+require 'crypto_apis'
+# setup authorization
+CryptoApis.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = CryptoApis::CreateSubscriptionsForApi.new
+blockchain = 'bitcoin' # String | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+network = 'mainnet' # String | 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.
+opts = {
+  context: 'context_example', # String | 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.
+  new_block_rb: CryptoApis::NewBlockRB.new({data: CryptoApis::NewBlockRBData.new({item: CryptoApis::NewBlockRBDataItem.new({callback_url: 'http://example.com'})})}) # NewBlockRB | 
+}
+
+begin
+  # New Block
+  result = api_instance.new_block(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_block: #{e}"
+end
+```
+
+#### Using the new_block_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewBlockR>, Integer, Hash)> new_block_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New Block
+  data, status_code, headers = api_instance.new_block_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewBlockR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_block_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. |  |
+| **network** | **String** | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \&quot;mainnet\&quot; is the live network with actual data while networks like \&quot;testnet\&quot;, \&quot;ropsten\&quot;, \&quot;rinkeby\&quot; are test networks. |  |
+| **context** | **String** | 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. &#x60;context&#x60; is specified by the user. | [optional] |
+| **new_block_rb** | [**NewBlockRB**](NewBlockRB.md) |  | [optional] |
+
+### Return type
+
+[**NewBlockR**](NewBlockR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## new_confirmed_coins_transactions
+
+> <NewConfirmedCoinsTransactionsR> new_confirmed_coins_transactions(blockchain, network, opts)
+
+New confirmed coins transactions
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new incoming or outgoing confirmed transactions for coins from/to the customer's address. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.     Being confirmed means that the transactions are verified by miners and added to the next block.    {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}
+
+### Examples
+
+```ruby
+require 'time'
+require 'crypto_apis'
+# setup authorization
+CryptoApis.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = CryptoApis::CreateSubscriptionsForApi.new
+blockchain = 'bitcoin' # String | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+network = 'mainnet' # String | 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.
+opts = {
+  context: 'context_example', # String | 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.
+  new_confirmed_coins_transactions_rb: CryptoApis::NewConfirmedCoinsTransactionsRB.new({data: CryptoApis::NewConfirmedCoinsTransactionsRBData.new({item: CryptoApis::NewConfirmedCoinsTransactionsRBDataItem.new({address: 'mho4jHBcrNCncKt38trJahXakuaBnS7LK5', callback_url: 'http://example.com'})})}) # NewConfirmedCoinsTransactionsRB | 
+}
+
+begin
+  # New confirmed coins transactions
+  result = api_instance.new_confirmed_coins_transactions(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_coins_transactions: #{e}"
+end
+```
+
+#### Using the new_confirmed_coins_transactions_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewConfirmedCoinsTransactionsR>, Integer, Hash)> new_confirmed_coins_transactions_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New confirmed coins transactions
+  data, status_code, headers = api_instance.new_confirmed_coins_transactions_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewConfirmedCoinsTransactionsR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_coins_transactions_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. |  |
+| **network** | **String** | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \&quot;mainnet\&quot; is the live network with actual data while networks like \&quot;testnet\&quot;, \&quot;ropsten\&quot;, \&quot;rinkeby\&quot; are test networks. |  |
+| **context** | **String** | 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. &#x60;context&#x60; is specified by the user. | [optional] |
+| **new_confirmed_coins_transactions_rb** | [**NewConfirmedCoinsTransactionsRB**](NewConfirmedCoinsTransactionsRB.md) |  | [optional] |
+
+### Return type
+
+[**NewConfirmedCoinsTransactionsR**](NewConfirmedCoinsTransactionsR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## new_confirmed_coins_transactions_and_each_confirmation
+
+> <NewConfirmedCoinsTransactionsAndEachConfirmationR> new_confirmed_coins_transactions_and_each_confirmation(blockchain, network, opts)
+
+New confirmed coins transactions and each confirmation
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new incoming or outgoing confirmed transactions for coins from/to the customer's address with also a response at each confirmation the transaction has received until the specified confirmations limit is reached. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.     Being confirmed means that the transactions are verified by miners and added to the next block. This endpoint refers to **coins transactions only, not tokens**.    {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}
+
+### Examples
+
+```ruby
+require 'time'
+require 'crypto_apis'
+# setup authorization
+CryptoApis.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = CryptoApis::CreateSubscriptionsForApi.new
+blockchain = 'bitcoin' # String | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+network = 'mainnet' # String | 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.
+opts = {
+  context: 'context_example', # String | 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.
+  new_confirmed_coins_transactions_and_each_confirmation_rb: CryptoApis::NewConfirmedCoinsTransactionsAndEachConfirmationRB.new({data: CryptoApis::NewConfirmedCoinsTransactionsAndEachConfirmationRBData.new({item: CryptoApis::NewConfirmedCoinsTransactionsAndEachConfirmationRBDataItem.new({address: 'mho4jHBcrNCncKt38trJahXakuaBnS7LK5', callback_url: 'http://example.com', confirmations_count: 3})})}) # NewConfirmedCoinsTransactionsAndEachConfirmationRB | 
+}
+
+begin
+  # New confirmed coins transactions and each confirmation
+  result = api_instance.new_confirmed_coins_transactions_and_each_confirmation(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_coins_transactions_and_each_confirmation: #{e}"
+end
+```
+
+#### Using the new_confirmed_coins_transactions_and_each_confirmation_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewConfirmedCoinsTransactionsAndEachConfirmationR>, Integer, Hash)> new_confirmed_coins_transactions_and_each_confirmation_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New confirmed coins transactions and each confirmation
+  data, status_code, headers = api_instance.new_confirmed_coins_transactions_and_each_confirmation_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewConfirmedCoinsTransactionsAndEachConfirmationR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_coins_transactions_and_each_confirmation_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. |  |
+| **network** | **String** | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \&quot;mainnet\&quot; is the live network with actual data while networks like \&quot;testnet\&quot;, \&quot;ropsten\&quot;, \&quot;rinkeby\&quot; are test networks. |  |
+| **context** | **String** | 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. &#x60;context&#x60; is specified by the user. | [optional] |
+| **new_confirmed_coins_transactions_and_each_confirmation_rb** | [**NewConfirmedCoinsTransactionsAndEachConfirmationRB**](NewConfirmedCoinsTransactionsAndEachConfirmationRB.md) |  | [optional] |
+
+### Return type
+
+[**NewConfirmedCoinsTransactionsAndEachConfirmationR**](NewConfirmedCoinsTransactionsAndEachConfirmationR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## new_confirmed_tokens_transactions
+
+> <NewConfirmedTokensTransactionsR> new_confirmed_tokens_transactions(blockchain, network, opts)
+
+New confirmed tokens transactions
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new incoming or outgoing confirmed transactions for tokens from/to the customer's address. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.     Being confirmed means that the transactions are verified by miners and added to the next block. This endpoint refers to **tokens transactions only, not coins**.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+
+### Examples
+
+```ruby
+require 'time'
+require 'crypto_apis'
+# setup authorization
+CryptoApis.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = CryptoApis::CreateSubscriptionsForApi.new
+blockchain = 'bitcoin' # String | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+network = 'mainnet' # String | 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.
+opts = {
+  context: 'context_example', # String | 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.
+  new_confirmed_tokens_transactions_rb: CryptoApis::NewConfirmedTokensTransactionsRB.new({data: CryptoApis::NewUnconfirmedTokensTransactionsRBData.new({item: CryptoApis::NewUnconfirmedTokensTransactionsRBDataItem.new({address: 'mho4jHBcrNCncKt38trJahXakuaBnS7LK5', callback_url: 'http://example.com'})})}) # NewConfirmedTokensTransactionsRB | 
+}
+
+begin
+  # New confirmed tokens transactions
+  result = api_instance.new_confirmed_tokens_transactions(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_tokens_transactions: #{e}"
+end
+```
+
+#### Using the new_confirmed_tokens_transactions_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewConfirmedTokensTransactionsR>, Integer, Hash)> new_confirmed_tokens_transactions_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New confirmed tokens transactions
+  data, status_code, headers = api_instance.new_confirmed_tokens_transactions_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewConfirmedTokensTransactionsR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_tokens_transactions_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. |  |
+| **network** | **String** | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \&quot;mainnet\&quot; is the live network with actual data while networks like \&quot;testnet\&quot;, \&quot;ropsten\&quot;, \&quot;rinkeby\&quot; are test networks. |  |
+| **context** | **String** | 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. &#x60;context&#x60; is specified by the user. | [optional] |
+| **new_confirmed_tokens_transactions_rb** | [**NewConfirmedTokensTransactionsRB**](NewConfirmedTokensTransactionsRB.md) |  | [optional] |
+
+### Return type
+
+[**NewConfirmedTokensTransactionsR**](NewConfirmedTokensTransactionsR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## new_confirmed_tokens_transactions_and_each_confirmation
+
+> <NewConfirmedTokensTransactionsAndEachConfirmationR> new_confirmed_tokens_transactions_and_each_confirmation(blockchain, network, opts)
+
+New confirmed tokens transactions and each confirmation
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new incoming or outgoing confirmed transactions for tokens from/to the customer's address with also a response at each confirmation the transaction has received until the specified confirmations limit is reached. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.     Being confirmed means that the transactions are verified by miners and added to the next block. This endpoint refers to **tokens transactions only, not coins**.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+
+### Examples
+
+```ruby
+require 'time'
+require 'crypto_apis'
+# setup authorization
+CryptoApis.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = CryptoApis::CreateSubscriptionsForApi.new
+blockchain = 'bitcoin' # String | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+network = 'mainnet' # String | 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.
+opts = {
+  context: 'context_example', # String | 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.
+  new_confirmed_tokens_transactions_and_each_confirmation_rb: CryptoApis::NewConfirmedTokensTransactionsAndEachConfirmationRB.new({data: CryptoApis::NewConfirmedTokensTransactionsAndEachConfirmationRBData.new({item: CryptoApis::NewConfirmedTokensTransactionsAndEachConfirmationRBDataItem.new({address: 'mho4jHBcrNCncKt38trJahXakuaBnS7LK5', callback_url: 'http://example.com'})})}) # NewConfirmedTokensTransactionsAndEachConfirmationRB | 
+}
+
+begin
+  # New confirmed tokens transactions and each confirmation
+  result = api_instance.new_confirmed_tokens_transactions_and_each_confirmation(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_tokens_transactions_and_each_confirmation: #{e}"
+end
+```
+
+#### Using the new_confirmed_tokens_transactions_and_each_confirmation_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewConfirmedTokensTransactionsAndEachConfirmationR>, Integer, Hash)> new_confirmed_tokens_transactions_and_each_confirmation_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New confirmed tokens transactions and each confirmation
+  data, status_code, headers = api_instance.new_confirmed_tokens_transactions_and_each_confirmation_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewConfirmedTokensTransactionsAndEachConfirmationR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_tokens_transactions_and_each_confirmation_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. |  |
+| **network** | **String** | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \&quot;mainnet\&quot; is the live network with actual data while networks like \&quot;testnet\&quot;, \&quot;ropsten\&quot;, \&quot;rinkeby\&quot; are test networks. |  |
+| **context** | **String** | 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. &#x60;context&#x60; is specified by the user. | [optional] |
+| **new_confirmed_tokens_transactions_and_each_confirmation_rb** | [**NewConfirmedTokensTransactionsAndEachConfirmationRB**](NewConfirmedTokensTransactionsAndEachConfirmationRB.md) |  | [optional] |
+
+### Return type
+
+[**NewConfirmedTokensTransactionsAndEachConfirmationR**](NewConfirmedTokensTransactionsAndEachConfirmationR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## new_unconfirmed_coins_transactions
+
+> <NewUnconfirmedCoinsTransactionsR> new_unconfirmed_coins_transactions(blockchain, network, opts)
+
+New unconfirmed coins transactions
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed coins transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed coins transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+
+### Examples
+
+```ruby
+require 'time'
+require 'crypto_apis'
+# setup authorization
+CryptoApis.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = CryptoApis::CreateSubscriptionsForApi.new
+blockchain = 'bitcoin' # String | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+network = 'mainnet' # String | 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.
+opts = {
+  context: 'context_example', # String | 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.
+  new_unconfirmed_coins_transactions_rb: CryptoApis::NewUnconfirmedCoinsTransactionsRB.new({data: CryptoApis::NewUnconfirmedCoinsTransactionsRBData.new({item: CryptoApis::NewUnconfirmedCoinsTransactionsRBDataItem.new({address: 'mho4jHBcrNCncKt38trJahXakuaBnS7LK5', callback_url: 'http://example.com'})})}) # NewUnconfirmedCoinsTransactionsRB | 
+}
+
+begin
+  # New unconfirmed coins transactions
+  result = api_instance.new_unconfirmed_coins_transactions(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_unconfirmed_coins_transactions: #{e}"
+end
+```
+
+#### Using the new_unconfirmed_coins_transactions_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewUnconfirmedCoinsTransactionsR>, Integer, Hash)> new_unconfirmed_coins_transactions_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New unconfirmed coins transactions
+  data, status_code, headers = api_instance.new_unconfirmed_coins_transactions_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewUnconfirmedCoinsTransactionsR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_unconfirmed_coins_transactions_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. |  |
+| **network** | **String** | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \&quot;mainnet\&quot; is the live network with actual data while networks like \&quot;testnet\&quot;, \&quot;ropsten\&quot;, \&quot;rinkeby\&quot; are test networks. |  |
+| **context** | **String** | 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. &#x60;context&#x60; is specified by the user. | [optional] |
+| **new_unconfirmed_coins_transactions_rb** | [**NewUnconfirmedCoinsTransactionsRB**](NewUnconfirmedCoinsTransactionsRB.md) |  | [optional] |
+
+### Return type
+
+[**NewUnconfirmedCoinsTransactionsR**](NewUnconfirmedCoinsTransactionsR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## new_unconfirmed_tokens_transactions
+
+> <NewUnconfirmedTokensTransactionsR> new_unconfirmed_tokens_transactions(blockchain, network, opts)
+
+New unconfirmed tokens transactions
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed tokens transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed tokens transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+
+### Examples
+
+```ruby
+require 'time'
+require 'crypto_apis'
+# setup authorization
+CryptoApis.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = CryptoApis::CreateSubscriptionsForApi.new
+blockchain = 'bitcoin' # String | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
+network = 'mainnet' # String | 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.
+opts = {
+  context: 'context_example', # String | 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.
+  new_unconfirmed_tokens_transactions_rb: CryptoApis::NewUnconfirmedTokensTransactionsRB.new({data: CryptoApis::NewUnconfirmedTokensTransactionsRBData.new({item: CryptoApis::NewUnconfirmedTokensTransactionsRBDataItem.new({address: 'mho4jHBcrNCncKt38trJahXakuaBnS7LK5', callback_url: 'http://example.com'})})}) # NewUnconfirmedTokensTransactionsRB | 
+}
+
+begin
+  # New unconfirmed tokens transactions
+  result = api_instance.new_unconfirmed_tokens_transactions(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_unconfirmed_tokens_transactions: #{e}"
+end
+```
+
+#### Using the new_unconfirmed_tokens_transactions_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewUnconfirmedTokensTransactionsR>, Integer, Hash)> new_unconfirmed_tokens_transactions_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New unconfirmed tokens transactions
+  data, status_code, headers = api_instance.new_unconfirmed_tokens_transactions_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewUnconfirmedTokensTransactionsR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_unconfirmed_tokens_transactions_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. |  |
+| **network** | **String** | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - \&quot;mainnet\&quot; is the live network with actual data while networks like \&quot;testnet\&quot;, \&quot;ropsten\&quot;, \&quot;rinkeby\&quot; are test networks. |  |
+| **context** | **String** | 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. &#x60;context&#x60; is specified by the user. | [optional] |
+| **new_unconfirmed_tokens_transactions_rb** | [**NewUnconfirmedTokensTransactionsRB**](NewUnconfirmedTokensTransactionsRB.md) |  | [optional] |
+
+### Return type
+
+[**NewUnconfirmedTokensTransactionsR**](NewUnconfirmedTokensTransactionsR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+