crypto_apis 1.0.0 → 1.1.0

data/docs/ListZilliqaTransactionsByBlockHeightRData.md

@@ -0,0 +1,24 @@
+# CryptoApis::ListZilliqaTransactionsByBlockHeightRData
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **offset** | **Integer** | The starting index of the response items, i.e. where the response should start listing the returned items. |  |
+| **limit** | **Integer** | Defines how many items should be returned in the response per page basis. |  |
+| **total** | **Integer** | Defines the total number of items returned in the response. |  |
+| **items** | [**Array<ListZilliqaTransactionsByBlockHeightRI>**](ListZilliqaTransactionsByBlockHeightRI.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::ListZilliqaTransactionsByBlockHeightRData.new(
+  offset: 0,
+  limit: 50,
+  total: 100,
+  items: []
+)
+```
+

data/docs/ListZilliqaTransactionsByBlockHeightRI.md

@@ -0,0 +1,40 @@
+# CryptoApis::ListZilliqaTransactionsByBlockHeightRI
+
+## 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. |  |
+| **nonce** | **Integer** | Represents a random value that can be adjusted to satisfy the Proof of Work. |  |
+| **recipients** | [**Array<ListZilliqaTransactionsByAddressRIRecipients>**](ListZilliqaTransactionsByAddressRIRecipients.md) | Defines an object array of the transaction recipients. |  |
+| **senders** | [**Array<ListZilliqaTransactionsByAddressRISenders>**](ListZilliqaTransactionsByAddressRISenders.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_hash** | **String** | Represents the hash of the transaction, which is its unique identifier. |  |
+| **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::ListZilliqaTransactionsByBlockHeightRI.new(
+  fee: null,
+  gas_limit: 550000,
+  gas_price: 2994782927,
+  gas_used: 958,
+  mined_in_block_hash: 0x3160ca05ac12f60023de6b6987596eccbf084629f1a92b59534c5c021bf27041,
+  nonce: 13,
+  recipients: null,
+  senders: null,
+  timestamp: 1582202940,
+  transaction_hash: 0xf4a847a1489a043ee509d5d7df48f2bf7ba1b15354ed14600b035ff2f7670203,
+  transaction_index: 0,
+  transaction_status: 0
+)
+```
+

data/docs/ManageSubscriptionsApi.md

@@ -93,7 +93,7 @@ end
 
 List Blockchain Events Subscriptions
 
-Through this endpoint the customer can obtain a list of their callback subscriptions for the available Blockchain events.    Currently Crypto APIs 2.0 offers certain Blockchain event endpoints which allow the user to subscribe for one/a few/all and receive callback notifications when the specific event occurs.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}
+Through this endpoint the customer can obtain a list of their callback subscriptions for the available Blockchain events.    Currently Crypto APIs 2.0 offers certain Blockchain event endpoints which allow the user to subscribe for one/a few/all and receive callback notifications when the specific event occurs.    {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks [here](https://developers.cryptoapis.io/technical-documentation/general-information/callbacks#callback-url).{/note}    {warning}Crypto APIs will notify the user **only when** the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification **will not** be sent if the event does not or cannot occur, or will take long time to occur.{/warning}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 

data/docs/MetadataApi.md

@@ -13,7 +13,7 @@ All URIs are relative to *https://rest.cryptoapis.io/v2*
 
 List Supported Assets
 
-This endpoint will return a list of supported assets. The asset could be a cryptocurrency or FIAT assets that we support. Each asset has a unique identifier - `assetId` and a unique symbol in the form of a string, e.g. \"BTC\".
+This endpoint will return a list of supported assets. The asset could be a cryptocurrency or FIAT assets that we support. Each asset has a unique identifier - `assetId` and a unique symbol in the form of a string, e.g. \"BTC\".    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 

data/docs/NewConfirmedInternalTransactionsAndEachConfirmationR.md

@@ -0,0 +1,24 @@
+# CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationR
+
+## 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** | [**NewConfirmedInternalTransactionsAndEachConfirmationRData**](NewConfirmedInternalTransactionsAndEachConfirmationRData.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationR.new(
+  api_version: 2.0,
+  request_id: 601c1710034ed6d407996b30,
+  context: You can add any text here,
+  data: null
+)
+```
+

data/docs/NewConfirmedInternalTransactionsAndEachConfirmationRB.md

@@ -0,0 +1,20 @@
+# CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRB
+
+## 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** | [**NewConfirmedInternalTransactionsAndEachConfirmationRBData**](NewConfirmedInternalTransactionsAndEachConfirmationRBData.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRB.new(
+  context: null,
+  data: null
+)
+```
+

data/docs/NewConfirmedInternalTransactionsAndEachConfirmationRBData.md

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

data/docs/NewConfirmedInternalTransactionsAndEachConfirmationRBDataItem.md

@@ -0,0 +1,26 @@
+# CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRBDataItem
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Defines the specific address of the internal transaction. |  |
+| **allow_duplicates** | **Boolean** | Specifies a flag that permits or denies the creation of duplicate addresses. | [default to false] |
+| **callback_secret_key** | **String** | Represents the Secret Key value provided by the customer. This field is used for security purposes during the callback notification, in order to prove the sender of the callback as Crypto APIs. |  |
+| **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. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRBDataItem.new(
+  address: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2,
+  allow_duplicates: true,
+  callback_secret_key: yourSecretString,
+  callback_url: https://example.com,
+  confirmations_count: 3
+)
+```
+

data/docs/NewConfirmedInternalTransactionsAndEachConfirmationRData.md

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

data/docs/NewConfirmedInternalTransactionsAndEachConfirmationRI.md

@@ -0,0 +1,34 @@
+# CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRI
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Defines the specific address of the internal transaction. |  |
+| **callback_secret_key** | **String** | Represents the Secret Key value provided by the customer. This field is used for security purposes during the callback notification, in order to prove the sender of the callback as Crypto APIs. |  |
+| **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 subscription was created in Unix Timestamp. |  |
+| **event_type** | **String** | Defines the type of the specific event available for the customer to subscribe to for callback notification. |  |
+| **is_active** | **Boolean** | Defines whether the subscription is active or not. Set as boolean. |  |
+| **reference_id** | **String** | Represents a unique ID used to reference the specific callback subscription. |  |
+| **transaction_id** | **String** | Represents the unique identification string that defines the transaction. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::NewConfirmedInternalTransactionsAndEachConfirmationRI.new(
+  address: 0xe2b5f5e885a268e4b6faae53f99a663f3bb3e036,
+  callback_secret_key: yourSecretKey,
+  callback_url: https://example.com,
+  confirmations_count: 2,
+  created_timestamp: 1611238648,
+  event_type: ADDRESS_INTERNAL_TRANSACTION_CONFIRMED_EACH_CONFIRMATION,
+  is_active: true,
+  reference_id: bc243c86-0902-4386-b30d-e6b30fa1f2aa,
+  transaction_id: 0xe67f98e281c303dbefa8c6b3e1441ff06742a914ae240e4829629abe7e464960
+)
+```
+

data/docs/NewConfirmedInternalTransactionsR.md

@@ -0,0 +1,24 @@
+# CryptoApis::NewConfirmedInternalTransactionsR
+
+## 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** | [**NewConfirmedInternalTransactionsRData**](NewConfirmedInternalTransactionsRData.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::NewConfirmedInternalTransactionsR.new(
+  api_version: 2.0,
+  request_id: 601c1710034ed6d407996b30,
+  context: You can add any text here,
+  data: null
+)
+```
+

data/docs/NewConfirmedInternalTransactionsRB.md

@@ -0,0 +1,20 @@
+# CryptoApis::NewConfirmedInternalTransactionsRB
+
+## 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** | [**NewConfirmedInternalTransactionsRBData**](NewConfirmedInternalTransactionsRBData.md) |  |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::NewConfirmedInternalTransactionsRB.new(
+  context: null,
+  data: null
+)
+```
+

