crypto_apis 1.2.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0ae6a9e6f2461aa0fc5219400c04b3d512b2dc15133c78a759290e1bbad3972c
-  data.tar.gz: 63ff9409d66ff7434ea346286513c2e03a2322492983e6fefeb5ace9d2c27cad
+  metadata.gz: 943921a1e1d210c23ca41fcfc237fb73edec85424f6b27e36022ac55b2ce87d6
+  data.tar.gz: 57d585051a399cdcb99a1f88a0458f99791215f7040e9c4c48c95082e548bd95
 SHA512:
-  metadata.gz: c01dad1e54e4944bfdaf93333d58debf53dedc4e1dc241fedbf0d8888eb44781ad16c24d4d55758fe69a8c35b81e2ad0d49ca5123e6db5309b259189067a1f29
-  data.tar.gz: 2e88e3dea6e8c30dda05a1c6f209ae62fb29c4b8397431d579561ba5c4dbe50730e77fc59b3d4abcecf56b7bc326a14713222b88f62ae140471a82d3dfac80d4
+  metadata.gz: 378c85aceb8f54ded301b79ca3db2971544dd0d6b5f50506695d21a10d7746e847a13a6f0cadf5626974c432e97c032c23cef2bc62fc124269fa459e30eb39c5
+  data.tar.gz: 3a385478d600bdadeab2e49a88681909265ae8b6be32faafb649f8adac3e945486a53a4fcde1e54a8edcb6b1acc9add10e65d88166f1b6dcc0c8ab180af8b698

data/README.md

@@ -7,7 +7,7 @@ Crypto APIs 2.0 is a complex and innovative infrastructure layer that radically
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
 - API version: 2.0.0
