crypto_apis 1.0.0 → 1.1.0

data/docs/GetZilliqaTransactionDetailsByTransactionIDRData.md

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

data/docs/GetZilliqaTransactionDetailsByTransactionIDRI.md

@@ -0,0 +1,40 @@
+# CryptoApis::GetZilliqaTransactionDetailsByTransactionIDRI
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **fee** | [**GetZilliqaTransactionDetailsByTransactionIDRIFee**](GetZilliqaTransactionDetailsByTransactionIDRIFee.md) |  |  |
+| **gas_limit** | **Integer** | Represents the maximum amount of gas allowed in the block in order to determine how many transactions it can fit. |  |
+| **gas_price** | **Integer** | Defines the price of the gas. |  |
+| **gas_used** | **Integer** | Defines how much of the gas for the block has been used. |  |
+| **mined_in_block_hash** | **String** | 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. |  |
+| **mined_in_block_height** | **Integer** | 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\". |  |
+| **nonce** | **Integer** | Represents the sequential running number for an address, starting from 0 for the first transaction. E.g., if the nonce of a transaction is 10, it would be the 11th transaction sent from the sender's address. |  |
+| **recipients** | [**Array<GetZilliqaTransactionDetailsByTransactionIDRIRecipients>**](GetZilliqaTransactionDetailsByTransactionIDRIRecipients.md) | Represents an object of addresses that receive the transactions. |  |
+| **senders** | [**Array<GetZilliqaTransactionDetailsByTransactionIDRISenders>**](GetZilliqaTransactionDetailsByTransactionIDRISenders.md) | Represents an object of addresses that provide the funds. |  |
+| **timestamp** | **Integer** | Defines the exact date/time when this block was mined in Unix Timestamp. |  |
+| **transaction_index** | **Integer** | Defines the numeric representation of the transaction index. |  |
+| **transaction_status** | **String** | Defines the status of the transaction, whether it is e.g. pending or complete. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::GetZilliqaTransactionDetailsByTransactionIDRI.new(
+  fee: null,
+  gas_limit: 552020,
+  gas_price: 2994782927,
+  gas_used: 24673,
+  mined_in_block_hash: 0x5ba627aed1ff0f5480694e994ee03a6ec7b5a6fa96be899c84d52725f9830891,
+  mined_in_block_height: 1250207,
+  nonce: 13,
+  recipients: null,
+  senders: null,
+  timestamp: 1582202940,
+  transaction_index: 0,
+  transaction_status: 0
+)
+```
+

data/docs/GetZilliqaTransactionDetailsByTransactionIDRIFee.md

@@ -0,0 +1,20 @@
+# CryptoApis::GetZilliqaTransactionDetailsByTransactionIDRIFee
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **amount** | **String** | Represents the amount of the transaction fee. |  |
+| **unit** | **String** | Represents the unit of the transaction fee. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::GetZilliqaTransactionDetailsByTransactionIDRIFee.new(
+  amount: 0.000235,
+  unit: ZIL
+)
+```
+

data/docs/GetZilliqaTransactionDetailsByTransactionIDRIRecipients.md

@@ -0,0 +1,20 @@
+# CryptoApis::GetZilliqaTransactionDetailsByTransactionIDRIRecipients
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Represents the hash of the address that receives the funds. |  |
+| **amount** | **String** | Defines the amount of the received funds as a string. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::GetZilliqaTransactionDetailsByTransactionIDRIRecipients.new(
+  address: zil1v25at4s3eh9w34uqqhe3vdvfsvcwq6un3fupc2,
+  amount: 0
+)
+```
+

data/docs/GetZilliqaTransactionDetailsByTransactionIDRISenders.md

@@ -0,0 +1,20 @@
+# CryptoApis::GetZilliqaTransactionDetailsByTransactionIDRISenders
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Represents the hash of the address that provides the funds. |  |
+| **amount** | **String** | Represents the total amount sent by this address including the fee. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::GetZilliqaTransactionDetailsByTransactionIDRISenders.new(
+  address: zil1uhn7627k6xl5f03sq6grje5lk3gy0kf5aptz83,
+  amount: 0
+)
+```
+

data/docs/InformativeApi.md