data/docs/NewConfirmedInternalTransactionsRBData.md

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

data/docs/NewConfirmedInternalTransactionsRBDataItem.md

@@ -0,0 +1,24 @@
+# CryptoApis::NewConfirmedInternalTransactionsRBDataItem
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Defines the specific address of the internal transaction. |  |
+| **allow_duplicates** | **Boolean** | Flag that permits or denies creation of duplicates | [default to false] |
+| **callback_secret_key** | **String** | Represents the Secret Key value provided by the customer. This field is used for security purposes during the callback notification, in order to prove the sender of the callback as Crypto APIs. |  |
+| **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. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::NewConfirmedInternalTransactionsRBDataItem.new(
+  address: 0xbcc817f057950b0df41206c5d7125e6225cae18e,
+  allow_duplicates: true,
+  callback_secret_key: yourSecretKey,
+  callback_url: http://example.com
+)
+```
+

data/docs/NewConfirmedInternalTransactionsRData.md

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

data/docs/NewConfirmedInternalTransactionsRI.md

@@ -0,0 +1,34 @@
+# CryptoApis::NewConfirmedInternalTransactionsRI
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Defines the specific address of the internal transaction. |  |
+| **callback_secret_key** | **String** | Represents the Secret Key value provided by the customer. This field is used for security purposes during the callback notification, in order to prove the sender of the callback as Crypto APIs 2.0. |  |
+| **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 subscription was created in Unix Timestamp. |  |
+| **event_type** | **String** | Defines the type of the specific event available for the customer to subscribe to for callback notification. |  |
+| **is_active** | **Boolean** | Defines whether the subscription is active or not. Set as boolean. |  |
+| **reference_id** | **String** | Represents a unique ID used to reference the specific callback subscription. |  |
+| **transaction_id** | **String** | Represents the unique identification string that defines the transaction. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::NewConfirmedInternalTransactionsRI.new(
+  address: null,
+  callback_secret_key: yourSecretKey,
+  callback_url: https://example.com,
+  confirmations_count: 2,
+  created_timestamp: 1236238648,
+  event_type: ADDRESS_INTERNAL_TRANSACTION_CONFIRMED,
+  is_active: true,
+  reference_id: bc243c86-0902-4386-b30d-e6b30fa1f2aa,
+  transaction_id: 0xe67f98e281c303dbefa8c6b3e1441ff06742a914ae240e4829629abe7e464960
+)
+```
+