-- Package version: 1.2.0
+- Package version: 1.2.1
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 For more information, please visit [https://cryptoapis.io](https://cryptoapis.io)
 
@@ -303,7 +303,6 @@ Class | Method | HTTP request | Description
  - [CryptoApis::GetBlockDetailsByBlockHashRIBS](docs/GetBlockDetailsByBlockHashRIBS.md)
  - [CryptoApis::GetBlockDetailsByBlockHashRIBSB](docs/GetBlockDetailsByBlockHashRIBSB.md)
  - [CryptoApis::GetBlockDetailsByBlockHashRIBSBC](docs/GetBlockDetailsByBlockHashRIBSBC.md)
- - [CryptoApis::GetBlockDetailsByBlockHashRIBSBSC](docs/GetBlockDetailsByBlockHashRIBSBSC.md)
  - [CryptoApis::GetBlockDetailsByBlockHashRIBSD](docs/GetBlockDetailsByBlockHashRIBSD.md)
  - [CryptoApis::GetBlockDetailsByBlockHashRIBSD2](docs/GetBlockDetailsByBlockHashRIBSD2.md)
  - [CryptoApis::GetBlockDetailsByBlockHashRIBSE](docs/GetBlockDetailsByBlockHashRIBSE.md)
@@ -315,7 +314,6 @@ Class | Method | HTTP request | Description
  - [CryptoApis::GetBlockDetailsByBlockHeightRIBS](docs/GetBlockDetailsByBlockHeightRIBS.md)
  - [CryptoApis::GetBlockDetailsByBlockHeightRIBSB](docs/GetBlockDetailsByBlockHeightRIBSB.md)
  - [CryptoApis::GetBlockDetailsByBlockHeightRIBSBC](docs/GetBlockDetailsByBlockHeightRIBSBC.md)
- - [CryptoApis::GetBlockDetailsByBlockHeightRIBSBSC](docs/GetBlockDetailsByBlockHeightRIBSBSC.md)
  - [CryptoApis::GetBlockDetailsByBlockHeightRIBSD](docs/GetBlockDetailsByBlockHeightRIBSD.md)
  - [CryptoApis::GetBlockDetailsByBlockHeightRIBSD2](docs/GetBlockDetailsByBlockHeightRIBSD2.md)
  - [CryptoApis::GetBlockDetailsByBlockHeightRIBSE](docs/GetBlockDetailsByBlockHeightRIBSE.md)
@@ -349,7 +347,6 @@ Class | Method | HTTP request | Description
  - [CryptoApis::GetLatestMinedBlockRIBS](docs/GetLatestMinedBlockRIBS.md)
  - [CryptoApis::GetLatestMinedBlockRIBSB](docs/GetLatestMinedBlockRIBSB.md)
  - [CryptoApis::GetLatestMinedBlockRIBSBC](docs/GetLatestMinedBlockRIBSBC.md)
- - [CryptoApis::GetLatestMinedBlockRIBSBSC](docs/GetLatestMinedBlockRIBSBSC.md)
  - [CryptoApis::GetLatestMinedBlockRIBSD](docs/GetLatestMinedBlockRIBSD.md)
  - [CryptoApis::GetLatestMinedBlockRIBSD2](docs/GetLatestMinedBlockRIBSD2.md)
  - [CryptoApis::GetLatestMinedBlockRIBSE](docs/GetLatestMinedBlockRIBSE.md)
@@ -376,8 +373,6 @@ Class | Method | HTTP request | Description
  - [CryptoApis::GetTransactionDetailsByTransactionIDRIBSBCScriptPubKey](docs/GetTransactionDetailsByTransactionIDRIBSBCScriptPubKey.md)
  - [CryptoApis::GetTransactionDetailsByTransactionIDRIBSBCVin](docs/GetTransactionDetailsByTransactionIDRIBSBCVin.md)
  - [CryptoApis::GetTransactionDetailsByTransactionIDRIBSBCVout](docs/GetTransactionDetailsByTransactionIDRIBSBCVout.md)
- - [CryptoApis::GetTransactionDetailsByTransactionIDRIBSBSC](docs/GetTransactionDetailsByTransactionIDRIBSBSC.md)
- - [CryptoApis::GetTransactionDetailsByTransactionIDRIBSBSCGasPrice](docs/GetTransactionDetailsByTransactionIDRIBSBSCGasPrice.md)
  - [CryptoApis::GetTransactionDetailsByTransactionIDRIBSBScriptPubKey](docs/GetTransactionDetailsByTransactionIDRIBSBScriptPubKey.md)
  - [CryptoApis::GetTransactionDetailsByTransactionIDRIBSBScriptSig](docs/GetTransactionDetailsByTransactionIDRIBSBScriptSig.md)
  - [CryptoApis::GetTransactionDetailsByTransactionIDRIBSBVin](docs/GetTransactionDetailsByTransactionIDRIBSBVin.md)
@@ -543,7 +538,6 @@ Class | Method | HTTP request | Description
  - [CryptoApis::ListTransactionsByAddressRIBSB](docs/ListTransactionsByAddressRIBSB.md)
  - [CryptoApis::ListTransactionsByAddressRIBSBC](docs/ListTransactionsByAddressRIBSBC.md)
  - [CryptoApis::ListTransactionsByAddressRIBSBCVin](docs/ListTransactionsByAddressRIBSBCVin.md)
- - [CryptoApis::ListTransactionsByAddressRIBSBSC](docs/ListTransactionsByAddressRIBSBSC.md)
  - [CryptoApis::ListTransactionsByAddressRIBSBScriptPubKey](docs/ListTransactionsByAddressRIBSBScriptPubKey.md)
  - [CryptoApis::ListTransactionsByAddressRIBSBVin](docs/ListTransactionsByAddressRIBSBVin.md)
  - [CryptoApis::ListTransactionsByAddressRIBSBVout](docs/ListTransactionsByAddressRIBSBVout.md)
@@ -571,7 +565,6 @@ Class | Method | HTTP request | Description
  - [CryptoApis::ListTransactionsByBlockHashRIBSBCScriptPubKey](docs/ListTransactionsByBlockHashRIBSBCScriptPubKey.md)
  - [CryptoApis::ListTransactionsByBlockHashRIBSBCVin](docs/ListTransactionsByBlockHashRIBSBCVin.md)
  - [CryptoApis::ListTransactionsByBlockHashRIBSBCVout](docs/ListTransactionsByBlockHashRIBSBCVout.md)
- - [CryptoApis::ListTransactionsByBlockHashRIBSBSC](docs/ListTransactionsByBlockHashRIBSBSC.md)
  - [CryptoApis::ListTransactionsByBlockHashRIBSBVin](docs/ListTransactionsByBlockHashRIBSBVin.md)
  - [CryptoApis::ListTransactionsByBlockHashRIBSD](docs/ListTransactionsByBlockHashRIBSD.md)
  - [CryptoApis::ListTransactionsByBlockHashRIBSD2](docs/ListTransactionsByBlockHashRIBSD2.md)
@@ -598,8 +591,6 @@ Class | Method | HTTP request | Description
  - [CryptoApis::ListTransactionsByBlockHeightRIBS](docs/ListTransactionsByBlockHeightRIBS.md)
  - [CryptoApis::ListTransactionsByBlockHeightRIBSB](docs/ListTransactionsByBlockHeightRIBSB.md)
  - [CryptoApis::ListTransactionsByBlockHeightRIBSBC](docs/ListTransactionsByBlockHeightRIBSBC.md)
- - [CryptoApis::ListTransactionsByBlockHeightRIBSBSC](docs/ListTransactionsByBlockHeightRIBSBSC.md)
- - [CryptoApis::ListTransactionsByBlockHeightRIBSBSCGasPrice](docs/ListTransactionsByBlockHeightRIBSBSCGasPrice.md)
  - [CryptoApis::ListTransactionsByBlockHeightRIBSBScriptPubKey](docs/ListTransactionsByBlockHeightRIBSBScriptPubKey.md)
  - [CryptoApis::ListTransactionsByBlockHeightRIBSBVout](docs/ListTransactionsByBlockHeightRIBSBVout.md)
  - [CryptoApis::ListTransactionsByBlockHeightRIBSD](docs/ListTransactionsByBlockHeightRIBSD.md)

data/docs/AssetsApi.md

@@ -13,7 +13,7 @@ All URIs are relative to *https://rest.cryptoapis.io/v2*
 
 List Assets Details
 
-This endpoint will return details on a requested asset. The asset could be a cryptocurrency or FIAT asset that we support. Each asset has a unique identifier - `assetId` and a unique symbol in the form of a string, e.g. \"BTC\".    The details returned could include information on the latest rate and rate fluctuation of different periods of time - 24 hours, a week, one hour, the encoding of the logo, and more.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+This endpoint will return details on a requested asset. The asset could be a cryptocurrency or FIAT asset that we support. Each asset has a unique identifier - `assetId` and a unique symbol in the form of a string, e.g. \"BTC\".    The details returned could include information on the latest rate and rate fluctuation of different periods of time - 24 hours, a week, one hour, the encoding of the logo, and more.
 
 ### Examples
 

data/docs/AutomaticCoinsForwardingApi.md

@@ -173,7 +173,7 @@ end
 
 List Coins Forwarding Automations
 
-Through this endpoint customers can list all of their **coins** forwarding automations (**not** tokens).    Customers can set up automatic forwarding functions for coins by setting a `fromAddress` and a `toAddress`, and specifying the amount that can be transferred between addresses.     A `feePriority` will be returned which represents the fee priority of the automation whether it is \"SLOW\", \"STANDARD\" OR \"FAST\".    {warning}The subscription will work for all incoming transactions until it is deleted. There is no need to do that for every transaction.{/warning}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+Through this endpoint customers can list all of their **coins** forwarding automations (**not** tokens).    Customers can set up automatic forwarding functions for coins by setting a `fromAddress` and a `toAddress`, and specifying the amount that can be transferred between addresses.     A `feePriority` will be returned which represents the fee priority of the automation whether it is \"SLOW\", \"STANDARD\" OR \"FAST\".    {warning}The subscription will work for all transactions until it is deleted. There is no need to do that for every transaction.{/warning}
 
 ### Examples
 

data/docs/AutomaticTokensForwardingApi.md

@@ -331,7 +331,7 @@ end
 
 List Tokens Forwarding Automations
 
-Through this endpoint customers can list all of their **tokens** forwarding automations (**not** coins).    Customers can set up automatic forwarding functions for tokens by setting a `fromAddress` and a `toAddress`, and specifying the amount that can be transferred between addresses.     A `feePriority` will be returned which represents the fee priority of the automation whether it is \"SLOW\", \"STANDARD\" OR \"FAST\".     {warning}The subscription will work for all incoming transactions until it is deleted. There is no need to do that for every transaction.{/warning}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+Through this endpoint customers can list all of their **tokens** forwarding automations (**not** coins).    Customers can set up automatic forwarding functions for tokens by setting a `fromAddress` and a `toAddress`, and specifying the amount that can be transferred between addresses.     A `feePriority` will be returned which represents the fee priority of the automation whether it is \"SLOW\", \"STANDARD\" OR \"FAST\".     {warning}The subscription will work for all transactions until it is deleted. There is no need to do that for every transaction.{/warning}
 
 ### Examples
 

data/docs/GetBlockDetailsByBlockHashRIBS.md

@@ -16,7 +16,6 @@ CryptoApis::GetBlockDetailsByBlockHashRIBS.openapi_one_of
 # [
 #   :'GetBlockDetailsByBlockHashRIBSB',
 #   :'GetBlockDetailsByBlockHashRIBSBC',
-#   :'GetBlockDetailsByBlockHashRIBSBSC',
 #   :'GetBlockDetailsByBlockHashRIBSD',
 #   :'GetBlockDetailsByBlockHashRIBSD2',
 #   :'GetBlockDetailsByBlockHashRIBSE',
@@ -51,7 +50,6 @@ CryptoApis::GetBlockDetailsByBlockHashRIBS.build(data_that_doesnt_match)
 
 - `GetBlockDetailsByBlockHashRIBSB`
 - `GetBlockDetailsByBlockHashRIBSBC`
-- `GetBlockDetailsByBlockHashRIBSBSC`
 - `GetBlockDetailsByBlockHashRIBSD`
 - `GetBlockDetailsByBlockHashRIBSD2`
 - `GetBlockDetailsByBlockHashRIBSE`

data/docs/GetBlockDetailsByBlockHeightRIBS.md

@@ -16,7 +16,6 @@ CryptoApis::GetBlockDetailsByBlockHeightRIBS.openapi_one_of
 # [
 #   :'GetBlockDetailsByBlockHeightRIBSB',
 #   :'GetBlockDetailsByBlockHeightRIBSBC',
-#   :'GetBlockDetailsByBlockHeightRIBSBSC',
 #   :'GetBlockDetailsByBlockHeightRIBSD',
 #   :'GetBlockDetailsByBlockHeightRIBSD2',
 #   :'GetBlockDetailsByBlockHeightRIBSE',
@@ -51,7 +50,6 @@ CryptoApis::GetBlockDetailsByBlockHeightRIBS.build(data_that_doesnt_match)
 
 - `GetBlockDetailsByBlockHeightRIBSB`
 - `GetBlockDetailsByBlockHeightRIBSBC`
-- `GetBlockDetailsByBlockHeightRIBSBSC`
 - `GetBlockDetailsByBlockHeightRIBSD`
 - `GetBlockDetailsByBlockHeightRIBSD2`
 - `GetBlockDetailsByBlockHeightRIBSE`

data/docs/GetLatestMinedBlockRIBS.md

@@ -16,7 +16,6 @@ CryptoApis::GetLatestMinedBlockRIBS.openapi_one_of
 # [
 #   :'GetLatestMinedBlockRIBSB',
 #   :'GetLatestMinedBlockRIBSBC',
-#   :'GetLatestMinedBlockRIBSBSC',
 #   :'GetLatestMinedBlockRIBSD',
 #   :'GetLatestMinedBlockRIBSD2',
 #   :'GetLatestMinedBlockRIBSE',
@@ -51,7 +50,6 @@ CryptoApis::GetLatestMinedBlockRIBS.build(data_that_doesnt_match)
 
 - `GetLatestMinedBlockRIBSB`
 - `GetLatestMinedBlockRIBSBC`
-- `GetLatestMinedBlockRIBSBSC`
 - `GetLatestMinedBlockRIBSD`
 - `GetLatestMinedBlockRIBSD2`
 - `GetLatestMinedBlockRIBSE`

data/docs/GetTransactionDetailsByTransactionIDRIBS.md

@@ -16,7 +16,6 @@ CryptoApis::GetTransactionDetailsByTransactionIDRIBS.openapi_one_of
 # [
 #   :'GetTransactionDetailsByTransactionIDRIBSB',
 #   :'GetTransactionDetailsByTransactionIDRIBSBC',
-#   :'GetTransactionDetailsByTransactionIDRIBSBSC',
 #   :'GetTransactionDetailsByTransactionIDRIBSD',
 #   :'GetTransactionDetailsByTransactionIDRIBSD2',
 #   :'GetTransactionDetailsByTransactionIDRIBSE',
@@ -51,7 +50,6 @@ CryptoApis::GetTransactionDetailsByTransactionIDRIBS.build(data_that_doesnt_matc
 
 - `GetTransactionDetailsByTransactionIDRIBSB`
 - `GetTransactionDetailsByTransactionIDRIBSBC`
-- `GetTransactionDetailsByTransactionIDRIBSBSC`
 - `GetTransactionDetailsByTransactionIDRIBSD`
 - `GetTransactionDetailsByTransactionIDRIBSD2`
 - `GetTransactionDetailsByTransactionIDRIBSE`

data/docs/InformativeApi.md

@@ -173,7 +173,7 @@ end
 
 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}
+Through this endpoint customers can obtain information on multiple tokens at once.
 
 ### Examples
 

data/docs/InternalApi.md

@@ -95,7 +95,7 @@ end
 
 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}
