crypto_apis 1.0.0 → 1.1.0

data/docs/BlockchainDataInternalTransactionNotFoundError.md

@@ -0,0 +1,22 @@
+# CryptoApis::BlockchainDataInternalTransactionNotFoundError
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **code** | **String** | Specifies an error code, e.g. error 404. |  |
+| **message** | **String** | Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”. |  |
+| **details** | [**Array<BannedIpAddressErrorDetails>**](BannedIpAddressErrorDetails.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::BlockchainDataInternalTransactionNotFoundError.new(
+  code: blockchain_data_internal_transaction_not_found,
+  message: The specified internal transaction has not been found on the specific blockchain.,
+  details: null
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromAddressR.md

@@ -0,0 +1,24 @@
+# CryptoApis::CreateCoinsTransactionRequestFromAddressR
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **api_version** | **String** | Specifies the version of the API that incorporates this endpoint. |  |
+| **request_id** | **String** | Defines the ID of the request. The `requestId` is generated by Crypto APIs and it's unique for every request. |  |
+| **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. `context` is specified by the user. | [optional] |
+| **data** | [**CreateCoinsTransactionRequestFromAddressRData**](CreateCoinsTransactionRequestFromAddressRData.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromAddressR.new(
+  api_version: 2.0,
+  request_id: 601c1710034ed6d407996b30,
+  context: You can add any text here,
+  data: null
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromAddressRB.md

@@ -0,0 +1,20 @@
+# CryptoApis::CreateCoinsTransactionRequestFromAddressRB
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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. `context` is specified by the user. | [optional] |
+| **data** | [**CreateCoinsTransactionRequestFromAddressRBData**](CreateCoinsTransactionRequestFromAddressRBData.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromAddressRB.new(
+  context: null,
+  data: null
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromAddressRBData.md

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

data/docs/CreateCoinsTransactionRequestFromAddressRBDataItem.md

@@ -0,0 +1,22 @@
+# CryptoApis::CreateCoinsTransactionRequestFromAddressRBDataItem
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **amount** | **String** | Represents the specific amount of the transaction. |  |
+| **fee_priority** | **String** | Represents the fee priority of the automation, whether it is \"slow\", \"standard\" or \"fast\". |  |
+| **to_address** | **String** | Defines the specific recipient address for the transaction. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromAddressRBDataItem.new(
+  amount: 0.2,
+  fee_priority: slow,
+  to_address: 0xc065b539490f81b6c297c37b1925c3be2f190732
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromAddressRData.md

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

data/docs/CreateCoinsTransactionRequestFromAddressRI.md

@@ -0,0 +1,24 @@
+# CryptoApis::CreateCoinsTransactionRequestFromAddressRI
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **fee_priority** | **String** | Represents the fee priority of the automation, whether it is \"slow\", \"standard\" or \"fast\". |  |
+| **recipients** | [**Array<CreateCoinsTransactionRequestFromAddressRIRecipients>**](CreateCoinsTransactionRequestFromAddressRIRecipients.md) | Defines the destination for the transaction, i.e. the recipient(s). |  |
+| **senders** | [**CreateCoinsTransactionRequestFromAddressRISenders**](CreateCoinsTransactionRequestFromAddressRISenders.md) |  |  |
+| **transaction_request_status** | **String** | Defines the status of the transaction request, e.g. \"created, \"await_approval\", \"pending\", \"prepared\", \"signed\", \"broadcasted\", \"success\", \"failed\", \"rejected\", mined\". |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromAddressRI.new(
+  fee_priority: standard,
+  recipients: null,
+  senders: null,
+  transaction_request_status: created
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromAddressRIRecipients.md

@@ -0,0 +1,20 @@
+# CryptoApis::CreateCoinsTransactionRequestFromAddressRIRecipients
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Defines the destination address. |  |
+| **amount** | **String** | Defines the amount sent to the destination address. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromAddressRIRecipients.new(
+  address: 0x1316bea88fb7cd4ccc4a57e2f9f4f43d1a86ee59,
+  amount: 0.0023
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromAddressRISenders.md

@@ -0,0 +1,18 @@
+# CryptoApis::CreateCoinsTransactionRequestFromAddressRISenders
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Defines the sender's public address. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromAddressRISenders.new(
+  address: 0x8798d11a96a2822ae60275f3a0798a2542912a10
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromWalletR.md

@@ -0,0 +1,24 @@
+# CryptoApis::CreateCoinsTransactionRequestFromWalletR
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **api_version** | **String** | Specifies the version of the API that incorporates this endpoint. |  |
+| **request_id** | **String** | Defines the ID of the request. The `requestId` is generated by Crypto APIs and it's unique for every request. |  |
+| **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. `context` is specified by the user. | [optional] |
+| **data** | [**CreateCoinsTransactionRequestFromWalletRData**](CreateCoinsTransactionRequestFromWalletRData.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromWalletR.new(
+  api_version: 2.0,
+  request_id: 601c1710034ed6d407996b30,
+  context: You can add any text here,
+  data: null
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromWalletRB.md

@@ -0,0 +1,20 @@
+# CryptoApis::CreateCoinsTransactionRequestFromWalletRB
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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. `context` is specified by the user. | [optional] |
+| **data** | [**CreateCoinsTransactionRequestFromWalletRBData**](CreateCoinsTransactionRequestFromWalletRBData.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromWalletRB.new(
+  context: null,
+  data: null
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromWalletRBData.md

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

data/docs/CreateCoinsTransactionRequestFromWalletRBDataItem.md

@@ -0,0 +1,20 @@
+# CryptoApis::CreateCoinsTransactionRequestFromWalletRBDataItem
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **destinations** | [**Array<CreateCoinsTransactionRequestFromWalletRBDataItemDestinations>**](CreateCoinsTransactionRequestFromWalletRBDataItemDestinations.md) | Defines the destination of the transaction, whether it is incoming or outgoing. |  |
+| **fee_priority** | **String** | Represents the fee priority of the automation, whether it is \"slow\", \"standard\" or \"fast\". |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromWalletRBDataItem.new(
+  destinations: null,
+  fee_priority: standard
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromWalletRBDataItemDestinations.md

@@ -0,0 +1,20 @@
+# CryptoApis::CreateCoinsTransactionRequestFromWalletRBDataItemDestinations
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Defines the specific destination address. |  |
+| **amount** | **String** | Represents the specific amount of the transaction's destination. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromWalletRBDataItemDestinations.new(
+  address: 0x6f61e3c2fbb8c8be698bd0907ba6c04b62800fe5,
+  amount: 0.125
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromWalletRData.md

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

data/docs/CreateCoinsTransactionRequestFromWalletRI.md

@@ -0,0 +1,24 @@
+# CryptoApis::CreateCoinsTransactionRequestFromWalletRI
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **fee_priority** | **String** | Represents the fee priority of the automation, whether it is \"slow\", \"standard\" or \"fast\". |  |
+| **recipients** | [**Array<CreateCoinsTransactionRequestFromWalletRIRecipients>**](CreateCoinsTransactionRequestFromWalletRIRecipients.md) | Defines the destination of the transaction, whether it is incoming or outgoing. |  |
+| **total_transaction_amount** | **String** | Represents the specific amount of the transaction. |  |
+| **transaction_request_status** | **String** | Defines the status of the transaction, e.g. \"created, \"await_approval\", \"pending\", \"prepared\", \"signed\", \"broadcasted\", \"success\", \"failed\", \"rejected\", mined\". |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromWalletRI.new(
+  fee_priority: standard,
+  recipients: null,
+  total_transaction_amount: 0.001,
+  transaction_request_status: created
+)
+```
+

data/docs/CreateCoinsTransactionRequestFromWalletRIRecipients.md

@@ -0,0 +1,20 @@
+# CryptoApis::CreateCoinsTransactionRequestFromWalletRIRecipients
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Defines the specific destination address. |  |
+| **amount** | **String** | Represents the specific amount of the transaction's destination. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::CreateCoinsTransactionRequestFromWalletRIRecipients.new(
+  address: mmd963W1fECjLyaDCHcioSCZYHkRwjkhtr,
+  amount: 0.00123
+)
+```
+

data/docs/CreateSubscriptionsForApi.md

@@ -8,6 +8,8 @@ All URIs are relative to *https://rest.cryptoapis.io/v2*
 | [**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_internal_transactions**](CreateSubscriptionsForApi.md#new_confirmed_internal_transactions) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/address-internal-transactions-confirmed | New confirmed internal transactions |
+| [**new_confirmed_internal_transactions_and_each_confirmation**](CreateSubscriptionsForApi.md#new_confirmed_internal_transactions_and_each_confirmation) | **POST** /blockchain-events/{blockchain}/{network}/subscriptions/address-internal-transactions-confirmed-each-confirmation | New confirmed internal 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 |
@@ -330,6 +332,164 @@ end
 - **Accept**: application/json
 
 
+## new_confirmed_internal_transactions
+
+> <NewConfirmedInternalTransactionsR> new_confirmed_internal_transactions(blockchain, network, opts)
+
+New confirmed internal transactions
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new confirmed internal transactions. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs.    Being confirmed means that the transactions are verified by miners and added to the next block.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+
+### 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_internal_transactions_rb: CryptoApis::NewConfirmedInternalTransactionsRB.new({data: CryptoApis::NewConfirmedInternalTransactionsRBData.new({item: CryptoApis::NewConfirmedInternalTransactionsRBDataItem.new({address: '0xbcc817f057950b0df41206c5d7125e6225cae18e', allow_duplicates: true, callback_secret_key: 'yourSecretKey', callback_url: 'http://example.com'})})}) # NewConfirmedInternalTransactionsRB | 
+}
+
+begin
+  # New confirmed internal transactions
+  result = api_instance.new_confirmed_internal_transactions(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_internal_transactions: #{e}"
+end
+```
+
+#### Using the new_confirmed_internal_transactions_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewConfirmedInternalTransactionsR>, Integer, Hash)> new_confirmed_internal_transactions_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New confirmed internal transactions
+  data, status_code, headers = api_instance.new_confirmed_internal_transactions_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewConfirmedInternalTransactionsR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_internal_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_internal_transactions_rb** | [**NewConfirmedInternalTransactionsRB**](NewConfirmedInternalTransactionsRB.md) |  | [optional] |
+
+### Return type
+
+[**NewConfirmedInternalTransactionsR**](NewConfirmedInternalTransactionsR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## new_confirmed_internal_transactions_and_each_confirmation
+
+> <NewConfirmedInternalTransactionsAndEachConfirmationR> new_confirmed_internal_transactions_and_each_confirmation(blockchain, network, opts)
+
+New confirmed internal transactions and each confirmation
+
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new confirmed internal transactions. Includes also a response at each confirmation the transaction receives until the specified confirmations limit is reached. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs.     Being confirmed means that the transactions are verified by miners and added to the next block.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+
+### 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_internal_transactions_and_each_confirmation_rb: CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRB.new({data: CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRBData.new({item: CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRBDataItem.new({address: '0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2', allow_duplicates: true, callback_secret_key: 'yourSecretString', callback_url: 'https://example.com', confirmations_count: 3})})}) # NewConfirmedInternalTransactionsAndEachConfirmationRB | 
+}
+
+begin
+  # New confirmed internal transactions and each confirmation
+  result = api_instance.new_confirmed_internal_transactions_and_each_confirmation(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_internal_transactions_and_each_confirmation: #{e}"
+end
+```
+
+#### Using the new_confirmed_internal_transactions_and_each_confirmation_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<NewConfirmedInternalTransactionsAndEachConfirmationR>, Integer, Hash)> new_confirmed_internal_transactions_and_each_confirmation_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # New confirmed internal transactions and each confirmation
+  data, status_code, headers = api_instance.new_confirmed_internal_transactions_and_each_confirmation_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <NewConfirmedInternalTransactionsAndEachConfirmationR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling CreateSubscriptionsForApi->new_confirmed_internal_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_internal_transactions_and_each_confirmation_rb** | [**NewConfirmedInternalTransactionsAndEachConfirmationRB**](NewConfirmedInternalTransactionsAndEachConfirmationRB.md) |  | [optional] |
+
+### Return type
+
+[**NewConfirmedInternalTransactionsAndEachConfirmationR**](NewConfirmedInternalTransactionsAndEachConfirmationR.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)
@@ -494,7 +654,7 @@ end
 
 New unconfirmed coins transactions
 
-Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed coins transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed coins transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed coins transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed coins transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {warning}We cannot guarantee at 100% that webhooks for unconfirmed transactions will always be received. Some may **not get received** due to the possibility of some nodes not being updated with that information. This can occur in networks with low activity and/or not many nodes, e.g. Testnet networks and rarely Mainnets.{/warning}    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
 
 ### Examples
 
@@ -573,7 +733,7 @@ end
 
 New unconfirmed tokens transactions
 
-Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed tokens transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed tokens transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed tokens transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.    Unconfirmed tokens transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations.    {warning}We cannot guarantee at 100% that webhooks for unconfirmed transactions will always be received. Some may **not get received** due to the possibility of some nodes not being updated with that information. This can occur in networks with low activity and/or not many nodes, e.g. Testnet networks and rarely Mainnets.{/warning}    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {note}It is also **important to note** that just because pending unconfirmed transactions are in the mempool, **doesn't necessarily** mean they will get confirmed.{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
 
 ### Examples