data/docs/OmniLayerApi.md

@@ -178,7 +178,7 @@ end
 
 List Omni Tokens By Address
 
-Through this endpoint the customer can receive basic information about a given Omni address based on confirmed/synced blocks only. In the case where there are any incoming or outgoing **unconfirmed** transactions for the specific address, they **will not** be counted or calculated here.
+Through this endpoint the customer can receive basic information about a given Omni address based on confirmed/synced blocks only. In the case where there are any incoming or outgoing **unconfirmed** transactions for the specific address, they **will not** be counted or calculated here.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 
@@ -257,7 +257,7 @@ end
 
 List Omni Transactions By Address
 
-This endpoint will list Omni transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.
+This endpoint will list Omni transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 
@@ -340,7 +340,7 @@ end
 
 List Omni Transactions By Block Hash
 
-This endpoint will list Omni transactions by an attribute `transactionHash`. The transactions listed will detail additional information such as addresses, height, time of creation in Unix timestamp, etc.
+This endpoint will list Omni transactions by an attribute `transactionHash`. The transactions listed will detail additional information such as addresses, height, time of creation in Unix timestamp, etc.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 
@@ -423,7 +423,7 @@ end
 
 List Omni Transactions By Block Height
 
-This endpoint will list Omni transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.
+This endpoint will list Omni transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 
@@ -506,7 +506,7 @@ end
 
 List Unconfirmed Omni Transactions By Address
 
-This endpoint will list unconfirmed Omni transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.
+This endpoint will list unconfirmed Omni transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 
@@ -589,7 +589,7 @@ end
 
 List Unconfirmed Omni Transactions By Property ID
 
-This endpoint will list unconfirmed Omni transactions by an attribute `propertyId`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.
+This endpoint will list unconfirmed Omni transactions by an attribute `propertyId`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 