+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.
 
 ### Examples
 

data/docs/ListTransactionsByAddressRIBS.md

@@ -16,7 +16,6 @@ CryptoApis::ListTransactionsByAddressRIBS.openapi_one_of
 # [
 #   :'ListTransactionsByAddressRIBSB',
 #   :'ListTransactionsByAddressRIBSBC',
-#   :'ListTransactionsByAddressRIBSBSC',
 #   :'ListTransactionsByAddressRIBSD',
 #   :'ListTransactionsByAddressRIBSD2',
 #   :'ListTransactionsByAddressRIBSE',
@@ -51,7 +50,6 @@ CryptoApis::ListTransactionsByAddressRIBS.build(data_that_doesnt_match)
 
 - `ListTransactionsByAddressRIBSB`
 - `ListTransactionsByAddressRIBSBC`
-- `ListTransactionsByAddressRIBSBSC`
 - `ListTransactionsByAddressRIBSD`
 - `ListTransactionsByAddressRIBSD2`
 - `ListTransactionsByAddressRIBSE`

data/docs/ListTransactionsByBlockHashRIBS.md

@@ -16,7 +16,6 @@ CryptoApis::ListTransactionsByBlockHashRIBS.openapi_one_of
 # [
 #   :'ListTransactionsByBlockHashRIBSB',
 #   :'ListTransactionsByBlockHashRIBSBC',
