crypto_apis 1.0.0

data/docs/UnsupportedMediaType.md

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

data/docs/UnsupportedMediaTypeError.md

@@ -0,0 +1,22 @@
+# CryptoApis::UnsupportedMediaTypeError
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **code** | **String** | Specifies an error code, e.g. error 404. |  |
+| **message** | **String** | Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”. |  |
+| **details** | [**Array<BannedIpAddressErrorDetails>**](BannedIpAddressErrorDetails.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::UnsupportedMediaTypeError.new(
+  code: unsupported_media_type,
+  message: The selected Media Type is unavailable. The Content-Type header should be 'application/json'.,
+  details: null
+)
+```
+

data/docs/UriNotFound.md

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

data/docs/UriNotFoundError.md

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

data/docs/ValidateAddressR.md

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

data/docs/ValidateAddressRB.md

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

data/docs/ValidateAddressRBData.md

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

data/docs/ValidateAddressRBDataItem.md

@@ -0,0 +1,18 @@
+# CryptoApis::ValidateAddressRBDataItem
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Represents the specific address that will be checked if it's valid or not. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::ValidateAddressRBDataItem.new(
+  address: mho4jHBcrNCncKt38trJahXakuaBnS7LK5
+)
+```
+

data/docs/ValidateAddressRData.md

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

data/docs/ValidateAddressRI.md

@@ -0,0 +1,20 @@
+# CryptoApis::ValidateAddressRI
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **address** | **String** | Represents the specific address that will be checked if it's valid or not. |  |
+| **is_valid** | **Boolean** | Defines whether the address is valid or not. Set as boolean. |  |
+
+## Example
+
+```ruby
+require 'crypto_apis'
+
+instance = CryptoApis::ValidateAddressRI.new(
+  address: 15XyNC88pujwuuur8DCsXBCfEhJJMzHayU,
+  is_valid: true
+)
+```
+

data/docs/ValidatingApi.md

@@ -0,0 +1,87 @@
+# CryptoApis::ValidatingApi
+
+All URIs are relative to *https://rest.cryptoapis.io/v2*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**validate_address**](ValidatingApi.md#validate_address) | **POST** /blockchain-tools/{blockchain}/{network}/addresses/validate | Validate Address |
+
+
+## validate_address
+
+> <ValidateAddressR> validate_address(blockchain, network, opts)
+
+Validate Address
+
+This endpoint checks user public addresses whether they are valid or not.
+
+### 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::ValidatingApi.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.
+  validate_address_rb: CryptoApis::ValidateAddressRB.new({data: CryptoApis::ValidateAddressRBData.new({item: CryptoApis::ValidateAddressRBDataItem.new({address: 'mho4jHBcrNCncKt38trJahXakuaBnS7LK5'})})}) # ValidateAddressRB | 
+}
+
+begin
+  # Validate Address
+  result = api_instance.validate_address(blockchain, network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling ValidatingApi->validate_address: #{e}"
+end
+```
+
+#### Using the validate_address_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<ValidateAddressR>, Integer, Hash)> validate_address_with_http_info(blockchain, network, opts)
+
+```ruby
+begin
+  # Validate Address
+  data, status_code, headers = api_instance.validate_address_with_http_info(blockchain, network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <ValidateAddressR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling ValidatingApi->validate_address_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] |
+| **validate_address_rb** | [**ValidateAddressRB**](ValidateAddressRB.md) |  | [optional] |
+
+### Return type
+
+[**ValidateAddressR**](ValidateAddressR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+

data/docs/XRPRippleApi.md

@@ -0,0 +1,559 @@
+# CryptoApis::XRPRippleApi
+
+All URIs are relative to *https://rest.cryptoapis.io/v2*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**get_latest_mined_xrp__ripple_block**](XRPRippleApi.md#get_latest_mined_xrp__ripple_block) | **GET** /blockchain-data/xrp/{network}/blocks/last | Get Latest Mined XRP (Ripple) Block |
+| [**get_xrp__ripple_address_details**](XRPRippleApi.md#get_xrp__ripple_address_details) | **GET** /blockchain-data/xrp/{network}/addresses/{address} | Get XRP (Ripple) Address Details |
+| [**get_xrp__ripple_block_details_by_block_hash**](XRPRippleApi.md#get_xrp__ripple_block_details_by_block_hash) | **GET** /blockchain-data/xrp/{network}/blocks/hash/{blockHash} | Get XRP (Ripple) Block Details By Block Hash |
+| [**get_xrp__ripple_block_details_by_block_height**](XRPRippleApi.md#get_xrp__ripple_block_details_by_block_height) | **GET** /blockchain-data/xrp/{network}/blocks/height/{height} | Get XRP (Ripple) Block Details By Block Height |
+| [**get_xrp__ripple_transaction_details_by_transaction_id**](XRPRippleApi.md#get_xrp__ripple_transaction_details_by_transaction_id) | **GET** /blockchain-data/xrp/{network}/transactions/{transactionHash} | Get XRP (Ripple) Transaction Details By Transaction ID |
+| [**list_xrp__ripple_transactions_by_address**](XRPRippleApi.md#list_xrp__ripple_transactions_by_address) | **GET** /blockchain-data/xrp/{network}/addresses/{address}/transactions | List XRP (Ripple) Transactions by Address |
+| [**list_xrp__ripple_transactions_by_block_hash**](XRPRippleApi.md#list_xrp__ripple_transactions_by_block_hash) | **GET** /blockchain-data/xrp/{network}/blocks/hash/{blockHash}/transactions | List XRP (Ripple) Transactions By Block Hash |
+
+
+## get_latest_mined_xrp__ripple_block
+
+> <GetLatestMinedXRPRippleBlockR> get_latest_mined_xrp__ripple_block(network, opts)
+
+Get Latest Mined XRP (Ripple) Block
+
+Through this endpoint customers can fetch the last mined XRP block in the blockchain, along with its details. These could include the hash of the specific, the previous and the next block, its transactions count, its height, etc.     Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
+
+### 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::XRPRippleApi.new
+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.
+}
+
+begin
+  # Get Latest Mined XRP (Ripple) Block
+  result = api_instance.get_latest_mined_xrp__ripple_block(network, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_latest_mined_xrp__ripple_block: #{e}"
+end
+```
+
+#### Using the get_latest_mined_xrp__ripple_block_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GetLatestMinedXRPRippleBlockR>, Integer, Hash)> get_latest_mined_xrp__ripple_block_with_http_info(network, opts)
+
+```ruby
+begin
+  # Get Latest Mined XRP (Ripple) Block
+  data, status_code, headers = api_instance.get_latest_mined_xrp__ripple_block_with_http_info(network, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GetLatestMinedXRPRippleBlockR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_latest_mined_xrp__ripple_block_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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] |
+
+### Return type
+
+[**GetLatestMinedXRPRippleBlockR**](GetLatestMinedXRPRippleBlockR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## get_xrp__ripple_address_details
+
+> <GetXRPRippleAddressDetailsR> get_xrp__ripple_address_details(network, address, opts)
+
+Get XRP (Ripple) Address Details
+
+Through this endpoint the customer can receive basic information about a given XRP 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.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
+
+### 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::XRPRippleApi.new
+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\",  are test networks.
+address = 'rA9bXGJcXvZKaWofrRphdJsBWzhyCfH3z' # String | Represents the public address, which is a compressed and shortened form of a public key.
+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 XRP (Ripple) Address Details
+  result = api_instance.get_xrp__ripple_address_details(network, address, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_xrp__ripple_address_details: #{e}"
+end
+```
+
+#### Using the get_xrp__ripple_address_details_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GetXRPRippleAddressDetailsR>, Integer, Hash)> get_xrp__ripple_address_details_with_http_info(network, address, opts)
+
+```ruby
+begin
+  # Get XRP (Ripple) Address Details
+  data, status_code, headers = api_instance.get_xrp__ripple_address_details_with_http_info(network, address, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GetXRPRippleAddressDetailsR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_xrp__ripple_address_details_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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;,  are test networks. |  |
+| **address** | **String** | Represents the public address, which is a compressed and shortened form of a public key. |  |
+| **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
+
+[**GetXRPRippleAddressDetailsR**](GetXRPRippleAddressDetailsR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## get_xrp__ripple_block_details_by_block_hash
+
+> <GetXRPRippleBlockDetailsByBlockHashR> get_xrp__ripple_block_details_by_block_hash(network, block_hash, opts)
+
+Get XRP (Ripple) Block Details By Block Hash
+
+Through this endpoint customers can obtain basic information about a given XRP block (a block on the XRP blockchain), specifically by using the `hash` parameter. These block details could include the hash of the specific, the previous and the next block, the number of included transactions, etc.     Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
+
+### 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::XRPRippleApi.new
+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\",  are test networks.
+block_hash = '1ab0614d2a438da8b23086cbceef7d443edbd295d9c7619fc8a19c7618bc22c9' # 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.
+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 XRP (Ripple) Block Details By Block Hash
+  result = api_instance.get_xrp__ripple_block_details_by_block_hash(network, block_hash, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_xrp__ripple_block_details_by_block_hash: #{e}"
+end
+```
+
+#### Using the get_xrp__ripple_block_details_by_block_hash_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GetXRPRippleBlockDetailsByBlockHashR>, Integer, Hash)> get_xrp__ripple_block_details_by_block_hash_with_http_info(network, block_hash, opts)
+
+```ruby
+begin
+  # Get XRP (Ripple) Block Details By Block Hash
+  data, status_code, headers = api_instance.get_xrp__ripple_block_details_by_block_hash_with_http_info(network, block_hash, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GetXRPRippleBlockDetailsByBlockHashR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_xrp__ripple_block_details_by_block_hash_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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;,  are test networks. |  |
+| **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. |  |
+| **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
+
+[**GetXRPRippleBlockDetailsByBlockHashR**](GetXRPRippleBlockDetailsByBlockHashR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## get_xrp__ripple_block_details_by_block_height
+
+> <GetXRPRippleBlockDetailsByBlockHeightR> get_xrp__ripple_block_details_by_block_height(network, height, opts)
+
+Get XRP (Ripple) Block Details By Block Height
+
+Through this endpoint customers can obtain basic information about a given XRP block (a block on the XRP blockchain), specifically by using the `height` parameter. These block details could include the hash of the specific, the previous and the next block, its transactions count, etc.    Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
+
+### 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::XRPRippleApi.new
+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\",  are test networks.
+height = '15886156' # String | 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\".
+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 XRP (Ripple) Block Details By Block Height
+  result = api_instance.get_xrp__ripple_block_details_by_block_height(network, height, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_xrp__ripple_block_details_by_block_height: #{e}"
+end
+```
+
+#### Using the get_xrp__ripple_block_details_by_block_height_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GetXRPRippleBlockDetailsByBlockHeightR>, Integer, Hash)> get_xrp__ripple_block_details_by_block_height_with_http_info(network, height, opts)
+
+```ruby
+begin
+  # Get XRP (Ripple) Block Details By Block Height
+  data, status_code, headers = api_instance.get_xrp__ripple_block_details_by_block_height_with_http_info(network, height, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GetXRPRippleBlockDetailsByBlockHeightR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_xrp__ripple_block_details_by_block_height_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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;,  are test networks. |  |
+| **height** | **String** | 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 \&quot;Genesis block\&quot;. |  |
+| **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
+
+[**GetXRPRippleBlockDetailsByBlockHeightR**](GetXRPRippleBlockDetailsByBlockHeightR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## get_xrp__ripple_transaction_details_by_transaction_id
+
+> <GetXRPRippleTransactionDetailsByTransactionIDR> get_xrp__ripple_transaction_details_by_transaction_id(network, transaction_hash, opts)
+
+Get XRP (Ripple) Transaction Details By Transaction ID
+
+Through this endpoint customers can obtain details about a XRP transaction by the transaction's unique identifier.     Since XRP is a different blockchain than Bitcoin and Ethereum, it isn't unified.
+
+### 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::XRPRippleApi.new
+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 = '36a1737481edec87bacc3101dfb752ae2c76f9171e7edebe587e330c1ea77c8d' # String | Represents the same as `transactionId` for account-based protocols like Ethereum, while it could be different in UTXO-based protocols like Bitcoin. E.g., in UTXO-based protocols `hash` is different from `transactionId` for SegWit transactions.
+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 XRP (Ripple) Transaction Details By Transaction ID
+  result = api_instance.get_xrp__ripple_transaction_details_by_transaction_id(network, transaction_hash, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_xrp__ripple_transaction_details_by_transaction_id: #{e}"
+end
+```
+
+#### Using the get_xrp__ripple_transaction_details_by_transaction_id_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GetXRPRippleTransactionDetailsByTransactionIDR>, Integer, Hash)> get_xrp__ripple_transaction_details_by_transaction_id_with_http_info(network, transaction_hash, opts)
+
+```ruby
+begin
+  # Get XRP (Ripple) Transaction Details By Transaction ID
+  data, status_code, headers = api_instance.get_xrp__ripple_transaction_details_by_transaction_id_with_http_info(network, transaction_hash, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GetXRPRippleTransactionDetailsByTransactionIDR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->get_xrp__ripple_transaction_details_by_transaction_id_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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. |  |
+| **transaction_hash** | **String** | Represents the same as &#x60;transactionId&#x60; for account-based protocols like Ethereum, while it could be different in UTXO-based protocols like Bitcoin. E.g., in UTXO-based protocols &#x60;hash&#x60; is different from &#x60;transactionId&#x60; for SegWit transactions. |  |
+| **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
+
+[**GetXRPRippleTransactionDetailsByTransactionIDR**](GetXRPRippleTransactionDetailsByTransactionIDR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## list_xrp__ripple_transactions_by_address
+
+> <ListXRPRippleTransactionsByAddressR> list_xrp__ripple_transactions_by_address(network, address, opts)
+
+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.
+
+### 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::XRPRippleApi.new
+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\",  are test networks.
+address = 'rA9bXGJcXvZKaWofrRphdJsBWzhyCfH3z' # String | Represents the public address, which is a compressed and shortened form of a public key.
+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 XRP (Ripple) Transactions by Address
+  result = api_instance.list_xrp__ripple_transactions_by_address(network, address, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->list_xrp__ripple_transactions_by_address: #{e}"
+end
+```
+
+#### Using the list_xrp__ripple_transactions_by_address_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<ListXRPRippleTransactionsByAddressR>, Integer, Hash)> list_xrp__ripple_transactions_by_address_with_http_info(network, address, opts)
+
+```ruby
+begin
+  # List XRP (Ripple) Transactions by Address
+  data, status_code, headers = api_instance.list_xrp__ripple_transactions_by_address_with_http_info(network, address, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <ListXRPRippleTransactionsByAddressR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->list_xrp__ripple_transactions_by_address_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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;,  are test networks. |  |
+| **address** | **String** | Represents the public address, which is a compressed and shortened form of a public key. |  |
+| **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
+
+[**ListXRPRippleTransactionsByAddressR**](ListXRPRippleTransactionsByAddressR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## list_xrp__ripple_transactions_by_block_hash
+
+> <ListXRPRippleTransactionsByBlockHashR> list_xrp__ripple_transactions_by_block_hash(network, block_hash, opts)
+
+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.
+
+### 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::XRPRippleApi.new
+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.
+block_hash = '14754656235f865a74eba27791fd41a47bdfe07fe811ff6d78f53db32e129e39' # 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.
+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 XRP (Ripple) Transactions By Block Hash
+  result = api_instance.list_xrp__ripple_transactions_by_block_hash(network, block_hash, opts)
+  p result
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->list_xrp__ripple_transactions_by_block_hash: #{e}"
+end
+```
+
+#### Using the list_xrp__ripple_transactions_by_block_hash_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<ListXRPRippleTransactionsByBlockHashR>, Integer, Hash)> list_xrp__ripple_transactions_by_block_hash_with_http_info(network, block_hash, opts)
+
+```ruby
+begin
+  # List XRP (Ripple) Transactions By Block Hash
+  data, status_code, headers = api_instance.list_xrp__ripple_transactions_by_block_hash_with_http_info(network, block_hash, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <ListXRPRippleTransactionsByBlockHashR>
+rescue CryptoApis::ApiError => e
+  puts "Error when calling XRPRippleApi->list_xrp__ripple_transactions_by_block_hash_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **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. |  |
+| **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. |  |
+| **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
+
+[**ListXRPRippleTransactionsByBlockHashR**](ListXRPRippleTransactionsByBlockHashR.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+