data/docs/TokensApi.md

@@ -4,18 +4,98 @@ All URIs are relative to *https://rest.cryptoapis.io/v2*
 
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
+| [**get_contract_details_by_address**](TokensApi.md#get_contract_details_by_address) | **GET** /blockchain-data/{blockchain}/{network}/addresses/{contractAddress}/contract | Get Contract Details by Address |
 | [**list_tokens_by_address**](TokensApi.md#list_tokens_by_address) | **GET** /blockchain-data/{blockchain}/{network}/addresses/{address}/tokens | List Tokens By Address |
 | [**list_tokens_transfers_by_address**](TokensApi.md#list_tokens_transfers_by_address) | **GET** /blockchain-data/{blockchain}/{network}/addresses/{address}/tokens-transfers | List Tokens Transfers By Address |
 | [**list_tokens_transfers_by_transaction_hash**](TokensApi.md#list_tokens_transfers_by_transaction_hash) | **GET** /blockchain-data/{blockchain}/{network}/transactions/{transactionHash}/tokens-transfers | List Tokens Transfers By Transaction Hash |
 
 
+## get_contract_details_by_address
+
+> <GetContractDetailsByAddressR> get_contract_details_by_address(blockchain, network, contract_address, opts)
+
+Get Contract Details by Address
+
+Though this endpoint customers can obtain information about a smart contract and its details. This can be done by the `address` parameter, i.e. the address of the smart contract.    {note}This address is **not** the same as the smart contract creator address.{/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::TokensApi.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.
+contract_address = '0x7495fede000c8a3b77eeae09cf70fa94cd2d53f5' # String | Defines the specific address of the contract.
+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 Contract Details by Address
+  result = api_instance.get_contract_details_by_address(blockchain, network, contract_address, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling TokensApi->get_contract_details_by_address: #{e}"
+end
+```
+
+#### Using the get_contract_details_by_address_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GetContractDetailsByAddressR>, Integer, Hash)> get_contract_details_by_address_with_http_info(blockchain, network, contract_address, opts)
+
+```ruby
+begin
+  # Get Contract Details by Address
+  data, status_code, headers = api_instance.get_contract_details_by_address_with_http_info(blockchain, network, contract_address, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GetContractDetailsByAddressR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling TokensApi->get_contract_details_by_address_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. |  |
+| **contract_address** | **String** | Defines the specific address of the contract. |  |
+| **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
+
+[**GetContractDetailsByAddressR**](GetContractDetailsByAddressR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
 ## list_tokens_by_address
 
 > <ListTokensByAddressR> list_tokens_by_address(blockchain, network, address, opts)
 
 List Tokens By Address
 
-Through this endpoint customers can obtain token data by providing an attribute - `address`.  The information that can be returned can include the contract address, the token symbol, type and balance.
+Through this endpoint customers can obtain token data by providing an attribute - `address`.  The information that can be returned can include the contract address, the token symbol, type and balance.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 
@@ -98,7 +178,7 @@ end
 
 List Tokens Transfers By Address
 
-Through this endpoint customers can obtain a list with token transfers by the `address` attribute. Token transfers may include information such as addresses of the sender and recipient, token name, token symbol, etc.    {note}This refers only to transfers done for **tokens** not coins.{/note}
+Through this endpoint customers can obtain a list with token transfers by the `address` attribute. Token transfers may include information such as addresses of the sender and recipient, token name, token symbol, etc.    {note}This refers only to transfers done for **tokens** not coins.{/note}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples
 
@@ -181,7 +261,7 @@ end
 
 List Tokens Transfers By Transaction Hash
 
-Through this endpoint customers can obtain a list with token transfers by the `transactionHash` attribute. Token transfers may include information such as addresses of the sender and recipient, token name, token symbol, etc.    {note}This refers only to transfers done for **tokens** not coins.{/note}
+Through this endpoint customers can obtain a list with token transfers by the `transactionHash` attribute. Token transfers may include information such as addresses of the sender and recipient, token name, token symbol, etc.    {note}This refers only to transfers done for **tokens** not coins.{/note}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
 
 ### Examples