-#   :'ListTransactionsByBlockHashRIBSBSC',
 #   :'ListTransactionsByBlockHashRIBSD',
 #   :'ListTransactionsByBlockHashRIBSD2',
 #   :'ListTransactionsByBlockHashRIBSE',
@@ -51,7 +50,6 @@ CryptoApis::ListTransactionsByBlockHashRIBS.build(data_that_doesnt_match)
 
 - `ListTransactionsByBlockHashRIBSB`
 - `ListTransactionsByBlockHashRIBSBC`
-- `ListTransactionsByBlockHashRIBSBSC`
 - `ListTransactionsByBlockHashRIBSD`
 - `ListTransactionsByBlockHashRIBSD2`
 - `ListTransactionsByBlockHashRIBSE`

data/docs/ListTransactionsByBlockHeightRIBS.md

@@ -16,7 +16,6 @@ CryptoApis::ListTransactionsByBlockHeightRIBS.openapi_one_of
 # [
 #   :'ListTransactionsByBlockHeightRIBSB',
 #   :'ListTransactionsByBlockHeightRIBSBC',
-#   :'ListTransactionsByBlockHeightRIBSBSC',
 #   :'ListTransactionsByBlockHeightRIBSD',
 #   :'ListTransactionsByBlockHeightRIBSD2',
 #   :'ListTransactionsByBlockHeightRIBSE',