@@ -0,0 +1,249 @@
+# CryptoApis::InformativeApi
+
+All URIs are relative to *https://rest.cryptoapis.io/v2*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**get_wallet_asset_details**](InformativeApi.md#get_wallet_asset_details) | **GET** /wallet-as-a-service/wallets/{walletId}/{blockchain}/{network} | Get Wallet Asset Details |
+| [**list_receiving_addresses**](InformativeApi.md#list_receiving_addresses) | **GET** /wallet-as-a-service/wallets/{walletId}/{blockchain}/{network}/addresses | List Receiving Addresses |
+| [**list_supported_tokens**](InformativeApi.md#list_supported_tokens) | **GET** /wallet-as-a-service/info/{blockchain}/{network}/supported-tokens | List Supported Tokens |
+
+
+## get_wallet_asset_details
+
+> <GetWalletAssetDetailsR> get_wallet_asset_details(blockchain, network, wallet_id, opts)
+
+Get Wallet Asset Details
+
+Through this endpoint customers can obtain details about a specific Wallet/Vault.
+
+### 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::InformativeApi.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.
+wallet_id = '60c9d9921c38030006675ff6' # String | Defines the unique ID of the Wallet.
+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.
+}
+
+begin
+  # Get Wallet Asset Details
+  result = api_instance.get_wallet_asset_details(blockchain, network, wallet_id, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InformativeApi->get_wallet_asset_details: #{e}"
+end
+```
+
+#### Using the get_wallet_asset_details_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GetWalletAssetDetailsR>, Integer, Hash)> get_wallet_asset_details_with_http_info(blockchain, network, wallet_id, opts)
+
+```ruby
+begin
+  # Get Wallet Asset Details
+  data, status_code, headers = api_instance.get_wallet_asset_details_with_http_info(blockchain, network, wallet_id, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GetWalletAssetDetailsR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InformativeApi->get_wallet_asset_details_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. |  |
+| **wallet_id** | **String** | Defines the unique ID of the Wallet. |  |
+| **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] |
+
+### Return type
+
+[**GetWalletAssetDetailsR**](GetWalletAssetDetailsR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## list_receiving_addresses
+
+> <ListReceivingAddressesR> list_receiving_addresses(blockchain, network, wallet_id, opts)
+
+List Receiving Addresses
+
+Through this endpoint customers can pull a list of Deposit Addresses they have already generated. Deposit addresses are listed with their specific details such as unique ID.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+
+### 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::InformativeApi.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.
+wallet_id = '60c9d9921c38030006675ff6' # String | Represents the unique ID of the specific Wallet.
+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.
+}
+
+begin
+  # List Receiving Addresses
+  result = api_instance.list_receiving_addresses(blockchain, network, wallet_id, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InformativeApi->list_receiving_addresses: #{e}"
+end
+```
+
+#### Using the list_receiving_addresses_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<ListReceivingAddressesR>, Integer, Hash)> list_receiving_addresses_with_http_info(blockchain, network, wallet_id, opts)
+
+```ruby
+begin
+  # List Receiving Addresses
+  data, status_code, headers = api_instance.list_receiving_addresses_with_http_info(blockchain, network, wallet_id, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <ListReceivingAddressesR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InformativeApi->list_receiving_addresses_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. |  |
+| **wallet_id** | **String** | Represents the unique ID of the specific Wallet. |  |
+| **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] |
+
+### Return type
+
+[**ListReceivingAddressesR**](ListReceivingAddressesR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## list_supported_tokens
+
+> <ListSupportedTokensR> list_supported_tokens(blockchain, network, opts)
+
+List Supported Tokens
+
+Through this endpoint customers can obtain information on multiple tokens at once.     {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+
+### 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::InformativeApi.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.
+  limit: 50, # Integer | Defines how many items should be returned in the response per page basis.
+  offset: 10 # Integer | The starting index of the response items, i.e. where the response should start listing the returned items.
+}
+
+begin
+  # List Supported Tokens
+  result = api_instance.list_supported_tokens(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InformativeApi->list_supported_tokens: #{e}"
+end
+```
+
+#### Using the list_supported_tokens_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<ListSupportedTokensR>, Integer, Hash)> list_supported_tokens_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # List Supported Tokens
+  data, status_code, headers = api_instance.list_supported_tokens_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <ListSupportedTokensR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InformativeApi->list_supported_tokens_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] |
+| **limit** | **Integer** | Defines how many items should be returned in the response per page basis. | [optional][default to 50] |
+| **offset** | **Integer** | The starting index of the response items, i.e. where the response should start listing the returned items. | [optional][default to 0] |
+
+### Return type
+
+[**ListSupportedTokensR**](ListSupportedTokensR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+

data/docs/InternalApi.md

@@ -0,0 +1,173 @@
+# CryptoApis::InternalApi
+
+All URIs are relative to *https://rest.cryptoapis.io/v2*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**get_internal_transaction_by_transaction_hash_and_operation_id**](InternalApi.md#get_internal_transaction_by_transaction_hash_and_operation_id) | **GET** /blockchain-data/{blockchain}/{network}/transactions/{transactionHash}/internal/{operationId} | Get Internal Transaction by Transaction Hash and Operation Id |
+| [**list_internal_transaction_details_by_transaction_hash**](InternalApi.md#list_internal_transaction_details_by_transaction_hash) | **GET** /blockchain-data/{blockchain}/{network}/transactions/{transactionHash}/internal | List Internal Transaction Details by Transaction Hash |
+
+
+## get_internal_transaction_by_transaction_hash_and_operation_id
+
+> <GetInternalTransactionByTransactionHashAndOperationIdR> get_internal_transaction_by_transaction_hash_and_operation_id(blockchain, network, operation_id, transaction_hash, opts)
+
+Get Internal Transaction by Transaction Hash and Operation Id
+
+Through this endpoint customers can obtain detailed information about a specific Internal Transaction by using the attributes `transactionHash`  (the parent transaction's Hash) and `operationId` (type trace address).    An internal transaction is the result of a smart contract being triggered by an EOA or a subsequent contract call.
+
+### 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::InternalApi.new
+blockchain = 'ethereum' # 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.
+operation_id = 'call_4' # String | Represents the unique internal transaction ID in regards to the parent transaction (type trace address).
+transaction_hash = '0x92bb77e16444e0417c8b50dfab68e89c7ad27d4140a766c3bbd4d0ac195f12fc' # String | String identifier of the parent transaction of the internal transaction represented in CryptoAPIs.
+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.
+}
+
+begin
+  # Get Internal Transaction by Transaction Hash and Operation Id
+  result = api_instance.get_internal_transaction_by_transaction_hash_and_operation_id(blockchain, network, operation_id, transaction_hash, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InternalApi->get_internal_transaction_by_transaction_hash_and_operation_id: #{e}"
+end
+```
+
+#### Using the get_internal_transaction_by_transaction_hash_and_operation_id_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GetInternalTransactionByTransactionHashAndOperationIdR>, Integer, Hash)> get_internal_transaction_by_transaction_hash_and_operation_id_with_http_info(blockchain, network, operation_id, transaction_hash, opts)
+
+```ruby
+begin
+  # Get Internal Transaction by Transaction Hash and Operation Id
+  data, status_code, headers = api_instance.get_internal_transaction_by_transaction_hash_and_operation_id_with_http_info(blockchain, network, operation_id, transaction_hash, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GetInternalTransactionByTransactionHashAndOperationIdR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InternalApi->get_internal_transaction_by_transaction_hash_and_operation_id_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. | [default to &#39;ethereum&#39;] |
+| **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. | [default to &#39;ropsten&#39;] |
+| **operation_id** | **String** | Represents the unique internal transaction ID in regards to the parent transaction (type trace address). |  |
+| **transaction_hash** | **String** | String identifier of the parent transaction of the internal transaction represented in CryptoAPIs. |  |
+| **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] |
+
+### Return type
+
+[**GetInternalTransactionByTransactionHashAndOperationIdR**](GetInternalTransactionByTransactionHashAndOperationIdR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## list_internal_transaction_details_by_transaction_hash
+
+> <ListInternalTransactionDetailsByTransactionHashR> list_internal_transaction_details_by_transaction_hash(blockchain, network, transaction_hash, opts)
+
+List Internal Transaction Details by Transaction Hash
+
+Through this endpoint customers can list internal transactions along with their details by a specific attribute `transactionHash`, which is the parent transaction's Hash.    An internal transaction is the result of a smart contract being triggered by an EOA or a subsequent contract call.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+
+### 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::InternalApi.new
+blockchain = 'ethereum' # 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.
+transaction_hash = '0x5d4ea0471b70de09fa3d6a4bc32f703ec44483bffa4d6169fa0a36c6a1dc108a' # String | String identifier of the parent transaction of the internal transaction represented in CryptoAPIs.
+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.
+  limit: 50, # Integer | Defines how many items should be returned in the response per page basis.
+  offset: 10 # Integer | The starting index of the response items, i.e. where the response should start listing the returned items.
+}
+
+begin
+  # List Internal Transaction Details by Transaction Hash
+  result = api_instance.list_internal_transaction_details_by_transaction_hash(blockchain, network, transaction_hash, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InternalApi->list_internal_transaction_details_by_transaction_hash: #{e}"
+end
+```
+
+#### Using the list_internal_transaction_details_by_transaction_hash_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<ListInternalTransactionDetailsByTransactionHashR>, Integer, Hash)> list_internal_transaction_details_by_transaction_hash_with_http_info(blockchain, network, transaction_hash, opts)
+
+```ruby
+begin
+  # List Internal Transaction Details by Transaction Hash
+  data, status_code, headers = api_instance.list_internal_transaction_details_by_transaction_hash_with_http_info(blockchain, network, transaction_hash, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <ListInternalTransactionDetailsByTransactionHashR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling InternalApi->list_internal_transaction_details_by_transaction_hash_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. | [default to &#39;ethereum&#39;] |
+| **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. | [default to &#39;mainnet&#39;] |
+| **transaction_hash** | **String** | String identifier of the parent transaction of the internal transaction represented in CryptoAPIs. |  |
+| **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] |
+| **limit** | **Integer** | Defines how many items should be returned in the response per page basis. | [optional][default to 50] |
+| **offset** | **Integer** | The starting index of the response items, i.e. where the response should start listing the returned items. | [optional][default to 0] |
+
+### Return type
+
+[**ListInternalTransactionDetailsByTransactionHashR**](ListInternalTransactionDetailsByTransactionHashR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+