@@ -51,7 +50,6 @@ CryptoApis::ListTransactionsByBlockHeightRIBS.build(data_that_doesnt_match)
 
 - `ListTransactionsByBlockHeightRIBSB`
 - `ListTransactionsByBlockHeightRIBSBC`
-- `ListTransactionsByBlockHeightRIBSBSC`
 - `ListTransactionsByBlockHeightRIBSD`
 - `ListTransactionsByBlockHeightRIBSD2`
 - `ListTransactionsByBlockHeightRIBSE`

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}    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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}
 
 ### 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\".    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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\".
 
 ### Examples
 

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.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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.
 
 ### 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.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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.
 
 ### 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.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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.
 
 ### 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.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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.
 
 ### 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.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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.
 
 ### 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.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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.
 
 ### Examples
 

data/docs/TokensApi.md

@@ -95,7 +95,7 @@ end
 
 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.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+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.
 
 ### Examples
 
@@ -178,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}    {note}Please note that listing data from the same type will apply pagination on the results.{/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}
 
 ### Examples
 
@@ -261,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}    {note}Please note that listing data from the same type will apply pagination on the results.{/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}
 
 ### Examples
 

data/docs/UTXOBasedApi.md

@@ -96,7 +96,7 @@ end
 
 List HD Wallet (xPub, yPub, zPub) Transactions
 
-This endpoint will list HD Wallet transactions.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+This endpoint will list HD Wallet transactions.
 
 ### Examples
 

data/docs/UnifiedEndpointsApi.md

@@ -491,7 +491,7 @@ end
 
 List Transactions By Address
 
-This endpoint will list transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+This endpoint will list transactions by an attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.
 
 ### Examples
 
@@ -574,7 +574,7 @@ end
 
 List Transactions by Block Hash
 
-This endpoint will list transactions by an attribute `transactionHash`. The transactions listed will detail additional information such as addresses, height, time of creation in Unix timestamp, etc.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+This endpoint will list transactions by an attribute `transactionHash`. The transactions listed will detail additional information such as addresses, height, time of creation in Unix timestamp, etc.
 
 ### Examples
 
@@ -657,7 +657,7 @@ end
 
 List Transactions by Block Height
 
-This endpoint will list transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+This endpoint will list transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.
 
 ### Examples
 

data/docs/XRPRippleApi.md

@@ -403,7 +403,7 @@ end
 
 List XRP (Ripple) Transactions by Address
 
-This endpoint will list XRP transactions by a attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+This endpoint will list XRP transactions by a attribute `address`. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
 
 ### Examples
 
@@ -486,7 +486,7 @@ end
 
 List XRP (Ripple) Transactions By Block Hash
 
-This endpoint will list transactions by an attribute `blockHash`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+This endpoint will list transactions by an attribute `blockHash`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
 
 ### Examples
 
@@ -567,7 +567,7 @@ end
 
 List XRP (Ripple) Transactions By Block Height
 
-This endpoint will list transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+This endpoint will list transactions by an attribute `blockHeight`. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
 
 ### Examples
 

data/docs/ZilliqaApi.md

@@ -403,7 +403,7 @@ end
 
 List Zilliqa Transactions by Address
 
-Through this endpoint customers can list transactions on the Zilliqa blockchain by the address parameter.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+Through this endpoint customers can list transactions on the Zilliqa blockchain by the address parameter.
 
 ### Examples
 
@@ -484,7 +484,7 @@ end
 
 List Zilliqa Transactions By Block Hash
 
-Through this endpoint customers can list transactions on the Zilliqa blockchain by the block hash parameter.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+Through this endpoint customers can list transactions on the Zilliqa blockchain by the block hash parameter.
 
 ### Examples
 
@@ -565,7 +565,7 @@ end
 
 List Zilliqa Transactions By Block Height
 
-Through this endpoint customers can list transactions on the Zilliqa blockchain by the block height parameter.    {note}Please note that listing data from the same type will apply pagination on the results.{/note}
+Through this endpoint customers can list transactions on the Zilliqa blockchain by the block height parameter.
 
 ### Examples
 

data/lib/crypto_apis.rb

@@ -182,7 +182,6 @@ require 'crypto_apis/models/get_block_details_by_block_hash_ri'
 require 'crypto_apis/models/get_block_details_by_block_hash_ribs'
 require 'crypto_apis/models/get_block_details_by_block_hash_ribsb'
 require 'crypto_apis/models/get_block_details_by_block_hash_ribsbc'
-require 'crypto_apis/models/get_block_details_by_block_hash_ribsbsc'
 require 'crypto_apis/models/get_block_details_by_block_hash_ribsd'
 require 'crypto_apis/models/get_block_details_by_block_hash_ribsd2'
 require 'crypto_apis/models/get_block_details_by_block_hash_ribse'
@@ -194,7 +193,6 @@ require 'crypto_apis/models/get_block_details_by_block_height_ri'
 require 'crypto_apis/models/get_block_details_by_block_height_ribs'
 require 'crypto_apis/models/get_block_details_by_block_height_ribsb'
 require 'crypto_apis/models/get_block_details_by_block_height_ribsbc'
-require 'crypto_apis/models/get_block_details_by_block_height_ribsbsc'
 require 'crypto_apis/models/get_block_details_by_block_height_ribsd'
 require 'crypto_apis/models/get_block_details_by_block_height_ribsd2'
 require 'crypto_apis/models/get_block_details_by_block_height_ribse'
@@ -228,7 +226,6 @@ require 'crypto_apis/models/get_latest_mined_block_ri'
 require 'crypto_apis/models/get_latest_mined_block_ribs'
 require 'crypto_apis/models/get_latest_mined_block_ribsb'
 require 'crypto_apis/models/get_latest_mined_block_ribsbc'
-require 'crypto_apis/models/get_latest_mined_block_ribsbsc'
 require 'crypto_apis/models/get_latest_mined_block_ribsd'
 require 'crypto_apis/models/get_latest_mined_block_ribsd2'
 require 'crypto_apis/models/get_latest_mined_block_ribse'
@@ -255,8 +252,6 @@ require 'crypto_apis/models/get_transaction_details_by_transaction_idribsbc'
 require 'crypto_apis/models/get_transaction_details_by_transaction_idribsbc_script_pub_key'
 require 'crypto_apis/models/get_transaction_details_by_transaction_idribsbc_vin'
 require 'crypto_apis/models/get_transaction_details_by_transaction_idribsbc_vout'
-require 'crypto_apis/models/get_transaction_details_by_transaction_idribsbsc'
-require 'crypto_apis/models/get_transaction_details_by_transaction_idribsbsc_gas_price'
 require 'crypto_apis/models/get_transaction_details_by_transaction_idribsb_script_pub_key'
 require 'crypto_apis/models/get_transaction_details_by_transaction_idribsb_script_sig'
 require 'crypto_apis/models/get_transaction_details_by_transaction_idribsb_vin'
@@ -422,7 +417,6 @@ require 'crypto_apis/models/list_transactions_by_address_ribs'
 require 'crypto_apis/models/list_transactions_by_address_ribsb'
 require 'crypto_apis/models/list_transactions_by_address_ribsbc'
 require 'crypto_apis/models/list_transactions_by_address_ribsbc_vin'
-require 'crypto_apis/models/list_transactions_by_address_ribsbsc'
 require 'crypto_apis/models/list_transactions_by_address_ribsb_script_pub_key'
 require 'crypto_apis/models/list_transactions_by_address_ribsb_vin'
 require 'crypto_apis/models/list_transactions_by_address_ribsb_vout'
@@ -450,7 +444,6 @@ require 'crypto_apis/models/list_transactions_by_block_hash_ribsbc'
 require 'crypto_apis/models/list_transactions_by_block_hash_ribsbc_script_pub_key'
 require 'crypto_apis/models/list_transactions_by_block_hash_ribsbc_vin'
 require 'crypto_apis/models/list_transactions_by_block_hash_ribsbc_vout'
-require 'crypto_apis/models/list_transactions_by_block_hash_ribsbsc'
 require 'crypto_apis/models/list_transactions_by_block_hash_ribsb_vin'
 require 'crypto_apis/models/list_transactions_by_block_hash_ribsd'
 require 'crypto_apis/models/list_transactions_by_block_hash_ribsd2'
@@ -477,8 +470,6 @@ require 'crypto_apis/models/list_transactions_by_block_height_ri'
 require 'crypto_apis/models/list_transactions_by_block_height_ribs'
 require 'crypto_apis/models/list_transactions_by_block_height_ribsb'
 require 'crypto_apis/models/list_transactions_by_block_height_ribsbc'
-require 'crypto_apis/models/list_transactions_by_block_height_ribsbsc'
-require 'crypto_apis/models/list_transactions_by_block_height_ribsbsc_gas_price'
 require 'crypto_apis/models/list_transactions_by_block_height_ribsb_script_pub_key'
 require 'crypto_apis/models/list_transactions_by_block_height_ribsb_vout'
 require 'crypto_apis/models/list_transactions_by_block_height_ribsd'