diff --git a/pages/rpc-service/chains/chains-api/xrp.mdx b/pages/rpc-service/chains/chains-api/xrp.mdx
index 9c3f11d2..a87c8766 100644
--- a/pages/rpc-service/chains/chains-api/xrp.mdx
+++ b/pages/rpc-service/chains/chains-api/xrp.mdx
@@ -5,7 +5,7 @@ import { Tabs, Tab } from "nextra-theme-docs";
> XRP API is available on [Web3 API platform](https://www.ankr.com/rpc/xrp).
-
+The XRP Ledger (XRPL) is a decentralized blockchain optimized for fast, low-cost payments and asset transfers. It uses a federated consensus algorithm in which a trusted set of validators propose and agree on transactions; once 80%+ reach consensus, a new ledger is finalized in 3–5 seconds with deterministic finality. XRPL supports native issued assets, a built-in DEX, escrows, payment channels, and multi-signing.
In order for your Web3 application to interact with XRP — either by reading blockchain data or sending transactions to the network — it must connect to an XRP node. Developers interact with the blockchain using the methods provided by the API.
@@ -17,91 +17,84 @@ The API interaction follows the [JSON-RPC](https://www.jsonrpc.org/specification
An account in the XRP Ledger represents a holder of XRP and a sender of transactions. Use these methods to work with account info.
- * [`account_channels`]() — retrieves a list of payment channels where the account is the source of the channel.
- * [`account_currencies`]() — retrieves a list of currencies an account can send or receive.
- * [`account_info`]() — retrieves basic data on the account.
- * [`account_lines`]() — retrieves info on the account's trust lines.
- * [`account_nfts`]() — retrieves a list of all NFTs for an account.
- * [`account_objects`]() — retrieves all ledger objects owned by an account.
- * [`account_offers`]() — retrieves info on the account's currency exchange offers.
- * [`account_tx`]() — retrieves a list of transactions affecting an account.
- * [`gateway_balances`]() — calculates total amounts issued by an account.
- * [`noripple_check`]() — gets recommended changes to an account's Default Ripple and No Ripple settings.
+ * [`account_channels`](/rpc-service/chains/chains-api/xrp/#account_channels) — retrieves a list of payment channels where the account is the source of the channel.
+ * [`account_currencies`](/rpc-service/chains/chains-api/xrp/#account_currencies) — retrieves a list of currencies an account can send or receive.
+ * [`account_info`](/rpc-service/chains/chains-api/xrp/#account_info) — retrieves basic data on the account.
+ * [`account_lines`](/rpc-service/chains/chains-api/xrp/#account_lines) — retrieves info on the account's trust lines.
+ * [`account_nfts`](/rpc-service/chains/chains-api/xrp/#account_nfts) — retrieves a list of all NFTs for an account.
+ * [`account_objects`](/rpc-service/chains/chains-api/xrp/#account_objects) — retrieves all ledger objects owned by an account.
+ * [`account_offers`](/rpc-service/chains/chains-api/xrp/#account_offers) — retrieves info on the account's currency exchange offers.
+ * [`account_tx`](/rpc-service/chains/chains-api/xrp/#account_tx) — retrieves a list of transactions affecting an account.
+ * [`gateway_balances`](/rpc-service/chains/chains-api/xrp/#gateway_balances) — calculates total amounts issued by an account.
+ * [`noripple_check`](/rpc-service/chains/chains-api/xrp/#noripple_check) — gets recommended changes to an account's Default Ripple and No Ripple settings.
**Ledger Methods**:
A ledger version contains a header, a transaction tree, and a state tree, which contain account settings, trustlines, balances, transactions, and other data. Use these methods to retrieve ledger info.
- * [`ledger`]() — retrieves info on the ledger.
- * [`ledger_closed`]() — retrieves the latest closed ledger version.
- * [`ledger_current`]() — retrieves the current working ledger version.
- * [`ledger_data`]() — retrieves the raw contents of a ledger version.
- * [`ledger_entry`]() — retrieves a single item from a ledger version.
+ * [`ledger`](/rpc-service/chains/chains-api/xrp/#ledger) — retrieves info on the ledger.
+ * [`ledger_closed`](/rpc-service/chains/chains-api/xrp/#ledger_closed) — retrieves the latest closed ledger version.
+ * [`ledger_current`](/rpc-service/chains/chains-api/xrp/#ledger_current) — retrieves the current working ledger version.
+ * [`ledger_data`](/rpc-service/chains/chains-api/xrp/#ledger_data) — retrieves the raw contents of a ledger version.
+ * [`ledger_entry`](/rpc-service/chains/chains-api/xrp/#ledger_entry) — retrieves a single item from a ledger version.
**Transaction Methods**:
Transactions are the only thing that can modify the shared state of the XRP Ledger. All business on the XRP Ledger takes the form of transactions. Use these methods to work with transactions.
- * [`simulate`]() — executes a dry run of any transaction type to preview results and metadata.
- * [`submit`]() — sends a transaction to the network.
- * [`submit_multisigned`]() — sends a multi-signed transaction to the network.
- * [`transaction_entry`]() — retrieves info on the transaction from a particular ledger version.
- * [`tx`]() — retrieves info on the transaction from all the ledgers at hand.
- * [`tx_history`]() — retrieves info on all recent transactions.
+ * [`simulate`](/rpc-service/chains/chains-api/xrp/#simulate) — executes a dry run of any transaction type to preview results and metadata.
+ * [`submit`](/rpc-service/chains/chains-api/xrp/#submit) — sends a transaction to the network.
+ * [`submit_multisigned`](/rpc-service/chains/chains-api/xrp/#submit_multisigned) — sends a multi-signed transaction to the network.
+ * [`transaction_entry`](/rpc-service/chains/chains-api/xrp/#transaction_entry) — retrieves info on the transaction from a particular ledger version.
+ * [`tx`](/rpc-service/chains/chains-api/xrp/#tx) — retrieves info on the transaction from all the ledgers at hand.
+ * [`tx_history`](/rpc-service/chains/chains-api/xrp/#tx_history) — retrieves info on all recent transactions.
**Path and Order Book Methods**:
Paths define a way for payments to flow through intermediary steps on their way from sender to receiver. Paths enable cross-currency payments by connecting sender and receiver through order books. Use these methods to work with paths and other books.
- * [`amm_info`]() — retrieves info on the Automated Market Maker (AMM) instance.
- * [`book_changes`]() — retrieves information on order book changes.
- * [`book_offers`]() — retrieves info on the currency exchange offers.
- * [`deposit_authorized`]() — checks whether an account is authorized to send money directly to another account.
- * [`get_aggregate_price`]() — calculates the aggregate price of specified Oracle instances.
- * [`nft_buy_offers`]() — retrieves a list of all buy offers for the NFT specified.
- * [`nft_sell_offers`]() — retrieves a list of all sell offers for the NFT specified.
- * [`path_find`]() — finds a path for a payment between two accounts and gets you updated.
- * [`ripple_path_find`]() — finds a path for payment between two accounts, once.
+ * [`amm_info`](/rpc-service/chains/chains-api/xrp/#amm_info) — retrieves info on the Automated Market Maker (AMM) instance.
+ * [`book_changes`](/rpc-service/chains/chains-api/xrp/#book_changes) — retrieves information on order book changes.
+ * [`book_offers`](/rpc-service/chains/chains-api/xrp/#book_offers) — retrieves info on the currency exchange offers.
+ * [`deposit_authorized`](/rpc-service/chains/chains-api/xrp/#deposit_authorized) — checks whether an account is authorized to send money directly to another account.
+ * [`get_aggregate_price`](/rpc-service/chains/chains-api/xrp/#get_aggregate_price) — calculates the aggregate price of specified Oracle instances.
+ * [`nft_buy_offers`](/rpc-service/chains/chains-api/xrp/#nft_buy_offers) — retrieves a list of all buy offers for the NFT specified.
+ * [`nft_sell_offers`](/rpc-service/chains/chains-api/xrp/#nft_sell_offers) — retrieves a list of all sell offers for the NFT specified.
+ * [`ripple_path_find`](/rpc-service/chains/chains-api/xrp/#ripple_path_find) — finds a path for payment between two accounts, once.
**Payment Channel Methods**:
Payment channels are a tool for facilitating repeated, unidirectional payments, or temporary credit between two parties. Use these methods to work with payment channels.
- * [`channel_authorize`]() — signs a claim for money from a payment channel.
- * [`channel_verify`]() — checks a payment channel claim's signature.
+ * [`channel_verify`](/rpc-service/chains/chains-api/xrp/#channel_verify) — checks a payment channel claim's signature.
**Server Info Methods**:
Use these methods to retrieve information about the current state of the rippled server.
- * [`fee`]() — retrieves information on the transaction cost.
- * [`feature`]() — retrieves information on the protocol amendments.
- * [`manifest`]() — retrieves public information on a known validator.
- * [`server_definitions`]() — retrieves an SDK-compatible `definitions.json`, generated from the `rippled` instance currently running.
- * [`server_info (rippled)`]() — retrieves status of the server in human-readable format.
- * [`server_state`]() — retrieves status of the server in machine-readable format.
- * [`version`]() — retrieves API version information.
+ * [`fee`](/rpc-service/chains/chains-api/xrp/#fee) — retrieves information on the transaction cost.
+ * [`feature`](/rpc-service/chains/chains-api/xrp/#feature) — retrieves information on the protocol amendments.
+ * [`manifest`](/rpc-service/chains/chains-api/xrp/#manifest) — retrieves public information on a known validator.
+ * [`server_definitions`](/rpc-service/chains/chains-api/xrp/#server_definitions) — retrieves an SDK-compatible `definitions.json`, generated from the `rippled` instance currently running.
+ * [`server_info (rippled)`](/rpc-service/chains/chains-api/xrp/#server_info-rippled) — retrieves status of the server in human-readable format.
+ * [`server_state`](/rpc-service/chains/chains-api/xrp/#server_state) — retrieves status of the server in machine-readable format.
+ * [`version`](/rpc-service/chains/chains-api/xrp/#version) — retrieves API version information.
**Clio Methods**:
These API methods are provided only by the Clio server, not `rippled`.
- * [`server_info`]() — retrieves status of the Clio server in human-readable format.
- * [`ledger`]() — retrieves info on the ledger version.
- * [`mpt_holders`]() — retrieves the holders of a given MPT issuance for a given ledger.
- * [`ledger_index`]() — retrieves a ledger by its close time.
- * [`nft_history`]() — retrieves the history of ownership and transfers for the specified NFT using Clio server's `nft_history` API.
- * [`nft_info`]() — retrieves information on the specified NFT using Clio server's `nft_info` API.
- * [`nfts_by_issuer`]() — retrieves the history of ownership and transfers for the specified NFT using Clio server's `nft_history` API.
- * [`version`]() — retrieves API version information.
+ * [`server_info`](/rpc-service/chains/chains-api/xrp/#server_info) — retrieves status of the Clio server in human-readable format.
+ * [`ledger`](/rpc-service/chains/chains-api/xrp/#ledger-1) — retrieves info on the ledger version.
+ * [`mpt_holders`](/rpc-service/chains/chains-api/xrp/#mpt_holders) — retrieves the holders of a given MPT issuance for a given ledger.
+ * [`version`](/rpc-service/chains/chains-api/xrp/#version-1) — retrieves API version information.
**Utility Methods**:
Use these methods to perform convenient tasks, such as ping and random number generation.
- * [`json`]() — passes JSON through the commandline.
- * [`ping`]() — confirms connectivity with the server.
- * [`random`]() — generates a random number.
+ * [`ping`](/rpc-service/chains/chains-api/xrp/#ping) — confirms connectivity with the server.
+ * [`random`](/rpc-service/chains/chains-api/xrp/#random) — generates a random number.
---
@@ -122,39 +115,39 @@ The `account_channels` method returns information about an account's Payment Cha
* `method` (string; required): a method used for the request.
* `params` (array; required):
- * `account` (string — address???; required): look up channels where this account is the channel’s owner/source.
- * `destination_account` (string — address???; optional): a second account; if provided, filters results to payment channels whose destination is this account.
- * `ledger_hash` (string; optional): the unique hash of the ledger version to use (see Specifying Ledgers???).
- * `ledger_index` (number or string; optional): the ledger index of the ledger to use, or a shortcut string to choose a ledger automatically (see Specifying Ledgers???).
+ * `account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses); required): look up channels where this account is the channel’s owner/source.
+ * `destination_account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses); optional): a second account; if provided, filters results to payment channels whose destination is this account.
+ * `ledger_hash` (string; optional): the unique hash of the ledger version to use (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `ledger_index` (number or string; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger to use, or a shortcut string to choose a ledger automatically (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
* `limit` (number; optional): limits the number of transactions to retrieve. Must be between 10 and 400; values outside this range are adjusted to the nearest valid value. Default: 200.
- * `marker` (string — marker???; optional): value from a previous paginated response; resumes retrieving data where that response left off.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): value from a previous paginated response; resumes retrieving data where that response left off.
### Returns
-The response follows the standard format???, with a successful result containing the following fields:
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following fields:
* `account` (string): the address of the source/owner of the payment channels. Corresponds to the `account` field of the request.
* `channels` (array of objects): list of payment channels owned by this `account`. Each object contains the following fields:
- * `account` (string): the owner of the channel, as an address???.
- * `channel_id` (string): a unique ID for this channel, represented as a 64-character hexadecimal string. This is also the ???ID of the channel object??? in the ledger’s state data.
+ * `account` (string): the owner of the channel, as an [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses).
+ * `channel_id` (string): a unique ID for this channel, represented as a 64-character hexadecimal string. This is also the [ID of the channel object](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types/paychannel#paychannel-id-format) in the ledger’s state data.
* `destination_account` (string): the destination account of the channel, as an address. Only this account can receive the `amount` in the channel while it is open.
* `settle_delay` (unsigned integer): the number of seconds the payment channel must remain open after the owner requests to close it.
- * `public_key` (string; optional): the public key for the payment channel in the XRP Ledger’s base58??? format. Signed claims against this channel must be redeemed with the matching key pair.
+ * `public_key` (string; optional): the public key for the payment channel in the XRP Ledger’s [base58](https://xrpl.org/docs/references/protocol/data-types/base58-encodings) format. Signed claims against this channel must be redeemed with the matching key pair.
* `public_key_hex` (string; optional): the public key for the payment channel in hexadecimal format, if one was specified at channel creation. Signed claims against this channel must be redeemed with the matching key pair.
- * `expiration` (unsigned integer; optional): time in ???seconds since the Ripple Epoch??? when this channel is set to expire. This expiration date is mutable. If this value is before the close time of the most recent validated ledger, the channel is expired.
- * `cancel_after` (unsigned integer; optional): time in ???seconds since the Ripple Epoch??? representing this channel’s immutable expiration, if one was specified at creation. If this is before the close time of the most recent validated ledger, the channel is expired.
- * `source_tag` (unsigned integer; optional): a 32-bit unsigned integer used as a ???source tag??? for payments through this payment channel, if specified at creation. This indicates the channel’s originator or purpose. Conventionally, if you bounce payments from this channel, you should include this value in the `DestinationTag` of the return payment.
- * `destination_tag` (unsigned integer; optional): a 32-bit unsigned integer used as a ???destination tag??? for payments through this payment channel, if specified at creation. This indicates the payment channel’s beneficiary or purpose at the destination account.
- * `ledger_hash` (string; optional): the identifying hash??? of the ledger version used to generate this response.
- * `ledger_index` (number): the ledger index??? of the ledger version used to generate this response.
+ * `expiration` (unsigned integer; optional): time in [seconds since the Ripple Epoch](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-time) when this channel is set to expire. This expiration date is mutable. If this value is before the close time of the most recent validated ledger, the channel is expired.
+ * `cancel_after` (unsigned integer; optional): time in [seconds since the Ripple Epoch](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-time) representing this channel’s immutable expiration, if one was specified at creation. If this is before the close time of the most recent validated ledger, the channel is expired.
+ * `source_tag` (unsigned integer; optional): a 32-bit unsigned integer used as a [source tag](https://xrpl.org/docs/concepts/transactions/source-and-destination-tags) for payments through this payment channel, if specified at creation. This indicates the channel’s originator or purpose. Conventionally, if you bounce payments from this channel, you should include this value in the `DestinationTag` of the return payment.
+ * `destination_tag` (unsigned integer; optional): a 32-bit unsigned integer used as a [destination tag](https://xrpl.org/docs/concepts/transactions/source-and-destination-tags) for payments through this payment channel, if specified at creation. This indicates the payment channel’s beneficiary or purpose at the destination account.
+ * `ledger_hash` (string; optional): the identifying [hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes) of the ledger version used to generate this response.
+ * `ledger_index` (number): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger version used to generate this response.
* `validated` (boolean; optional): if `true`, the information in this response comes from a validated ledger version; otherwise, the information is subject to change.
* `limit` (number; optional): the limit defining how many channel objects were actually returned by this request.
- * `marker` (string — marker???; optional): server-defined value for pagination; pass this value to the next call to resume fetching results from where this call left off. Omitted when there are no more pages of data.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): server-defined value for pagination; pass this value to the next call to resume fetching results from where this call left off. Omitted when there are no more pages of data.
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -212,24 +205,24 @@ The `account_currencies` command retrieves a list of currencies that an account
* `method` (string; required): a method used for the request.
* `params` (array; required):
- * `account` (string — address???; required): look up currencies this account can send or receive.
- * `ledger_hash` (string; optional): the unique hash of the ledger version to use (see ???Specifying Ledgers???).
- * `ledger_index` (number or string; optional): the ledger index of the ledger to use, or a shortcut string to choose a ledger automatically (see ???Specifying Ledgers???).
+ * `account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses); required): look up currencies this account can send or receive.
+ * `ledger_hash` (string; optional): the unique hash of the ledger version to use (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `ledger_index` (number or string; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger to use, or a shortcut string to choose a ledger automatically (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
### Returns
-The response follows the ???standard format???, with a successful result containing the following fields:
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following fields:
- * `ledger_hash` (string — hash???; optional): the identifying hash of the ledger version used to retrieve this data, represented as a hexadecimal string.
- * `ledger_index` (integer): the ???ledger index??? of the ledger version used to retrieve this data.
- * `receive_currencies` (array of strings): list of ???currency codes??? that this account can receive.
- * `send_currencies` (array of strings): list of currency codes that this account can send.
+ * `ledger_hash` (string — [hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes); optional): the identifying hash of the ledger version used to retrieve this data, represented as a hexadecimal string.
+ * `ledger_index` (integer): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger version used to retrieve this data.
+ * `receive_currencies` (array of strings): list of [currency codes](https://xrpl.org/docs/references/protocol/data-types/currency-formats#currency-codes) that this account can receive.
+ * `send_currencies` (array of strings): list of [currency codes](https://xrpl.org/docs/references/protocol/data-types/currency-formats#currency-codes) that this account can send.
* `validated` (boolean): if `true`, the data in this response comes from a validated ledger.
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -297,49 +290,49 @@ The `account_info` command retrieves information about an account, its activity,
* `method` (string; required): a method used for the request.
* `params` (array; required):
- * `account` (string — address???; required): the account to look up.
- * `ledger_hash` (string; optional): the unique hash of the ledger version to use (see ???Specifying Ledgers???).
- * `ledger_index` (number or string; optional): the ledger index of the ledger to use, or a shortcut string to choose a ledger automatically (see ???Specifying Ledgers???).
- * `queue` (boolean; optional): if `true`, returns stats about ???queued transactions??? sent by this account. Can only be used when querying data from the current open ledger.
- * `signer_lists` (boolean; optional): if `true`, returns any `SignerList` objects associated with this account.
+ * `account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses); required): the account to look up.
+ * `ledger_hash` (string; optional): the unique hash of the ledger version to use (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `ledger_index` (number or string; optional): the ledger index of the ledger to use, or a shortcut string to choose a ledger automatically (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `queue` (boolean; optional): if `true`, returns stats about [queued transactions](https://xrpl.org/docs/concepts/transactions/transaction-queue) sent by this account. Can only be used when querying data from the current open ledger.
+ * `signer_lists` (boolean; optional): if `true`, returns any [`SignerList` objects](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types/signerlist) associated with this account.
### Returns
-The response follows the ???standard format???, with the result containing the requested account, its data, and a ledger to which it applies, as the following fields:
-
- * `account_data` (object): the `AccountRoot` ledger object containing this account’s information as stored in the ledger.
- * `account_flags` (object): the account’s flag statuses, derived from the Flags field of the account. Contains the following nested fields:
- * `defaultRipple` (boolean): if `true`, the account allows ???rippling??? on its trust lines by default.
- * `depositAuth` (boolean): if `true`, the account uses ???Deposit Authorization??? and does not accept payments from unknown parties.
- * `disableMasterKey` (boolean): if `true`, the account’s ???master key pair??? is disabled.
- * `disallowIncomingCheck` (boolean): if `true`, the account does not allow others to send ???Checks??? to it.
- * `disallowIncomingNFTokenOffer` (boolean): if `true`, the account does not allow others to make ???NFT buy or sell offers??? to it.
- * `disallowIncomingPayChan` (boolean): if `true`, the account does not allow others to create ???Payment Channels??? to it.
- * `disallowIncomingTrustline` (boolean): if `true`, the account does not allow others to create ???trust lines??? to it.
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with the result containing the requested account, its data, and a ledger to which it applies, as the following fields:
+
+ * `account_data` (object): the [AccountRoot ledger object](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types/accountroot) containing this account’s information as stored in the ledger.
+ * `account_flags` (object): the account’s flag statuses, derived from the `Flags` field of the account. Contains the following nested fields:
+ * `defaultRipple` (boolean): if `true`, the account allows [rippling](https://xrpl.org/docs/concepts/tokens/fungible-tokens/rippling) on its trust lines by default.
+ * `depositAuth` (boolean): if `true`, the account uses [Deposit Authorization](https://xrpl.org/docs/concepts/accounts/depositauth) and does not accept payments from unknown parties.
+ * `disableMasterKey` (boolean): if `true`, the account’s [master key pair](https://xrpl.org/docs/concepts/accounts/cryptographic-keys) is disabled.
+ * `disallowIncomingCheck` (boolean): if `true`, the account does not allow others to send [Checks](https://xrpl.org/docs/concepts/payment-types/checks) to it.
+ * `disallowIncomingNFTokenOffer` (boolean): if `true`, the account does not allow others to make [NFT buy or sell offers](https://xrpl.org/docs/concepts/tokens/nfts/trading) to it.
+ * `disallowIncomingPayChan` (boolean): if `true`, the account does not allow others to create [Payment Channels](https://xrpl.org/docs/concepts/payment-types/payment-channels) to it.
+ * `disallowIncomingTrustline` (boolean): if `true`, the account does not allow others to create [trust lines](https://xrpl.org/docs/concepts/tokens/fungible-tokens) to it.
* `disallowIncomingXRP` (boolean): if `true`, the account prefers not to receive XRP from others. This setting is advisory and not enforced at the protocol level.
* `globalFreeze` (boolean): if `true`, all tokens issued by the account are currently frozen.
- * `noFreeze` (boolean): if `true`, the account has permanently renounced the ability to freeze individual trust lines or enforce a global freeze. See ???No Freeze??? for details.
- * `passwordSpent` (boolean): if `false`, the account can send a special ???key-reset transaction?? with zero transaction cost. The protocol automatically toggles this flag; it is not user-controlled.
- * `requireAuthorization` (boolean): if `true`, the account uses ???Authorized Trust Lines??? to restrict who can hold its issued tokens.
- * `requireDestinationTag` (boolean): if `true`, the account ???requires a destination tag??? on all incoming payments.
+ * `noFreeze` (boolean): if `true`, the account has permanently renounced the ability to freeze individual trust lines or enforce a global freeze. See [No Freeze](https://xrpl.org/docs/concepts/tokens/fungible-tokens/freezes#no-freeze) for details.
+ * `passwordSpent` (boolean): if `false`, the account can send a special [key-reset transaction](https://xrpl.org/docs/concepts/transactions/transaction-cost#key-reset-transaction) with zero transaction cost. The protocol automatically toggles this flag; it is not user-controlled.
+ * `requireAuthorization` (boolean): if `true`, the account uses [Authorized Trust Lines](https://xrpl.org/docs/concepts/tokens/fungible-tokens/authorized-trust-lines) to restrict who can hold its issued tokens.
+ * `requireDestinationTag` (boolean): if `true`, the account [requires a destination tag](https://xrpl.org/docs/tutorials/how-tos/manage-account-settings/require-destination-tags) on all incoming payments.
* `signer_lists` (array; optional):
* API v1: omitted unless the request specified signer_lists and at least one SignerList is associated with the account. Contains an array of SignerList ledger objects for multi-signing. Since an account can own at most one SignerList, this array contains exactly one member if present. The field is nested under account_data.
* API v2: identical to API v1, but the field is returned at the root level of the response. (Clio implements API v2 behavior in all cases.)
* `ledger_current_index` (integer; optional): the ledger index of the current in-progress ledger used when retrieving this information. Omitted if ledger_index is provided instead.
* `ledger_index` (integer; optional): the ledger index of the ledger version used to retrieve this information. This data does not include any changes from newer ledger versions.
- * `queue_data` (object; optional): information about ???queued transactions??? sent by this account. Returned only if queue was set to `true` and the current open ledger was queried. Describes the local rippled server’s queue state, which may differ across the network. Some fields may be omitted because certain values are computed lazily by the queuing mechanism. Contains the following nested fields:
+ * `queue_data` (object; optional): information about [queued transactions](https://xrpl.org/docs/concepts/transactions/transaction-cost#queued-transactions) sent by this account. Returned only if queue was set to `true` and the current open ledger was queried. Describes the local rippled server’s queue state, which may differ across the network. Some fields may be omitted because certain values are computed lazily by the queuing mechanism. Contains the following nested fields:
* `txn_count` (integer): number of queued transactions from this address.
- * `auth_change_queued` (boolean; optional): whether a transaction in the queue changes this address’s ???ways of authorizing transactions???. If `true`, no further transactions can be queued until that transaction executes or drops from the queue.
- * `lowest_sequence` (integer; optional): the lowest ???sequence number??? among transactions queued by this address.
- * `highest_sequence` (integer; optional): the highest ???sequence number??? among transactions queued by this address.
- * `max_spend_drops_total` (string; optional): the total number of ???drops of XRP??? that could be debited from this account if every queued transaction consumes the maximum possible amount.
+ * `auth_change_queued` (boolean; optional): whether a transaction in the queue changes this address’s [ways of authorizing transactions](https://xrpl.org/docs/concepts/transactions#authorizing-transactions). If `true`, no further transactions can be queued until that transaction executes or drops from the queue.
+ * `lowest_sequence` (integer; optional): the lowest [sequence number](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#account-sequence) among transactions queued by this address.
+ * `highest_sequence` (integer; optional): the highest [sequence number](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#account-sequence) among transactions queued by this address.
+ * `max_spend_drops_total` (string; optional): the total number of [drops of XRP](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-currency-amounts) that could be debited from this account if every queued transaction consumes the maximum possible amount.
* `transactions` (array; optional): information about each queued transaction from this account.
- * `validated` (boolean): true if this data originates from a validated ledger version; if omitted or false, the data is not final.
+ * `validated` (boolean): `true` if this data originates from a validated ledger version; if omitted or `false`, the data is not final.
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -415,47 +408,46 @@ The `account_lines` method returns information about an account's trust lines, w
* `method` (string; required): a method used for the request.
* `params` (array; required):
- * `account` (string — address???; required): look up trust lines connected to this account, from this account’s perspective.
+ * `account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses); required): look up trust lines connected to this account, from this account’s perspective.
* `ignore_default` (boolean; optional): if `true`, omits trust lines where this account’s side is in the default state. Default: `false`.
- * `ledger_hash` (string — ???hash; optional): the unique hash of the ledger version to use (see ???Specifying Ledgers???).
- * `ledger_index` (number or string; optional): the ???ledger index??? of the ledger version to use, or a shortcut string to choose a ledger automatically (see ???Specifying Ledgers???).
+ * `ledger_hash` (string — [hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes); optional): the unique hash of the ledger version to use (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `ledger_index` (number or string; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger version to use, or a shortcut string to choose a ledger automatically (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
* `limit` (number; optional): limits the number of trust lines to retrieve. Must be between 10 and 400. Values outside this range are adjusted to the nearest valid option. Default: `200`.
- * `marker` (string — marker???; optional): value from a previous paginated response; resumes retrieving data where that response left off.
- * `peer` (string — address???; optional): a second account; if provided, filters results to trust lines connecting the two accounts.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): value from a previous paginated response; resumes retrieving data where that response left off.
+ * `peer` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses); optional): a second account; if provided, filters results to trust lines connecting the two accounts.
### Returns
-The response follows the ???standard format???, with a successful result containing the address of the account and an array of trust line objects. Specifically, the result object contains the following fields:
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the address of the account and an array of trust line objects. Specifically, the result object contains the following fields:
- * `account` (string): the unique ???address??? of the account this request corresponds to — the perspective account for the listed trust lines.
+ * `account` (string): the unique [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses) of the account this request corresponds to — the perspective account for the listed trust lines.
* `lines` (array of objects): array of trust line objects associated with the specified account. If the number of trust lines is large, only returns up to the limit at a time. Each object contains the following fields:
-
- * `account` (string — ???address???): the counterparty to this trust line.
- * `balance` (string — number???): the current balance held on this line.
+ * `account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses)): the counterparty to this trust line.
+ * `balance` (string — [number](https://xrpl.org/docs/references/protocol/data-types/currency-formats#string-numbers)): the current balance held on this line.
* A positive balance indicates that the perspective account holds value.
* A negative balance indicates that the perspective account owes value.
- * `currency` (string — ???currency code???): the currency code of the token that this trust line represents.
- * `limit` (string — ???number???): the maximum amount of the given currency that this account is willing to owe the peer account.
- * `limit_peer` (string — number???): the maximum amount of the given currency that the counterparty is willing to owe the perspective account.
+ * `currency` (string — [currency code]()): the currency code of the token that this trust line represents.
+ * `limit` (string — [number](https://xrpl.org/docs/references/protocol/data-types/currency-formats#string-numbers)): the maximum amount of the given currency that this account is willing to owe the peer account.
+ * `limit_peer` (string — [number](https://xrpl.org/docs/references/protocol/data-types/currency-formats#string-numbers)): the maximum amount of the given currency that the counterparty is willing to owe the perspective account.
* `quality_in` (number): rate at which the account values incoming balances on this trust line, as a ratio of this value per 1 billion units. For example, a value of 500 million represents a `0.5:1` ratio. As a special case, 0 is treated as a `1:1` ratio.
* `quality_out` (number): rate at which the account values outgoing balances on this trust line, as a ratio of this value per 1 billion units. For example, a value of 500 million represents a `0.5:1` ratio. As a special case, 0 is treated as a `1:1` ratio.
- * `no_ripple` (boolean; optional): if `true`, this account has enabled the ???No Ripple flag??? for this trust line. If `false`, the flag is disabled, but this is not considered default??? when Default Ripple is also disabled. If omitted, No Ripple is disabled and Default Ripple is enabled.
- * `no_ripple_peer` (boolean; optional): if `true`, the peer account has enabled the ???No Ripple flag??? for this trust line. If `false`, the flag is disabled, but this is not considered ???default??? when Default Ripple is also disabled. If omitted, No Ripple is disabled and Default Ripple is enabled.
- * `authorized` (boolean; optional): if true, the perspective account ???has authorized this trust line???. Default: `false`.
- * `peer_authorized` (boolean; optional): if `true`, the counterparty ???has authorized this trust line???. Default: `false`.
- * `freeze` (boolean; optional): if `true`, the perspective account ???has frozen this trust line???. Default: `false`.
- * `freeze_peer` (boolean; optional): if `true`, the counterparty ???has frozen this trust line???. Default: `false`.
-
- * `ledger_current_index` (integer; optional): the ???ledger index??? used when retrieving this data. Present only when using an open ledger version.
- * `ledger_index` (integer; optional): the ???ledger index??? used when retrieving this data. Present only when using a closed ledger version.
- * `ledger_hash` (string — ???hash; optional): the identifying hash of the ledger version used when retrieving this data. This field is only provided when using a closed ledger version.
- * `marker` (string — marker???; optional): server-defined value indicating pagination; pass this to the next call to resume retrieving results from where this response ended. Omitted when there are no additional pages.
+ * `no_ripple` (boolean; optional): if `true`, this account has enabled the [No Ripple flag](https://xrpl.org/docs/concepts/tokens/fungible-tokens/rippling) for this trust line. If `false`, the flag is disabled, but this is not considered [default](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate#contributing-to-the-owner-reserve) when Default Ripple is also disabled. If omitted, No Ripple is disabled and Default Ripple is enabled.
+ * `no_ripple_peer` (boolean; optional): if `true`, the peer account has enabled the [No Ripple flag](https://xrpl.org/docs/concepts/tokens/fungible-tokens/rippling) for this trust line. If `false`, the flag is disabled, but this is not considered [default](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate#contributing-to-the-owner-reserve) when Default Ripple is also disabled. If omitted, No Ripple is disabled and Default Ripple is enabled.
+ * `authorized` (boolean; optional): if true, the perspective account [has authorized this trust line](https://xrpl.org/docs/concepts/tokens/fungible-tokens/authorized-trust-lines). Default: `false`.
+ * `peer_authorized` (boolean; optional): if `true`, the counterparty [has authorized this trust line](https://xrpl.org/docs/concepts/tokens/fungible-tokens/authorized-trust-lines). Default: `false`.
+ * `freeze` (boolean; optional): if `true`, the perspective account [has frozen this trust line](https://xrpl.org/docs/concepts/tokens/fungible-tokens/authorized-trust-lines). Default: `false`.
+ * `freeze_peer` (boolean; optional): if `true`, the counterparty [has frozen this trust line](https://xrpl.org/docs/concepts/tokens/fungible-tokens/authorized-trust-lines). Default: `false`.
+
+ * `ledger_current_index` (integer; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) used when retrieving this data. Present only when using an open ledger version.
+ * `ledger_index` (integer; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) used when retrieving this data. Present only when using a closed ledger version.
+ * `ledger_hash` (string — [hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes); optional): the identifying hash of the ledger version used when retrieving this data. This field is only provided when using a closed ledger version.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): server-defined value indicating pagination; pass this to the next call to resume retrieving results from where this response ended. Omitted when there are no additional pages.
* `limit` (number; optional): the maximum number of trust lines retrieved. The server may return fewer than the specified limit even if more results are available. Default: `200`.
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -518,36 +510,36 @@ The `account_nfts` method returns a list of `NFToken` objects for the specified
* `method` (string; required): a method used for the request.
* `params` (array; required):
- * `account` (string; required): the unique identifier of an account (typically, address???). Returns a list of NFTs owned by this account.
- * `ledger_hash` (string; optional): the unique hash of the ledger version to use (see ???Specifying Ledgers???).
- * `ledger_index` (string or number; optional): the ???ledger index??? of the ledger version to use, or a shortcut string to choose a ledger automatically (see ???Specifying Ledgers???).
- * `limit` (integer; optional): limits the number of ???token pages??? to retrieve. Each page can contain up to 32 NFTs.
+ * `account` (string; required): the unique identifier of an account (typically, [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses)). Returns a list of NFTs owned by this account.
+ * `ledger_hash` (string; optional): the unique hash of the ledger version to use (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `ledger_index` (string or number; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger version to use, or a shortcut string to choose a ledger automatically (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `limit` (integer; optional): limits the number of [token pages](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage) to retrieve. Each page can contain up to 32 NFTs.
* Must be between `20` and `400`; values outside this range are adjusted to the nearest valid option.
* Default: `100`.
- * `marker` (string — marker; optional): value from a previous paginated response; resumes retrieving data where that response left off.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): value from a previous paginated response; resumes retrieving data where that response left off.
### Returns
-The response follows the ???standard format???, with a successful result containing the following fields:
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following fields:
* `account` (string): the account that owns the list of NFTs.
* `account_nfts` (array of objects): list of NFTs owned by the account. Each object represents one NFToken and includes the following fields:
- * `Flags` (number): a bitmap of boolean flags enabled for this NFToken. See ???NFToken Flags??? for possible values.
- * `Issuer` (string — ???address???): the account that issued this NFToken.
+ * `Flags` (number): a bitmap of boolean flags enabled for this NFToken. See [NFToken Flags](https://xrpl.org/docs/references/protocol/data-types/nftoken#nftoken-flags) for possible values.
+ * `Issuer` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses)): the account that issued this NFToken.
* `NFTokenID` (string): the unique identifier of this NFToken, represented as a hexadecimal string.
- * `NFTokenTaxon` (number): the unscrambled version of this token’s ???taxon???. Tokens sharing the same taxon may represent multiple instances of a limited series.
+ * `NFTokenTaxon` (number): the unscrambled version of this token’s [taxon](https://xrpl.org/docs/references/protocol/data-types/nftoken#nftokentaxon). Tokens sharing the same taxon may represent multiple instances of a limited series.
* `URI` (string): the URI data associated with this NFToken, represented in hexadecimal format.
* `nft_serial` (number): the token sequence number of this NFToken, unique per issuer.
* `ledger_hash` (string; optional): the identifying hash of the ledger version used to generate this response.
* `ledger_index` (number; optional): the ledger index of the ledger version used to generate this response.
* `ledger_current_index` (number; optional): the ledger index of the current in-progress ledger version used to generate this response.
* `validated` (boolean): if true, the information in this response comes from a validated ledger version; otherwise, the information is subject to change.
- * `marker` (string — marker; optional): server-defined value indicating pagination. Pass this to the next call to resume fetching results from where this response ended. Omitted when there are no additional pages.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): server-defined value indicating pagination. Pass this to the next call to resume fetching results from where this response ended. Omitted when there are no additional pages.
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -582,9 +574,9 @@ curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94a
> Retrieves all ledger objects owned by an account.
-The `account_objects` command returns all ledger entries owned by an account, in their raw ???ledger format???.
+The `account_objects` command returns all ledger entries owned by an account, in their raw [ledger format](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types).
-There are other API methods that are specialized for getting certain types of ledger entry, such as the ???account_lines??? method for trust lines, or ???account_offers??? method for offers. These methods provide a processed view of the data that is more suitable for typical use cases. Use `account_objects` if you want to get ledger entries of types that don't have a specialized method, or if you want to get the entries in their canonical format.
+There are other API methods that are specialized for getting certain types of ledger entry, such as the `account_lines` method for trust lines, or `account_offers` method for offers. These methods provide a processed view of the data that is more suitable for typical use cases. Use `account_objects` if you want to get ledger entries of types that don't have a specialized method, or if you want to get the entries in their canonical format.
### Parameters
@@ -593,28 +585,28 @@ There are other API methods that are specialized for getting certain types of le
* `method` (string; required): a method used for the request.
* `params` (array; required):
- * `account` (string — ???address???; required): retrieves ledger entries associated with this account.
+ * `account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses); required): retrieves ledger entries associated with this account.
* `deletion_blockers_only` (boolean; optional): if `true`, returns only ledger entries that would prevent this account from being deleted. Default: `false`.
- * `ledger_hash` (string — ???hash???; optional): the unique hash of the ledger version to use (see ???Specifying Ledgers???).
- * `ledger_index` (number or string; optional): the ???ledger index??? of the ledger version to use, or a shortcut string to choose a ledger automatically (see ???Specifying Ledgers???).
+ * `ledger_hash` (string — [hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes); optional): the unique hash of the ledger version to use (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `ledger_index` (number or string; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger version to use, or a shortcut string to choose a ledger automatically (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
* `limit` (number; optional): the maximum number of ledger entries to include in the results. Must be between `10` and `400` for non-admin connections. Default: `200`.
- * `marker` (string — marker; optional): value from a previous paginated response; resumes retrieving data where that response left off.
- * `type` (string; optional): filters results by a specific type of ledger entry. Accepts canonical or ???short names?? of ???ledger entry types??? (case-insensitive). Ledger entry types that cannot appear in an owner directory are not allowed. If omitted, all types are returned.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): value from a previous paginated response; resumes retrieving data where that response left off.
+ * `type` (string; optional): filters results by a specific type of ledger entry. Accepts canonical or [short names](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/ledger-entry-short-names) of [ledger entry types](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types) (case-insensitive). Ledger entry types that cannot appear in an owner directory are not allowed. If omitted, all types are returned.
### Returns
-The response follows the ???standard format???, with a successful result containing the following fields:
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following fields:
- * `account` (string — ???address???): the account this request corresponds to.
+ * `account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses)): the account this request corresponds to.
* `account_objects` (array of objects): array of ledger entries found in this account’s owner directory. Includes both:
* Entries owned directly by this account, and
* Entries linked to this account but owned by others (for example, escrows where this account is the destination).
- * Each member is a ledger entry in its raw ???ledger format???. The number of entries may be fewer than the value specified in `limit`.
+ * Each member is a ledger entry in its raw [ledger format](https://xrpl.org/docs/references/protocol/ledger-data/ledger-entry-types). The number of entries may be fewer than the value specified in `limit`.
* `ledger_hash` (string; optional): the identifying hash of the ledger used to generate this response.
- * `ledger_index` (number; optional): the ???ledger index??? of the ledger version used to generate this response.
- * `ledger_current_index` (number; optional): the ???ledger index??? of the open ledger version used to generate this response.
+ * `ledger_index` (number; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger version used to generate this response.
+ * `ledger_current_index` (number; optional): the [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the open ledger version used to generate this response.
* `limit` (number; optional): the limit value that was applied in this request, if specified.
- * `marker` (string — ???marker???; optional): server-defined value indicating pagination. Pass this to the next call to resume retrieving data where this response ended. Omitted when there are no additional pages.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): server-defined value indicating pagination. Pass this to the next call to resume retrieving data where this response ended. Omitted when there are no additional pages.
* `validated` (boolean; optional): if `true`, the data in this response originates from a validated ledger version; otherwise, it may be subject to change.
@@ -624,7 +616,7 @@ The `account_objects` array may be empty even if there are additional ledger ent
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -689,7 +681,7 @@ curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94a
> Retrieves info on the account's currency exchange offers.
-The `account_offers` method retrieves a list of ???offers??? made by a given ???account??? that are outstanding as of a particular ???ledger version???.
+The `account_offers` method retrieves a list of [offers]() made by a given [account]() that are outstanding as of a particular [ledger version]().
### Parameters
@@ -698,41 +690,36 @@ The `account_offers` method retrieves a list of ???offers??? made by a given ???
* `method` (string; required): a method used for the request.
* `params` (array; required):
- * `account` (string — ???address???; required): look up Offers placed by this account.
- * `ledger_hash` (string — ???hash???; optional): the unique hash of the ledger version to use (see ???Specifying Ledgers???).
- * `ledger_index` (number or string; optional): the ???ledger index??? of the ledger version to use, or a shortcut string to choose a ledger automatically (see ???Specifying Ledgers???).
- * `limit` (number; optional): limits the number of Offers to retrieve.
- * Must be between `10` and `400`; values outside this range are replaced with the nearest valid option.
- * Default: `200`.
- * `marker` (string — ???marker???; optional): value from a previous paginated response; resumes retrieving data where that response left off.
+ * `account` (string — [address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses); required): Look up Offers placed by this account.
+ * `ledger_hash` ([hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes); optional): The unique hash of the ledger version to use. (See [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers))
+ * `ledger_index` (ledger index; optional): The [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers))
+ * `limit` (number; optional): Limit the number of Offers to retrieve. The server may return fewer than this number of results. Must be within the inclusive range `10` to `400`. Positive values outside this range are replaced with the closest valid option. The default is `200`.
+ * `marker` (marker; optional): Value from a previous paginated response. Resume retrieving data where that response left off.
### Returns
-The response follows the ???standard format???, with a successful result containing the following fields:
-
- * `account` (string): the unique ???address??? identifying the account that created the offers.
- * `offers` (array of objects): list of offers made by this account that are outstanding as of the requested ledger version. If the number of offers is large, only up to the specified ???limit??? are returned per response. Each object contains the following fields:
- * `flags` (unsigned integer): bitwise flags representing options set for this offer entry.
- * `seq` (unsigned integer): the sequence number of the transaction that created this offer entry. (Transaction ???sequence numbers??? are relative to the account.)
- * `taker_gets` (string or object): the amount the offer receiver (taker) receives, expressed as either:
- * a string representing an amount in XRP, or
- * an object defining a non-XRP currency amount (see ???Specifying Currency Amounts???).
- * `taker_pays` (string or object): the amount the offer receiver (taker) provides, expressed as either:
- * a string representing an amount in XRP, or
- * an object defining a non-XRP currency amount (see ???Specifying Currency Amounts???).
- * `quality` (string): the exchange rate of the offer, calculated as the ratio of the original `taker_pays` divided by the original `taker_gets`.
- * Offers with a lower quality are more favorable and are executed first.
- * Offers with the same quality are executed in order of oldest to newest.
- * `expiration` (unsigned integer; optional): time after which this offer is considered unfunded, represented as ???seconds since the Ripple Epoch???. (See also: ???Offer Expiration???.)
- * `ledger_current_index` (number; optional): the ???ledger index?? of the current in-progress ledger version used when retrieving this data. Omitted if ledger_hash or ledger_index is provided.
- * `ledger_index` (number; optional): the ???ledger index??? of the ledger version used when retrieving this data. Omitted if ledger_current_index is provided instead.
- * `ledger_hash` (string — ???hash???; optional): the identifying hash of the ledger version used to generate this response.
- * `marker` (string — ???marker???; optional): server-defined value indicating pagination. Pass this to the next call to resume retrieving results where this response ended. Omitted when there are no additional pages.
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following fields:
+
+ * `account` (string): Unique [Address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses) identifying the account that made the offers.
+ * `offers` (array): Array of objects, where each object represents an offer made by this account that is outstanding as of the requested ledger version. If the number of offers is large, only returns up to `limit` at a time.
+ * `ledger_current_index` (number — [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index); optional): Omitted if `ledger_hash` or `ledger_index` is provided. The ledger index of the current in-progress ledger version, which was used when retrieving this data.
+ * `ledger_index` (number — [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index); optional): Omitted if `ledger_current_index` is provided instead. The ledger index of the ledger version that was used when retrieving this data, as requested.
+ * `ledger_hash` (string — [hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes); optional): The identifying hash of the ledger version that was used when retrieving this data.
+ * `marker` ([marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): Server-defined value indicating the response is paginated. Pass this to the next call to resume where this call left off. Omitted when there are no pages of information after this one.
+
+Each `offer` object contains the following fields:
+
+ * `flags` (unsigned integer): Options set for this offer entry as bit-flags.
+ * `seq` (unsigned integer): Sequence number of the transaction that created this entry. (Transaction [sequence numbers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#account-sequence) are relative to accounts.)
+ * `taker_gets` (string or object): The amount the account accepting the offer receives, as a String representing an amount in XRP, or a currency specification object. (See [Specifying Currency Amounts](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-currency-amounts)).
+ * `taker_pays` (string or object): The amount the account accepting the offer provides, as a String representing an amount in XRP, or a currency specification object. (See [Specifying Currency Amounts](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-currency-amounts)).
+ * `quality` (string): The exchange rate of the offer, as the ratio of the original `taker_pays` divided by the original `taker_gets`. When executing offers, the offer with the most favorable (lowest) quality is consumed first; offers with the same quality are executed from oldest to newest.
+ * `expiration` (unsigned integer; optional): A time after which this offer is considered unfunded, as the number of [seconds since the Ripple Epoch](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-time). See also: [Offer Expiration](https://xrpl.org/docs/concepts/tokens/decentralized-exchange/offers#offer-expiration).
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -777,15 +764,15 @@ The `account_tx` method retrieves a list of validated transactions that involve
* `params` (array; required):
* `account` (string; required): the unique identifier of the account, typically its address.
- * `tx_type` (string; optional): (Clio only) filters results to a specific transaction type (for example "Clawback", "AccountSet", "AccountDelete"). Case-insensitive. See ???Transaction Types???. ???New in: Clio v2.0???; ???AMM support since: Clio v2.1.0???.
+ * `tx_type` (string; optional): (Clio only) filters results to a specific transaction type (for example "Clawback", "AccountSet", "AccountDelete"). Case-insensitive. See [Transaction Types](https://xrpl.org/docs/references/protocol/transactions/types#transaction-types).
* `ledger_index_min` (integer; optional): earliest ledger index to include transactions from. A value of `-1` uses the earliest validated ledger available.
* `ledger_index_max` (integer; optional): most recent ledger index to include transactions from. A value of `-1` uses the most recent validated ledger available.
- * `ledger_hash` (string — hash; optional): specifies a single ledger by its unique hash (see ???Specifying Ledgers???).
- * `ledger_index` (string or unsigned integer; optional): specifies a single ledger by its index or a shortcut keyword (see ???Specifying Ledgers???).
+ * `ledger_hash` (string — hash; optional): specifies a single ledger by its unique hash (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `ledger_index` (string or unsigned integer; optional): specifies a single ledger by its index or a shortcut keyword (see [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
* `binary` (boolean; optional): if `true`, returns transactions as hex strings instead of JSON. Default: `false`.
* `forward` (boolean; optional): if `true`, returns results indexed with the oldest ledger first; otherwise, the newest ledger first. Each page may not be internally ordered, but pages overall follow the chosen order. Default: `false`.
* `limit` (integer; optional): limits the number of transactions to retrieve. The default varies depending on server configuration. The server is not required to honor this value.
- * `marker` (string — ???marker???; optional): value from a previous paginated response; resumes retrieving data where that response left off. Stable even if the server’s available ledger range changes.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): value from a previous paginated response; resumes retrieving data where that response left off. Stable even if the server’s available ledger range changes.
**Iterating over queried data**:
@@ -797,11 +784,11 @@ In the time between requests, `"ledger_index_min": -1` and `"ledger_index_max":
#### API v2
- * `account` (string): Unique ???Address??? identifying the related account.
- * `ledger_index_min` (integer — ???ledger index???): The ledger index of the earliest ledger actually searched for transactions.
- * `ledger_index_max` (integer — ???ledger index???): The ledger index of the most recent ledger actually searched for transactions.
+ * `account` (string): Unique [Address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses) identifying the related account.
+ * `ledger_index_min` (integer — [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index)): The ledger index of the earliest ledger actually searched for transactions.
+ * `ledger_index_max` (integer — [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index)): The ledger index of the most recent ledger actually searched for transactions.
* `limit` (integer): The `limit` value used in the request. (This may differ from the actual limit value enforced by the server.)
- * `marker` (string — ???marker???): Server-defined value indicating the response is paginated. Pass this to the next call to resume where this call left off.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination)): Server-defined value indicating the response is paginated. Pass this to the next call to resume where this call left off.
* `transactions` (array): Array of transactions matching the request's criteria, as explained below.
* `validated` (boolean): If included and set to `true`, the information in this response comes from a validated ledger version. Otherwise, the information is subject to change.
@@ -809,12 +796,12 @@ In the time between requests, `"ledger_index_min": -1` and `"ledger_index_max":
The server may respond with different values of `ledger_index_min` and `ledger_index_max` than you provided in the request, for example if it did not have the versions you specified on hand.
-Each transaction object includes the following fields, depending on whether it was requested in JSON or hex string (`"binary": true`) format:
+Each `transaction` object includes the following fields, depending on whether it was requested in JSON or hex string (`"binary": true`) format:
* `close_time_iso` (string): The ledger close time represented in ISO 8601 time format.
* `hash` (string): The unique hash identifier of the transaction.
* `ledger_hash` (string): A hex string of the ledger version that included this transaction.
- * `ledger_index` (integer): The ledger index of the ledger version that included this transaction.
+ * `ledger_index` (integer): The [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger version that included this transaction.
* `tx_json` (object — JSON): (JSON mode) JSON object defining the transaction.
* `tx_blob` (string — binary): (Binary mode) A unique hex string defining the transaction.
* `meta` (object — JSON): (JSON mode) The transaction results metadata in JSON.
@@ -823,11 +810,11 @@ Each transaction object includes the following fields, depending on whether it w
#### API v1
- * `account` (string): Unique ???Address??? identifying the related account.
- * `ledger_index_min` (integer — ???ledger index???): The ledger index of the earliest ledger actually searched for transactions.
- * `ledger_index_max` (integer — ???ledger index???): The ledger index of the most recent ledger actually searched for transactions.
+ * `account` (string): Unique [Address](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#addresses) identifying the related account.
+ * `ledger_index_min` (integer — [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index)): The ledger index of the earliest ledger actually searched for transactions.
+ * `ledger_index_max` (integer — [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index)): The ledger index of the most recent ledger actually searched for transactions.
* `limit` (integer): The `limit` value used in the request. (This may differ from the actual limit value enforced by the server.)
- * `marker` (string — ???marker???): Server-defined value indicating the response is paginated. Pass this to the next call to resume where this call left off.
+ * `marker` (string — [marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination)): Server-defined value indicating the response is paginated. Pass this to the next call to resume where this call left off.
* `transactions` (array): Array of transactions matching the request's criteria, as explained below.
* `validated` (boolean): If included and set to `true`, the information in this response comes from a validated ledger version. Otherwise, the information is subject to change.
@@ -835,9 +822,9 @@ Each transaction object includes the following fields, depending on whether it w
The server may respond with different values of `ledger_index_min` and `ledger_index_max` than you provided in the request, for example if it did not have the versions you specified on hand.
-Each transaction object includes the following fields, depending on whether it was requested in JSON or hex string (`"binary": true`) format.
+Each `transaction` object includes the following fields, depending on whether it was requested in JSON or hex string (`"binary": true`) format.
- * `ledger_index` (integer): The ledger index of the ledger version that included this transaction.
+ * `ledger_index` (integer): The [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger version that included this transaction.
* `tx` (object — JSON): (JSON mode) JSON object defining the transaction.
* `tx_blob` (string — binary): (Binary mode) Hex string representing the transaction.
* `meta` (object — JSON or string — binary): If `binary` is `true`, then this is a hex string of the transaction results metadata. Otherwise, the transaction results metadata is included in JSON format.
@@ -846,7 +833,7 @@ Each transaction object includes the following fields, depending on whether it w
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -919,7 +906,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1041,7 +1028,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1173,7 +1160,7 @@ If the request specified `"owner_funds": true` and expanded transactions, the re
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1244,7 +1231,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1293,7 +1280,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1360,7 +1347,7 @@ The format of each object in the `state` array depends on whether `binary` was s
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1424,23 +1411,23 @@ This method can retrieve several distinct types of data. You can select which ty
In addition to the general fields above, you must specify exactly 1 of the specific fields to indicate what type of entry to retrieve, along with its sub-fields as appropriate. The valid fields are:
- * [Get Ledger Entry by ID]()
- * [Get AccountRoot Entry]()
- * [Get AMM Entry]()
- * [Get Bridge Entry]()
- * [Get Credential Entry]()
- * [Get DirectoryNode Entry]()
- * [Get Offer Entry]()
- * [Get Oracle Entry]()
- * [Get RippleState Entry]()
- * [Get Check Entry]()
- * [Get Escrow Entry]()
- * [Get PayChannel Entry]()
- * [Get DepositPreauth Entry]()
- * [Get Ticket Entry]()
- * [Get NFT Page]()
- * [Get MPT Issuance Object]()
- * [Get MPToken Object]()
+ * [Get Ledger Entry by ID](/rpc-service/chains/chains-api/xrp/#get-ledger-entry-by-id)
+ * [Get AccountRoot Entry](/rpc-service/chains/chains-api/xrp/#get-accountroot-entry)
+ * [Get AMM Entry](/rpc-service/chains/chains-api/xrp/#get-amm-entry)
+ * [Get Bridge Entry](/rpc-service/chains/chains-api/xrp/#get-bridge-entry)
+ * [Get Credential Entry](/rpc-service/chains/chains-api/xrp/#get-credential-entry)
+ * [Get DirectoryNode Entry](/rpc-service/chains/chains-api/xrp/#get-directorynode-entry)
+ * [Get Offer Entry](/rpc-service/chains/chains-api/xrp/#get-offer-entry)
+ * [Get Oracle Entry](/rpc-service/chains/chains-api/xrp/#get-oracle-entry)
+ * [Get RippleState Entry](/rpc-service/chains/chains-api/xrp/#get-ripplestate-entry)
+ * [Get Check Entry](/rpc-service/chains/chains-api/xrp/#get-check-entry)
+ * [Get Escrow Entry](/rpc-service/chains/chains-api/xrp/#get-escrow-entry)
+ * [Get PayChannel Entry](/rpc-service/chains/chains-api/xrp/#get-paychannel-entry)
+ * [Get DepositPreauth Entry](/rpc-service/chains/chains-api/xrp/#get-depositpreauth-entry)
+ * [Get Ticket Entry](/rpc-service/chains/chains-api/xrp/#get-ticket-entry)
+ * [Get NFT Page](/rpc-service/chains/chains-api/xrp/#get-nft-page)
+ * [Get MPT Issuance Object](/rpc-service/chains/chains-api/xrp/#get-mpt-issuance-object)
+ * [Get MPToken Object](/rpc-service/chains/chains-api/xrp/#get-mptoken-object)
#### Get Ledger Entry by ID
@@ -1458,7 +1445,7 @@ Retrieve any type of ledger entry by its unique ID.
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1503,7 +1490,7 @@ curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94a
#### Get AccountRoot Entry
-Retrieve an [AccountRoot entry]() by its address. This is roughly equivalent to the ???account_info method.
+Retrieve an [AccountRoot entry]() by its address. This is roughly equivalent to the `account_info` method.
##### Parameters
@@ -1517,7 +1504,7 @@ Retrieve an [AccountRoot entry]() by its address. This is roughly equivalent to
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1569,7 +1556,7 @@ curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94a
#### Get AMM Entry
-Retrieve an Automated Market-Maker (AMM) object from the ledger. This is similar to ???amm_info method???, but the `ledger_entry` version returns only the ledger entry as stored.
+Retrieve an Automated Market-Maker (AMM) object from the ledger. This is similar to `amm_info` method but the `ledger_entry` version returns only the ledger entry as stored.
##### Parameters
@@ -1585,7 +1572,7 @@ Retrieve an Automated Market-Maker (AMM) object from the ledger. This is similar
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1675,7 +1662,7 @@ Retrieve a [Bridge entry](https://xrpl.org/docs/references/protocol/ledger-data/
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1753,7 +1740,7 @@ Retrieve a [Credential entry](https://xrpl.org/docs/references/protocol/ledger-d
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1816,7 +1803,7 @@ Retrieve a [DirectoryNode](https://xrpl.org/docs/references/protocol/ledger-data
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1884,7 +1871,7 @@ Retrieve an [Offer entry](https://xrpl.org/docs/references/protocol/ledger-data/
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -1955,7 +1942,7 @@ Retrieve an [Oracle entry](https://xrpl.org/docs/references/protocol/ledger-data
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2025,7 +2012,7 @@ Retrieve a [RippleState entry](https://xrpl.org/docs/references/protocol/ledger-
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2103,7 +2090,7 @@ Retrieve a [Check entry](https://xrpl.org/docs/references/protocol/ledger-data/l
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2171,7 +2158,7 @@ Retrieve an [Escrow entry](https://xrpl.org/docs/references/protocol/ledger-data
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2235,7 +2222,7 @@ Retrieve a [PayChannel entry](https://xrpl.org/docs/references/protocol/ledger-d
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2307,7 +2294,7 @@ Each member of the `deposit_preauth.authorized_credentials` array, if provided,
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2370,7 +2357,7 @@ Retrieve a [Ticket entry](https://xrpl.org/docs/references/protocol/ledger-data/
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2431,7 +2418,7 @@ Return an NFT Page in its raw ledger format.
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2498,7 +2485,7 @@ Return an `MPTokenIssuance` object.
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2559,7 +2546,7 @@ Return an `MPToken` object.
##### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2658,7 +2645,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2795,7 +2782,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
#### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2899,7 +2886,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
#### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -2931,7 +2918,7 @@ curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94a
> Sends a multi-signed transaction to the network.
-The `submit_multisigned` command applies a [multi-signed](https://xrpl.org/docs/concepts/accounts/multi-signing) transaction and sends it to the network to be included in future ledgers. (You can also submit multi-signed transactions in binary form using the `submit` command in ???submit-only mode???.)
+The `submit_multisigned` command applies a [multi-signed](https://xrpl.org/docs/concepts/accounts/multi-signing) transaction and sends it to the network to be included in future ledgers.
### Parameters
@@ -2956,7 +2943,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3004,7 +2991,7 @@ curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94a
> Retrieves info on the transaction from a particular ledger version.
-The `transaction_entry` method retrieves information on a single transaction from a specific ledger version. (The ???tx method???, by contrast, searches all ledgers for the specified transaction. We recommend using that method instead.)
+The `transaction_entry` method retrieves information on a single transaction from a specific ledger version. (The `tx` method by contrast, searches all ledgers for the specified transaction. We recommend using that method instead.)
### Parameters
@@ -3036,7 +3023,7 @@ The `transaction_entry` method retrieves information on a single transaction fro
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3103,7 +3090,7 @@ The response follows the [standard format](https://xrpl.org/docs/references/http
### Request example (CTID)
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3121,7 +3108,7 @@ curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94a
### Request example (Hash)
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3162,7 +3149,7 @@ Caution: This method is removed in [API v2](https://xrpl.org/docs/references/htt
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3282,7 +3269,7 @@ Each entry in the `vote_slots` array represents one liquidity provider's vote to
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3404,7 +3391,7 @@ Exchange rates involving XRP are always calculated using [drops of XRP](https://
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3535,7 +3522,7 @@ Each member of the `offers` array contains canonical fields of an [Offer entry](
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3627,7 +3614,7 @@ Note: If you provide a set of credentials that does not exactly match a set of c
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3707,7 +3694,7 @@ Each member of the `oracles` array is an oracle identifier object with the follo
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3804,7 +3791,7 @@ Each member of the `offers` array represents one [NFTokenOffer object](https://x
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3877,7 +3864,7 @@ Each member of the `offers` array represents one [NFTokenOffer object](https://x
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -3951,7 +3938,7 @@ Each element in the `alternatives` array is an object that represents a path fro
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -4047,10 +4034,15 @@ The `channel_verify` method checks the validity of a signature that can be used
### Parameters
- * `amount` (string; required): The amount of [XRP, in drops](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-currency-amounts), that the provided `signature` authorizes.
- * `channel_id` (string; required): The Channel ID of the channel that provides the amount. This is a 64-character hexadecimal string.
- * `public_key` (string; required): The public key of the channel and the key pair that was used to create the signature, in hexadecimal or the XRP Ledger's `base58` format.
- * `signature` (string; required): The signature to verify, in hexadecimal.
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required):
+
+ * `amount` (string; required): The amount of [XRP, in drops](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-currency-amounts), that the provided `signature` authorizes.
+ * `channel_id` (string; required): The Channel ID of the channel that provides the amount. This is a 64-character hexadecimal string.
+ * `public_key` (string; required): The public key of the channel and the key pair that was used to create the signature, in hexadecimal or the XRP Ledger's `base58` format.
+ * `signature` (string; required): The signature to verify, in hexadecimal.
### Returns
@@ -4059,7 +4051,7 @@ The `channel_verify` method checks the validity of a signature that can be used
### Request example
```shell
-curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94ac96c5e063c305f8dbe76d29' \
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
-d '{
"jsonrpc": "2.0",
"id": 1,
@@ -4094,63 +4086,1244 @@ curl 'https://rpc.ankr.com/xrp_mainnet/e65149e943f9f3a07d76cc87e6a90883e851ef94a
Use these methods to retrieve information about the current state of the rippled server.
-##
+## `fee`
+
+> Retrieves information on the transaction cost.
+
+The `fee` command reports the current state of the open-ledger requirements for the [transaction cost](https://xrpl.org/docs/concepts/transactions/transaction-cost). This requires the [FeeEscalation amendment](https://xrpl.org/resources/known-amendments#feeescalation) to be enabled.
+
+### Parameters
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required): none.
+### Returns
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following fields:
+ * `current_ledger_size` (string — integer): Number of transactions provisionally included in the in-progress ledger.
+ * `current_queue_size` (string — integer): Number of transactions currently queued for the next ledger.
+ * `drops` (object): Various information about the transaction cost (the `Fee` field of a transaction), in [drops of XRP](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-currency-amounts).
+ * `drops.base_fee` (string — integer): The transaction cost required for a [reference transaction](https://xrpl.org/docs/concepts/transactions/transaction-cost#reference-transaction-cost) to be included in a ledger under minimum load, represented in drops of XRP.
+ * `drops.median_fee` (string — integer): An approximation of the median transaction cost among transactions included in the previous validated ledger, represented in drops of XRP.
+ * `drops.minimum_fee` (string — integer): The minimum transaction cost for a [reference transaction](https://xrpl.org/docs/concepts/transactions/transaction-cost#reference-transaction-cost) to be queued for a later ledger, represented in drops of XRP. If greater than `base_fee`, the transaction queue is full.
+ * `drops.open_ledger_fee` (string — integer): The minimum transaction cost that a [reference transaction](https://xrpl.org/docs/concepts/transactions/transaction-cost#reference-transaction-cost) must pay to be included in the current open ledger, represented in drops of XRP.
+ * `expected_ledger_size` (string — integer): The approximate number of transactions expected to be included in the current ledger. This is based on the number of transactions in the previous ledger.
+ * `ledger_current_index` (number): The Ledger Index of the current open ledger these stats describe.
+ * `levels` (object): Various information about the transaction cost, in [fee levels](https://xrpl.org/docs/concepts/transactions/transaction-cost#fee-levels). The ratio in fee levels applies to any transaction relative to the minimum cost of that particular transaction.
+ * `levels.median_level` (string — integer): The median transaction cost among transactions in the previous validated ledger, represented in [fee levels](https://xrpl.org/docs/concepts/transactions/transaction-cost#fee-levels).
+ * `levels.minimum_level` (string — integer): The minimum transaction cost required to be queued for a future ledger, represented in [fee levels](https://xrpl.org/docs/concepts/transactions/transaction-cost#fee-levels).
+ * `levels.open_ledger_level` (string — integer): The minimum transaction cost required to be included in the current open ledger, represented in [fee levels](https://xrpl.org/docs/concepts/transactions/transaction-cost#fee-levels).
+ * `levels.reference_level` (string — integer): The equivalent of the minimum transaction cost, represented in [fee levels](https://xrpl.org/docs/concepts/transactions/transaction-cost#fee-levels).
+ * `max_queue_size` (string — integer): The maximum number of transactions that the [transaction queue](https://xrpl.org/docs/concepts/transactions/transaction-cost#queued-transactions) can currently hold.
+### Request example
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "fee",
+ "params": [{}]
+ }'
+```
+### Response example
+```json
+{
+ "result": {
+ "current_ledger_size": "89",
+ "current_queue_size": "0",
+ "drops": {
+ "base_fee": "10",
+ "median_fee": "5000",
+ "minimum_fee": "10",
+ "open_ledger_fee": "10"
+ },
+ "expected_ledger_size": "396",
+ "ledger_current_index": 100647307,
+ "levels": {
+ "median_level": "128000",
+ "minimum_level": "256",
+ "open_ledger_level": "256",
+ "reference_level": "256"
+ },
+ "max_queue_size": "7920",
+ "status": "success"
+ }
+}
+```
+---
+## `feature`
+> Retrieves information on the protocol amendments.
+The `feature` command returns information about [amendments](https://xrpl.org/docs/concepts/networks-and-servers/amendments) this server knows about, including whether they are enabled and if the server knows how to apply the amendments.
+### Parameters
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required):
+ * `feature` (string; optional): The unique ID of an amendment, as hexadecimal; or the short name of the amendment. If provided, limits the response to one amendment. Otherwise, the response lists all amendments.
- * [`fee`]() — retrieves information on the transaction cost.
- * [`feature`]() — retrieves information on the protocol amendments.
- * [`manifest`]() — retrieves public information on a known validator.
- * [`server_definitions`]() — retrieves an SDK-compatible `definitions.json`, generated from the `rippled` instance currently running.
- * [`server_info (rippled)`]() — retrieves status of the server in human-readable format.
- * [`server_state`]() — retrieves status of the server in machine-readable format.
- * [`version`]() — retrieves API version information.
+### Returns
-**Clio Methods**:
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing a map of amendments as a JSON object.
-These API methods are provided only by the Clio server, not `rippled`.
+The keys of the object are amendment IDs. The values for each key are amendment objects that describe the status of the amendment with that ID. If the request specified a `feature`, the map contains only the requested amendment object, after applying any changes from the request. Each amendment object has the following fields:
- * [`server_info`]() — retrieves status of the Clio server in human-readable format.
- * [`ledger`]() — retrieves info on the ledger version.
- * [`mpt_holders`]() — retrieves the holders of a given MPT issuance for a given ledger.
- * [`ledger_index`]() — retrieves a ledger by its close time.
- * [`nft_history`]() — retrieves the history of ownership and transfers for the specified NFT using Clio server's `nft_history` API.
- * [`nft_info`]() — retrieves information on the specified NFT using Clio server's `nft_info` API.
- * [`nfts_by_issuer`]() — retrieves the history of ownership and transfers for the specified NFT using Clio server's `nft_history` API.
- * [`version`]() — retrieves API version information.
+ * `enabled` (boolean): Whether this amendment is currently enabled in the latest ledger.
+ * `name` (string; optional): The human-readable name for this amendment, if known.
+ * `supported` (boolean): Whether the server knows how to apply this amendment. If this field is set to `false` (the server does not know how to apply this amendment) and `enabled` is set to `true` (this amendment is enabled in the latest ledger), this amendment may cause your server to be [amendment blocked](https://xrpl.org/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers).
-**Utility Methods**:
+### Request example
-Use these methods to perform convenient tasks, such as ping and random number generation.
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "fee",
+ "params": [
+ {
+ "feature": "4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373"
+ }
+ ]
+ }'
+```
+
+### Response example
+
+```json
+{
+ "id": 1,
+ "jsonrpc": "2.0",
+ "result": {
+ "current_ledger_size": "36",
+ "current_queue_size": "0",
+ "drops": {
+ "base_fee": "10",
+ "median_fee": "5000",
+ "minimum_fee": "10",
+ "open_ledger_fee": "10"
+ },
+ "expected_ledger_size": "396",
+ "ledger_current_index": 100647615,
+ "levels": {
+ "median_level": "128000",
+ "minimum_level": "256",
+ "open_ledger_level": "256",
+ "reference_level": "256"
+ },
+ "max_queue_size": "7920",
+ "status": "success"
+ }
+}
+```
+
+---
+
+## `manifest`
+
+> Retrieves public information on a known validator.
+
+The `manifest` method reports the current "manifest" information for a given validator public key. The "manifest" is a block of data that authorizes an ephemeral signing key with a signature from the validator's master key pair.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required):
+
+ * `public_key` (string; required): The [base58](https://xrpl.org/docs/references/protocol/data-types/base58-encodings)-encoded public key of the validator to look up. This can be the master public key or ephemeral public key.
+
+### Returns
+
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following fields:
+
+ * `details` (object; optional): The data contained in this manifest. Omitted if the server does not have a manifest for the `public_key` from the request. See Details Object below for a full description of its contents.
+ * `manifest` (string; optional): The full manifest data in base64 format. This data is serialized to binary before being base64-encoded. Omitted if the server does not have a manifest for the `public_key` from the request.
+ * `requested` (string): The `public_key` from the request.
+
+#### Details Object
+
+If provided, the `details` object contains the following fields:
+
+ * `domain` (string): The domain name this validator claims to be associated with. If the manifest does not contain a domain, this is an empty string.
+ * `ephemeral_key` (string): The ephemeral public key for this validator, in [base58](https://xrpl.org/docs/references/protocol/data-types/base58-encodings).
+ * `master_key` (string): The master public key for this validator, in [base58](https://xrpl.org/docs/references/protocol/data-types/base58-encodings).
+ * `seq` (number): The sequence number of this manifest. This number increases whenever the validator operator updates the validator's token to rotate ephemeral keys or change settings.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "manifest",
+ "params": [
+ {
+ "public_key":"nHUFE9prPXPrHcG3SkwP1UzAQbSphqyQkQK9ATXLZsfkezhhda3p"
+ }
+ ]
+ }'
+```
+
+### Response example
+
+```json
+{
+ "id": 1,
+ "jsonrpc": "2.0",
+ "result": {
+ "details": {
+ "domain": "alloy.ee",
+ "ephemeral_key": "n9LMfcjE6dMyshCqiftLFXpB9K3Mnd2r5bG7K8osmrkFpHUoR3c1",
+ "master_key": "nHUFE9prPXPrHcG3SkwP1UzAQbSphqyQkQK9ATXLZsfkezhhda3p",
+ "seq": 4
+ },
+ "manifest": "JAAAAARxIe3AkJgOyqs3y+UuiAI27Ff3Mrfbt8e7mjdo06bnGEp5XnMhAu2LSAwZEQnm/mq9K6sSZJk5JkbcKCv6C7vQW2C8RnZVdkcwRQIhAI9uwQ1p58oyob1E+DaFLwjTdiRbVIKSMPqaaUwnJdN2AiB79DlPXHwztNULraVTkehbDsCAyDdf3VZB3FvkCZNOFHcIYWxsb3kuZWVwEkBf6A9ktcj2H4a61Av8ujQFL2KNcmr/FuEKbwlZEniJvhf0UqNiYc2bAsTJE5wMn00E0JBbw2m9OFwto50DcdkC",
+ "requested": "nHUFE9prPXPrHcG3SkwP1UzAQbSphqyQkQK9ATXLZsfkezhhda3p",
+ "status": "success"
+ }
+}
+```
+
+---
+
+## `server_definitions`
+
+> Retrieves an SDK-compatible `definitions.json` generated from the currently running `rippled` instance.
+
+The `server_definitions` command returns an SDK-compatible `definitions.json`, generated from the `rippled` instance currently running. You can use this to query a node in a network, quickly receiving the definitions necessary to serialize/deserialize its binary data.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required): none.
+
+### Returns
+
+To see a full `definitions.json` file and descriptions of the top-level fields, see the [Definitions File](https://xrpl.org/docs/references/protocol/binary-format#definitions-file).
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "server_definitions",
+ "params": []
+ }'
+```
+
+### Response example
+
+```json
+{
+ "id": 1,
+ "result": {
+ "FIELDS": [
+ [
+ "Generic",
+ {
+ "isSerialized": false,
+ "isSigningField": false,
+ "isVLEncoded": false,
+ "nth": 0,
+ "type": "Unknown"
+ }
+ ],
+ [
+ "Invalid",
+ {
+ "isSerialized": false,
+ "isSigningField": false,
+ "isVLEncoded": false,
+ "nth": -1,
+ "type": "Unknown"
+ }
+ ],
+ [
+ "ObjectEndMarker",
+ {
+ "isSerialized": true,
+ "isSigningField": true,
+ "isVLEncoded": false,
+ "nth": 1,
+ "type": "STObject"
+ }
+ ],
+ [
+ "ArrayEndMarker",
+ {
+ "isSerialized": true,
+ "isSigningField": true,
+ "isVLEncoded": false,
+ "nth": 1,
+ "type": "STArray"
+ }
+ ]
+ ...
+ ]
+ }
+}
+```
+
+---
+
+## `server_info (rippled)`
+
+> Retrieves status of the server in human-readable format.
- * [`json`]() — passes JSON through the commandline.
- * [`ping`]() — confirms connectivity with the server.
- * [`random`]() — generates a random number.
+The `server_info` command asks the server for a human-readable version of various information about the [`rippled` server](https://xrpl.org/docs/concepts/networks-and-servers) being queried.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required):
+
+ * `counters` (boolean; optional): If `true`, return metrics about the job queue, ledger store, and API method activity. The default is `false`.
+
+### Returns
+
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing an `info` object as its only field.
+
+The `info` object may have some arrangement of the following fields:
+
+ * `amendment_blocked` (boolean; may be omitted): If `true`, this server is amendment blocked. If the server is not [amendment blocked](https://xrpl.org/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), the response omits this field.
+ * `build_version` (string): The version number of the running `rippled` server.
+ * `closed_ledger` (object; may be omitted): Information on the most recently closed ledger that has not been validated by consensus, as a [Server Ledger Object](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info#server-ledger-object). If the most recently validated ledger is available, the response omits this field and includes `validated_ledger` instead.
+ * `complete_ledgers` (string): Range expression indicating the sequence numbers of the ledger versions the local `rippled` has in its database. This may be a disjoint sequence such as `24900901-24900984,24901116-24901158`. If the server does not have any complete ledgers (for example, it recently started syncing with the network), this is the string `empty`.
+ * `git` (object; admin only): The Git details of your `rippled` build.
+ * `git.branch` (string; admin only): The Git branch used to build your version of `rippled`.
+ * `git.hash` (string; admin only): The Git hash of the commit used to build your version of `rippled`.
+ * `hostid` (string): On an admin request, returns the hostname of the server running the `rippled` instance; otherwise, returns a single [RFC-1751](https://tools.ietf.org/html/rfc1751) word based on the [node public key](https://xrpl.org/docs/concepts/networks-and-servers/peer-protocol#node-key-pair).
+ * `io_latency_ms` (number): Amount of time spent waiting for I/O operations, in milliseconds. If this number is not very, very low, then the `rippled` server is probably having serious load issues.
+ * `jq_trans_overflow` (string — number): The number of times (since starting up) that this server has had over 250 transactions waiting to be processed at once. A large number here may mean that your server is unable to handle the transaction load of the XRP Ledger network. For detailed recommendations of future-proof server specifications, see [Capacity Planning](https://xrpl.org/docs/infrastructure/installation/capacity-planning).
+ * `last_close` (object): Information about the last time the server closed a ledger, including the amount of time it took to reach a consensus and the number of trusted validators participating.
+ * `last_close.converge_time_s` (number): The amount of time it took to reach a consensus on the most recently validated ledger version, in seconds.
+ * `last_close.proposers` (number): How many trusted validators the server considered (including itself, if configured as a validator) in the consensus process for the most recently validated ledger version.
+ * `load` (object; admin only): Detailed information about the current load state of the server.
+ * `load.job_types` (array; admin only): Information about the rate of different types of jobs the server is doing and how much time it spends on each.
+ * `load.threads` (number; admin only): The number of threads in the server's main job pool.
+ * `load_factor` (number): The multiplier to the [transaction cost](https://xrpl.org/docs/concepts/transactions/transaction-cost) the server is currently enforcing. For example, at `1000` load factor and a reference transaction cost of 10 drops of XRP, the load-scaled transaction cost is 10,000 drops (0.01 XRP). The load factor is determined by the highest of the individual server's load factor, the cluster's load factor, the open ledger cost, and the overall network's load factor.
+ * `load_factor_local` (number; may be omitted): The current multiplier to the transaction cost based on load to this server.
+ * `load_factor_net` (number; may be omitted): The current multiplier to the transaction cost being used by the rest of the network.
+ * `load_factor_cluster` (number; may be omitted): The current multiplier to the transaction cost based on load to servers in this [cluster](https://xrpl.org/docs/concepts/networks-and-servers/clustering).
+ * `load_factor_fee_escalation` (number; may be omitted): The current multiplier to the transaction cost that a transaction must pay to get into the open ledger.
+ * `load_factor_fee_queue` (number; may be omitted): The current multiplier to the transaction cost required to get into the queue, if the queue is full.
+ * `load_factor_server` (number; may be omitted): The current multiplier based on server, cluster, and network load (not including open ledger cost).
+ * `network_ledger` (string; may be omitted): When [starting the server with the `--net` parameter](https://xrpl.org/docs/infrastructure/commandline-usage), this field contains the string `waiting` while the server is syncing to the network.
+ * `peers` (number): How many other `rippled` servers this one is currently connected to.
+ * `ports` (array): A list of ports where the server is listening for API commands. Each entry is a [Port Descriptor object](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info#port-descriptor-object).
+ * `pubkey_node` (string): Public key used to verify this server for peer-to-peer communications. This [node key pair](https://xrpl.org/docs/concepts/networks-and-servers/peer-protocol#node-key-pair) is automatically generated by the server the first time it starts up. (If deleted, the server can create a new pair of keys.) You can set a persistent value in the config file using the `[node_seed]` config option, which is useful for [clustering](https://xrpl.org/docs/concepts/networks-and-servers/clustering).
+ * `pubkey_validator` (string; admin only): Public key used by this node to sign ledger validations. This validation key pair is derived from the `[validator_token]` or `[validation_seed]` config field.
+ * `server_state` (string): A string indicating to what extent the server is participating in the network. See [Possible Server States](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/rippled-server-states) for more details.
+ * `server_state_duration_us` (number): The number of consecutive microseconds the server has been in the current state.
+ * `state_accounting` (object): A map of [various server states](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/rippled-server-states) with information about the time the server spends in each. This can be useful for tracking the long-term health of your server's connectivity to the network. The contents of this field are formatted as [State Accounting Objects](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info#state-accounting-object).
+ * `uptime` (number): Number of consecutive seconds that the server has been operational.
+ * `validated_ledger` (object; may be omitted): Information about the most recent fully-validated ledger, as a [Server Ledger Object](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info#server-ledger-object). If not available, omitted and `closed_ledger` is included instead.
+ * `validation_quorum` (number): Minimum number of trusted validations required to validate a ledger version.
+ * `validator_list_expires` (string; admin only): Either the human-readable time, in UTC, when the current validator list expires, or the string `unknown` if the server has yet to load a published validator list, or the string `never` if the server uses a static validator list.
+ * `counters` (object): Performance metrics regarding RPC calls, JobQueue, and nodestore details (`node_writes`, `node_reads_total`, `node_reads_hit`, etc.).
+ * `current_activity` (object): Lists items currently being run in the job queue and contains two arrays for `jobs` and `methods`.
+
+#### Port Descriptor Object
+
+Each member of the `ports` array is an object with the following fields:
+
+ * `port` (string — number): A port number where the server is listening.
+ * `protocol` (array of string): A list of protocols being served on this port. Valid protocols include `http` or `https` for JSON-RPC, `ws`, `ws2`, `wss`, `wss2` for WebSocket, `grpc` for gRPC, and `peer` for the [XRP Ledger Peer Protocol](https://xrpl.org/docs/concepts/networks-and-servers/peer-protocol).
+
+#### State Accounting Object
+
+Each field in the `state_accounting` object has a key that refers to a specific [server state](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/rippled-server-states), and a value that is an object with the following fields:
+
+ * `duration_us` (string — number): The number of microseconds the server has spent in this state. (This is updated whenever the server transitions into another state.)
+ * `transitions` (string — number): The number of times the server has changed into this state.
+
+#### Server Ledger Object
+
+The response provides either a `validated_ledger` field or a `closed_ledger` field. Either field contains an object with the following fields:
+
+ * `age` (number): The time since the ledger was closed, in seconds.
+ * `base_fee_xrp` (number): Base fee, in XRP (not drops). This may be represented in scientific notation such as `1e-05` for `0.00001`.
+ * `hash` (string — [hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes)): Unique hash for the ledger, as hexadecimal.
+ * `reserve_base_xrp` (number): Minimum amount of XRP (not drops) necessary for every account to keep in reserve.
+ * `reserve_inc_xrp` (number): Amount of XRP (not drops) added to the account reserve for each object an account owns in the ledger.
+ * `seq` (number): The [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the latest validated ledger.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "server_info",
+ "params": [{"counters" : false}]
+ }'
+```
+### Response example
+```json
+{
+ "result": {
+ "info": {
+ "build_version": "2.6.2",
+ "complete_ledgers": "100146025-100650763",
+ "hostid": "SAD",
+ "initial_sync_duration_us": "292599227",
+ "io_latency_ms": 1,
+ "jq_trans_overflow": "0",
+ "last_close": {
+ "converge_time_s": 3,
+ "proposers": 35
+ },
+ "load_factor": 1,
+ "peer_disconnects": "18440",
+ "peer_disconnects_resources": "3",
+ "peers": 49,
+ "ports": [
+ {
+ "port": "51235",
+ "protocol": [
+ "peer"
+ ]
+ },
+ {
+ "port": "51234",
+ "protocol": [
+ "http"
+ ]
+ },
+ {
+ "port": "51233",
+ "protocol": [
+ "ws"
+ ]
+ },
+ {
+ "port": "50051",
+ "protocol": [
+ "grpc"
+ ]
+ }
+ ],
+ "pubkey_node": "n94B86FddoyYsndK6N8gZwcD5xoMonptkHxmWnNqc22naS5V1pF8",
+ "server_state": "full",
+ "server_state_duration_us": "99692864611",
+ "state_accounting": {
+ "connected": {
+ "duration_us": "283465932",
+ "transitions": "2"
+ },
+ "disconnected": {
+ "duration_us": "1040136",
+ "transitions": "2"
+ },
+ "full": {
+ "duration_us": "99692864611",
+ "transitions": "1"
+ },
+ "syncing": {
+ "duration_us": "8093158",
+ "transitions": "1"
+ },
+ "tracking": {
+ "duration_us": "0",
+ "transitions": "1"
+ }
+ },
+ "time": "2025-Dec-04 15:01:28.199321 UTC",
+ "uptime": 99985,
+ "validated_ledger": {
+ "age": 4,
+ "base_fee_xrp": 1e-05,
+ "hash": "DC9E71BB38F18D5202594FA800230B0B080199704D7CA02BD2524ED49170DA2F",
+ "reserve_base_xrp": 1,
+ "reserve_inc_xrp": 0.2,
+ "seq": 100650763
+ },
+ "validation_quorum": 28
+ },
+ "status": "success"
+ }
+}
+```
+---
+## `server_state`
+> Retrieves status of the server in machine-readable format.
+The `server_state` command asks the server for various machine-readable information about the `rippled` server's current state. The response is almost the same as the `server_info` `rippled` method, but uses units that are easier to process instead of easier to read. (For example, XRP values are given in integer drops instead of scientific notation or decimal values, and time is given in milliseconds instead of seconds.)
+The Clio server does not support `server_state` directly, but you can ask for the `server_state` of the `rippled` server that Clio is connected to. Specify `"ledger_index": "current"` (WebSocket) or `"params": [{"ledger_index": "current"}]` (JSON-RPC).
+### Parameters
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required): none.
+### Returns
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing a `state` object as its only field.
+
+The `state` object may have some arrangement of the following fields:
+
+ * `amendment_blocked` (boolean): (May be omitted) If `true`, this server is [amendment blocked](https://xrpl.org/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers). If the server is not amendment blocked, the response omits this field.
+ * `build_version` (string): The version number of the running `rippled` version.
+ * `complete_ledgers` (string): Range expression indicating the sequence numbers of the ledger versions the local `rippled` has in its database. It is possible to be a disjoint sequence, e.g. "2500-5000,32570-7695432". If the server does not have any complete ledgers (for example, it recently started syncing with the network), this is the string `empty`.
+ * `closed_ledger` (object): (May be omitted) Information on the most recently closed ledger that has not been validated by consensus, as a [Server Ledger Object](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state#server-ledger-object). If the most recently validated ledger is available, the response omits this field and includes `validated_ledger` instead.
+ * `io_latency_ms` (number): Amount of time spent waiting for I/O operations, in milliseconds. If this number is not very, very low, then the `rippled` server is probably having serious load issues.
+ * `jq_trans_overflow` (string — number): The number of times this server has had over 250 transactions waiting to be processed at once. A large number here may mean that your server is unable to handle the transaction load of the XRP Ledger network. For detailed recommendations of future-proof server specifications, see [Capacity Planning](https://xrpl.org/docs/infrastructure/installation/capacity-planning).
+ * `last_close` (object): Information about the last time the server closed a ledger, including the amount of time it took to reach a consensus and the number of trusted validators participating.
+ * `last_close.converge_time` (number): The amount of time it took to reach a consensus on the most recently validated ledger version, in milliseconds.
+ * `last_close.proposers` (number): How many trusted validators the server considered (including itself, if configured as a validator) in the consensus process for the most recently validated ledger version.
+ * `load` (object): (Admin only) Detailed information about the current load state of the server.
+ * `load.job_types` (array): (Admin only) Information about the rate of different types of jobs the server is doing and how much time it spends on each.
+ * `load.threads` (number): (Admin only) The number of threads in the server's main job pool.
+ * `load_base` (number): The baseline amount of server load used in [transaction cost](https://xrpl.org/docs/concepts/transactions/transaction-cost) calculations. If the `load_factor` is equal to the `load_base`, then only the base transaction cost is enforced. If the `load_factor` is higher than the `load_base`, then transaction costs are multiplied by the ratio between them. For example, if the `load_factor` is double the `load_base`, then transaction costs are doubled.
+ * `load_factor` (number): The load factor the server is currently enforcing. The ratio between this value and the `load_base` determines the multiplier for transaction costs. The load factor is determined by the highest of the individual server's load factor, the cluster's load factor, the open ledger cost, and the overall network's load factor.
+ * `load_factor_fee_escalation` (number): (May be omitted) The current multiplier to the transaction cost to get into the open ledger, in [fee levels](https://xrpl.org/docs/concepts/transactions/transaction-cost#fee-levels).
+ * `load_factor_fee_queue` (number): (May be omitted) The current multiplier to the transaction cost to get into the queue, if the queue is full, in fee levels.
+ * `load_factor_fee_reference` (number): (May be omitted) The transaction cost with no load scaling, in fee levels.
+ * `load_factor_server` (number): (May be omitted) The load factor the server is enforcing, based on load to the server, cluster, and network, but not factoring in the open ledger cost.
+ * `network_ledger` (string): (May be omitted) When [starting the server with the `--net` parameter](https://xrpl.org/docs/infrastructure/commandline-usage), this field contains the string `waiting` while the server is syncing to the network. The field is omitted otherwise.
+ * `peers` (number): How many other `rippled` servers this one is currently connected to.
+ * `ports` (array): A list of ports where the server is listening for API commands. Each entry in the array is a [Port Descriptor object](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state#port-descriptor-object).
+ * `pubkey_node` (string): Public key used to verify this server for peer-to-peer communications. This node key pair is automatically generated by the server the first time it starts up. (If deleted, the server can create a new pair of keys.) You can set a persistent value in the config file using the `[node_seed]` config option, which is useful for [clustering](https://xrpl.org/docs/concepts/networks-and-servers/clustering).
+ * `pubkey_validator` (string): (Admin only) Public key used by this node to sign ledger validations. This validation key pair is derived from the `[validator_token]` or `[validation_seed]` config field.
+ * `server_state` (string): A string indicating to what extent the server is participating in the network. See [Possible Server States](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/rippled-server-states) for more details.
+ * `server_state_duration_us` (number): The number of consecutive microseconds the server has been in the current state.
+ * `state_accounting` (object): A map of various [server states](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/rippled-server-states) with information about the time the server spends in each. This can be useful for tracking the long-term health of your server's connectivity to the network. The contents of this field are formatted as [State Accounting Objects](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state#state-accounting-object).
+ * `time` (string): The current time in UTC, according to the server's clock.
+ * `uptime` (number): Number of consecutive seconds that the server has been operational.
+ * `validated_ledger` (object): (May be omitted) Information about the most recent fully-validated ledger, as a [Server Ledger Object](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state#server-ledger-object). If the most recent validated ledger is not available, the response omits this field and includes `closed_ledger` instead.
+ * `validation_quorum` (number): Minimum number of trusted validations required to validate a ledger version. Some circumstances may cause the server to require more validations.
+ * `validator_list_expires` (number): (Admin only) When the current validator list expires, in [seconds since the Ripple Epoch](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-time), or 0 if the server has yet to load a published validator list.
+
+#### Port Descriptor Object
+
+Each member of the `ports` array is an object with the following fields:
+
+ * `port` (string — number): A port number where the server is listening.
+ * `protocol` (array of string): A list of protocols being served on this port. Valid protocols include `http` or `https` for JSON-RPC, `ws`, `ws2`, `wss`, `wss2` for WebSocket, `grpc` for gRPC, and `peer` for the [XRP Ledger Peer Protocol](https://xrpl.org/docs/concepts/networks-and-servers/peer-protocol).
+
+#### State Accounting Object
+
+Each field in the `state_accounting` object has a key that refers to a specific [server state](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/rippled-server-states), and a value that is an object with the following fields:
+
+ * `duration_us` (string — number): The number of microseconds the server has spent in this state. (This is updated whenever the server transitions into another state.)
+ * `transitions` (string — number): The number of times the server has changed into this state.
+
+#### Server Ledger Object
+
+The response provides either a `validated_ledger` field or a `closed_ledger` field. Either field contains an object with the following fields:
+
+ * `base_fee` (number): The base fee, in drops of XRP, for propagating a transaction to the network, as of this ledger version.
+ * `close_time` (number): The official close time of this ledger version, in [seconds since the Ripple Epoch](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-time). This value is rounded; see [Ledger Close Times](https://xrpl.org/docs/concepts/ledgers/ledger-close-times) for details.
+ * `hash` (string — [hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes)): The unique hash of this ledger version, as hexadecimal.
+ * `reserve_base` (number): The minimum [account reserve](https://xrpl.org/docs/concepts/accounts/reserves), as of the most recent validated ledger version.
+ * `reserve_inc` (number): The [owner reserve](https://xrpl.org/docs/concepts/accounts/reserves) for each item an account owns, as of the most recent validated ledger version.
+ * `seq` (number): The [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of this ledger version.
+### Request example
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "server_state",
+ "params": []
+ }'
+```
+### Response example
+```json
+{
+ "result": {
+ "state": {
+ "build_version": "2.6.2",
+ "complete_ledgers": "100145467-100651296",
+ "initial_sync_duration_us": "397921122",
+ "io_latency_ms": 1,
+ "jq_trans_overflow": "0",
+ "last_close": {
+ "converge_time": 3001,
+ "proposers": 35
+ },
+ "load_base": 256,
+ "load_factor": 256,
+ "load_factor_fee_escalation": 256,
+ "load_factor_fee_queue": 256,
+ "load_factor_fee_reference": 256,
+ "load_factor_server": 256,
+ "peer_disconnects": "15089",
+ "peer_disconnects_resources": "7",
+ "peers": 24,
+ "ports": [
+ {
+ "port": "51235",
+ "protocol": [
+ "peer"
+ ]
+ },
+ {
+ "port": "51234",
+ "protocol": [
+ "http"
+ ]
+ },
+ {
+ "port": "51233",
+ "protocol": [
+ "ws"
+ ]
+ },
+ {
+ "port": "50051",
+ "protocol": [
+ "grpc"
+ ]
+ }
+ ],
+ "pubkey_node": "n94B86FddoyYsndK6N8gZwcD5xoMonptkHxmWnNqc22naS5V1pF8",
+ "server_state": "full",
+ "server_state_duration_us": "101916702241",
+ "state_accounting": {
+ "connected": {
+ "duration_us": "391641811",
+ "transitions": "2"
+ },
+ "disconnected": {
+ "duration_us": "2071962",
+ "transitions": "2"
+ },
+ "full": {
+ "duration_us": "101916702241",
+ "transitions": "1"
+ },
+ "syncing": {
+ "duration_us": "4207345",
+ "transitions": "1"
+ },
+ "tracking": {
+ "duration_us": "1",
+ "transitions": "1"
+ }
+ },
+ "time": "2025-Dec-04 15:35:55.844094 UTC",
+ "uptime": 102314,
+ "validated_ledger": {
+ "base_fee": 10,
+ "close_time": 818177751,
+ "hash": "883E90590C94615CA601D2B9C577FE9AD382ADD5065550EA8021B8088AFD4581",
+ "reserve_base": 1000000,
+ "reserve_inc": 200000,
+ "seq": 100651296
+ },
+ "validation_quorum": 28
+ },
+ "status": "success"
+ }
+}
+```
+
+---
+
+## `version`
+
+> Retrieves API version information.
+
+The `version` command retrieves the API version information for the rippled server. For `Clio` servers, see `version` (`clio`) instead.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required): none.
+
+### Returns
+
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing a version object as its only field.
+
+The `version` object returns some arrangement of the following fields:
+
+ * `first` (string): Lowest supported API release.
+ * `last` (string): Highest supported API release.
+ * `good` (string): Default API if none specified.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "version",
+ "params": []
+ }'
+```
+
+### Response example
+
+```json
+{
+ "id": 1,
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "success",
+ "version": {
+ "first": "1.0.0",
+ "good": "1.0.0",
+ "last": "1.0.0"
+ }
+ }
+}
+```
+
+---
+
+**Clio Methods**:
+
+These API methods are provided only by the Clio server, not `rippled`.
+
+## `server_info`
+
+> Retrieves status of the Clio server in human-readable format.
+
+The `server_info` command asks the [Clio server](https://xrpl.org/docs/concepts/networks-and-servers/the-clio-server) for a human-readable version of various information about the Clio server being queried. For `rippled` servers, see `server_info` (`rippled`) instead.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required): none.
+
+### Returns
+
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing an `info` object as its only field.
+
+The `info` object may have some arrangement of the following fields:
+
+ * `complete_ledgers` (string): Range expression indicating the sequence numbers of the ledger versions the local `rippled` has in its database. This may be a disjoint sequence such as `24900901-24900984,24901116-24901158`. If the server does not have any complete ledgers (for example, it recently started syncing with the network), this is the string `empty`.
+ * `counters` (object; optional): Stats on API calls handled since server startup. This is present only if the client connects to the Clio server over `localhost`.
+ * `rpc` (object; optional): Stats on each API call handled by the Clio server since startup. Since this is nested within the `counters` object, this is also present only if the client connects to the Clio server over `localhost`. The rpc object is a map of API method names to API Stats Objects.
+ * `subscriptions` (object; optional): Number of current subscribers for each stream type. Since this is nested within the `counters` object, this is also present only if the client connects to the Clio server over `localhost`.
+ * `subscriptions.ledger`
+ * `subscriptions.transactions`
+ * `subscriptions.transactions_proposed`
+ * `subscriptions.manifests`
+ * `subscriptions.validations`
+ * `subscriptions.account`
+ * `subscriptions.accounts_proposed`
+ * `subscriptions.books`
+ * `time` (string): The current time in UTC, according to the server's clock.
+ * `uptime` (number): Number of consecutive seconds that the server has been operational.
+ * `amendment_blocked` (boolean; optional): Whether the Clio server is Amendment Blocked.
+ * `load_factor` (number): The load-scaled open ledger transaction cost the server is currently enforcing, as a multiplier on the base transaction cost. For example, at `1000` load factor and a reference transaction cost of 10 drops of XRP, the load-scaled transaction cost is 10,000 drops (0.01 XRP). The load factor is determined by the highest of the [individual server's load factor](https://xrpl.org/docs/concepts/transactions/transaction-cost#local-load-cost), the cluster's load factor, the [open ledger cost](https://xrpl.org/docs/concepts/transactions/transaction-cost#open-ledger-cost), and the overall network's load factor.
+ * `clio_version` (string): The version number of the running Clio server.
+ * `libxrpl_version` (string): The version number of the `libxrpl` library this Clio server was built against.
+ * `validation_quorum` (number; optional): Minimum number of trusted validations required to validate a ledger version. Some circumstances may cause the server to require more validations. This value is obtained from `rippled`. This field may be omitted from the response if the Clio server is unable to connect to `rippled` for some reason.
+ * `rippled_version` (string; optional): The version number of the running `rippled` server that the Clio server is connected to. This field may be omitted from the response if the Clio server is unable to connect to `rippled` for some reason.
+ * `network_id` (string; optional): The network ID of the network that the `rippled` this Clio server is connected to is operating on. This field may be omitted from the response if the Clio server is unable to connect to `rippled` for some reason.
+ * `validated_ledger` (object; optional): Information about the most recent fully-validated ledger. If the most recent validated ledger is not available, the response omits this field and includes `closed_ledger` instead.
+ * `validated_ledger.age` (number): The time since the ledger was closed, in seconds.
+ * `validated_ledger.base_fee_xrp` (number): Base fee, in XRP. This may be represented in scientific notation such as `1e-05` for `0.00001`.
+ * `validated_ledger.hash` (string): Unique hash for the ledger, as hexadecimal.
+ * `validated_ledger.reserve_base_xrp` (number): Minimum amount of XRP (not drops) necessary for every account to keep in reserve. This may be represented in scientific notation such as `1e-05` for `0.00001`.
+ * `validated_ledger.reserve_inc_xrp` (number): Amount of XRP (not drops) added to the account reserve for each object an account owns in the ledger. This may be represented in scientific notation such as `1e-05` for `0.00001`.
+ * `validated_ledger.seq` (number): The [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the latest validated ledger.
+ * `validator_list_expires` (string): (Admin only) Either the human-readable time, in UTC, when the current validator list expires, the string `unknown` if the server has yet to load a published validator list or the string `never` if the server uses a static validator list.
+ * `cache` (object): Information on Clio's state data cache.
+ * `cache.size` (number): Number of state data objects currently in the cache.
+ * `cache.is_full` (boolean): True if cache contains all state data for a specific ledger, false otherwise. Some API calls, such as the book_offers method, process much faster when the cache is full.
+ * `cache.latest_ledger_seq` (number): The ledger index of the latest validated ledger stored in the cache.
+ * `etl` (object): The `rippled` sources (ETL sources) that the Clio server is connected to. This is present only if the client connects to the Clio server over `localhost`.
+ * `etl.etl_sources` (array): List the `rippled` sources (ETL sources) that the Clio server is connected to and extracts data from.
+ * `etl.etl_sources.validated_range` (string): The validated ledger range retrieved by the P2P `rippled` server.
+ * `etl.etl_sources.is_connected` (boolean): True if Clio is connected to this source via websocket, false otherwise. A value of false here could indicate a networking issue, or that `rippled` is not running, amongst other things.
+ * `etl.etl_sources.ip` (number): IP of the `rippled` server.
+ * `etl.etl_sources.ws_port` (number): Websocket port of the `rippled` server.
+ * `etl.etl_sources.grpc_port` (number): The gRPC connection port of the P2P `rippled` server that the Clio server is connected to.
+ * `etl.etl_sources.last_msg_age_seconds` (number): Total seconds that have elapsed since Clio last heard anything from `rippled`. This should not be higher than 8.
+ * `etl.is_writer` (boolean): `true` if this Clio server is currently writing data to the database, `false` otherwise.
+ * `etl.read_only` (boolean): `true` if this Clio server is configured in read-only mode, `false` otherwise.
+ * `etl.last_publish_age_seconds` (number): Time in seconds that have elapsed since this Clio server last published a ledger. This should not be more than 8.
+ * `validated` (boolean): When `true`, this indicates that the response uses a ledger version that has been validated by consensus. In Clio, this is always true as Clio stores and returns validated ledger data. If a request was forwarded to `rippled` and the server returns current data, a missing or `false` value indicates that this ledger's data is not final.
+ * `status` (string): Returns the status of the API request: `success` when the request completes successfully.
+
+#### API Stats Objects
+
+An API Stats object provides key metrics for every API call handled by the Clio server since startup. It includes the following fields:
+
+ * `started` (number): Number of API calls of this type that the Clio server has started processing since startup.
+ * `finished` (number): Number of API calls of this type that the Clio server has finished processing since startup.
+ * `errored` (number): Number of API calls of this type that have resulted in some sort of error since startup.
+ * `forwarded` (number): Number of API calls of this type that the Clio server has forwarded to a `rippled` P2P server since startup.
+ * `duration_us` (number): The total number of microseconds spent processing API calls of this type since startup.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "server_info",
+ "params": []
+ }'
+```
+
+### Response example
+
+```json
+{
+ "result": {
+ "info": {
+ "build_version": "2.6.2",
+ "complete_ledgers": "100146025-100669999",
+ "hostid": "SAD",
+ "initial_sync_duration_us": "292599227",
+ "io_latency_ms": 1,
+ "jq_trans_overflow": "0",
+ "last_close": {
+ "converge_time_s": 3,
+ "proposers": 35
+ },
+ "load_factor": 1,
+ "peer_disconnects": "25682",
+ "peer_disconnects_resources": "10",
+ "peers": 50,
+ "ports": [
+ {
+ "port": "51235",
+ "protocol": [
+ "peer"
+ ]
+ },
+ {
+ "port": "51234",
+ "protocol": [
+ "http"
+ ]
+ },
+ {
+ "port": "51233",
+ "protocol": [
+ "ws"
+ ]
+ },
+ {
+ "port": "50051",
+ "protocol": [
+ "grpc"
+ ]
+ }
+ ],
+ "pubkey_node": "n94B86FddoyYsndK6N8gZwcD5xoMonptkHxmWnNqc22naS5V1pF8",
+ "server_state": "full",
+ "server_state_duration_us": "174432150738",
+ "state_accounting": {
+ "connected": {
+ "duration_us": "283465932",
+ "transitions": "2"
+ },
+ "disconnected": {
+ "duration_us": "1040136",
+ "transitions": "2"
+ },
+ "full": {
+ "duration_us": "174432150738",
+ "transitions": "1"
+ },
+ "syncing": {
+ "duration_us": "8093158",
+ "transitions": "1"
+ },
+ "tracking": {
+ "duration_us": "0",
+ "transitions": "1"
+ }
+ },
+ "time": "2025-Dec-05 11:47:07.485428 UTC",
+ "uptime": 174724,
+ "validated_ledger": {
+ "age": 4,
+ "base_fee_xrp": 1e-05,
+ "hash": "88DD7DD8994E83A178D341FB9621610CD56B4576384FCA3A962A675E9C1A4003",
+ "reserve_base_xrp": 1,
+ "reserve_inc_xrp": 0.2,
+ "seq": 100669999
+ },
+ "validation_quorum": 28
+ },
+ "status": "success"
+ }
+}
+```
+
+---
+
+## `ledger`
+
+> Retrieves info on the ledger version.
+
+The `ledger` command retrieves information about the public [ledger](https://xrpl.org/docs/concepts/ledgers).
+
+Note that the Clio server returns validated ledger data by default.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required):
+
+ * `ledger_hash` ([hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes); optional): The unique hash of the ledger version to use. (See [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers)).
+ * `ledger_index` ([ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index); optional): The [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers))
+ * `transactions` (boolean; optional): If `true`, return information on transactions in the specified ledger version. Defaults to `false`. Ignored if you did not specify a ledger version.
+ * `expand` (boolean; optional): Provide full JSON-formatted information for transaction/account information instead of only hashes. Defaults to `false`. Ignored unless you request transactions.
+ * `owner_funds` (boolean; optional): If `true`, include `owner_funds` field in the metadata of OfferCreate transactions in the response. Defaults to `false`. Ignored unless transactions are included and expand is `true`.
+ * `binary` (boolean; optional): If `true`, and `transactions` and `expand` are both also `true`, return transaction information in binary format (hexadecimal string) instead of JSON format.
+ * `diff` (boolean; optional): If `true`, returns all objects that were added, modified, or deleted as part of applying transactions in the specified ledger.
+
+### Returns
+
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing information about the ledger, including the following fields:
+
+ * `ledger` (object): The complete header data of this ledger.
+ * `ledger.account_hash` (string): Hash of all account state information in this ledger, as hex.
+ * `ledger.accountState` (array; optional): All the [account-state information](https://xrpl.org/docs/references/protocol/ledger-data) in this ledger.
+ * `ledger.close_flags` (integer): A bit-map of [flags relating to the closing of this ledger](https://xrpl.org/docs/references/protocol/ledger-data/ledger-header#close-flags).
+ * `ledger.close_time` (integer): The time this ledger was closed, in [seconds since the Ripple Epoch](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-time).
+ * `ledger.close_time_human` (string): The time this ledger was closed, in human-readable format. Always uses the UTC time zone.
+ * `ledger.close_time_resolution` (integer): Ledger close times are rounded to within this many seconds.
+ * `ledger.closed` (boolean): Whether this ledger has been closed or not.
+ * `ledger.ledger_hash` (string): Unique identifying hash of the entire ledger.
+ * `ledger.ledger_index` (string): The [Ledger Index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of this ledger, as a quoted integer.
+ * `ledger.parent_close_time` (integer): The time at which the previous ledger was closed.
+ * `ledger.parent_hash` (string): Unique identifying hash of the ledger that came immediately before this one.
+ * `ledger.total_coins` (string): Total number of XRP drops in the network, as a quoted integer. (This decreases as transaction costs destroy XRP.)
+ * `ledger.transaction_hash` (string): Hash of the transaction information included in this ledger, as hex.
+ * `ledger.transactions` (array; optional): Transactions applied in this ledger version. By default, members are the transactions' identifying [Hash](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes) strings. If the request specified `expand` as `true`, members are full representations of the transactions instead, in either JSON or binary depending on whether the request specified `binary` as `true`.
+ * `ledger_hash` (string): Unique identifying hash of the entire ledger.
+ * `ledger_index` (number): The [Ledger Index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of this ledger.
+ * `validated` (boolean; optional): If `true`, this is a validated ledger version. If omitted or set to `false`, this ledger's data is not final.
+ * `diff` (object; optional): Object containing an array of hashes that were added, modified, or deleted as part of applying transactions for the ledger.
+
+If the request specified `"owner_funds": true` and expanded transactions, the response has a field `owner_funds` in the `metaData` object of each [OfferCreate transaction](https://xrpl.org/docs/references/protocol/transactions/types/offercreate). The purpose of this field is to make it easier to track the [funding status of offers](https://xrpl.org/docs/concepts/tokens/decentralized-exchange/offers#lifecycle-of-an-offer) with each new validated ledger.
+
+ * `owner_funds` (string): Numeric amount of the `TakerGets` currency that the `Account` sending this OfferCreate transaction has after the execution of all transactions in this ledger. This does not check whether the currency amount is [frozen](https://xrpl.org/docs/concepts/tokens/fungible-tokens/freezes).
+
+If the request specified `"diff": true`, the response has an object `diff`. The fields of this object are as follows:
+
+ * `object_id` (string): The object identifier.
+ * `Hashes` (object or string): Depending on whether the request set `binary` to `true` or `false`, this field returns the contents of the object that was created, the new value of an object that was modified, or an empty string if the object was deleted.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "ledger",
+ "params": [
+ {
+ "ledger_index": "validated",
+ "transactions": false,
+ "expand": false,
+ "owner_funds": false,
+ "diff": false
+ }
+ ]
+ }'
+```
+
+### Response example
+
+```json
+{
+ "result": {
+ "ledger": {
+ "account_hash": "F16BD4873733F45AA69A22E16669701FA6382BE5465EDA7B9B77AFCFBE9BB335",
+ "close_flags": 0,
+ "close_time": 818251651,
+ "close_time_human": "2025-Dec-05 12:07:31.000000000 UTC",
+ "close_time_iso": "2025-12-05T12:07:31Z",
+ "close_time_resolution": 10,
+ "closed": true,
+ "ledger_hash": "57FAE517644B0E528D331D105D5E06071742CD7E35BE77C4F775E6FA98B38A83",
+ "ledger_index": "100670317",
+ "parent_close_time": 818251650,
+ "parent_hash": "ECEB12B2CC088D735BA64F05DF424833B9CD1821FDFE72C8608FA0895BF8DA87",
+ "total_coins": "99985745812732275",
+ "transaction_hash": "B3440C9462D83D4CD22208538DA257974A99AC132EBE976CE7B581C36F8B8825"
+ },
+ "ledger_hash": "57FAE517644B0E528D331D105D5E06071742CD7E35BE77C4F775E6FA98B38A83",
+ "ledger_index": 100670317,
+ "status": "success",
+ "validated": true
+ }
+}
+```
+
+---
+
+## `mpt_holders`
+
+> Retrieves the holders of a given MPT issuance for a given ledger.
+
+For a given `MPTokenIssuanceID` and ledger sequence, `mpt_holders` returns all holders of that [MPT](https://xrpl.org/docs/concepts/tokens/fungible-tokens/multi-purpose-tokens) and their balance. This method likely returns very large data sets, so you should expect to implement paging via the `marker` field. This API is only available using Clio, not `rippled`.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required):
+
+ * `mpt_issuance_id` (string; required): The `MPTokenIssuance` to query.
+ * `ledger_index` ([ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index); optional): The [Ledger Index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the max ledger to use, or a shortcut string to choose a ledger automatically. You must specify either `ledger_index` or `ledger_hash`. See [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers).
+ * `ledger_hash` (string; optional): A 32-byte hex string for the ledger version to use. You must specify either `ledger_index` or `ledger_hash`. See [Specifying Ledgers](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-ledgers).
+ * `marker` ([marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): Used to continue your query where it left off in paginating.
+ * `limit` (number — positive integer; optional): Specify a limit to the number of MPTs returned.
+
+### Returns
+
+ * `mpt_issuance_id` (string): The `MPTokenIssuance` queried.
+ * `mptokens` (array): An array of [MPTokens](https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/clio-methods/mpt_holders#mptoken). Includes all relevant fields in the underlying `MPToken` object.
+ * `marker` ([marker](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/markers-and-pagination); optional): Used to continue querying where we left off when paginating. Omitted if there are no more entries after this result.
+ * `limit` (number): The limit, as specified in the request.
+ * `ledger_index` ([ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index)): The index of the ledger used.
+ * `validated` (boolean): If `true`, the ledger has been validated by the consensus process and is immutable. Otherwise, the contents of the ledger are not final and may change. In Clio, this is always true as Clio stores and returns validated ledger data.
+
+#### MPToken
+
+An `MPToken` object has the following parameters:
+
+ * `account` (string): The account address of the holder who owns the `MPToken`.
+ * `flags` (number): The flags assigned to the `MPToken` object.
+ * `mpt_amount` ([string — number](https://xrpl.org/docs/references/protocol/data-types/currency-formats#string-numbers)): Specifies a positive amount of tokens currently held by the owner.
+ * `mptoken_index` (string): Key of the `MPToken` object.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "mpt_holders",
+ "params": [
+ {
+ "mpt_issuance_id": "0024D204E07DDDFBCD83B1649C07FE27FD536A3A32E6FDD8",
+ "ledger_index": "validated"
+ }
+ ]
+ }'
+```
+
+### Response example
+
+```json
+{
+ "result": {
+ "mpt_issuance_id": "0024D204E07DDDFBCD83B1649C07FE27FD536A3A32E6FDD8",
+ "limit": 50,
+ "ledger_index": 2415033,
+ "mptokens": [
+ {
+ "account": "rfyWeQpYM3vCXRHA9cMLs2ZEdZv1F1jzm9",
+ "flags": 0,
+ "mpt_amount": "200",
+ "mptoken_index": "22F99DCD55BCCF3D68DC3E4D6CF12602006A7563A6BE93FC57FD63298BCCEB13"
+ }
+ ],
+ "validated": true,
+ "status": "success"
+ },
+ "warnings": [
+ {
+ "id": 2001,
+ "message": "This is a clio server. clio only serves validated data. If you want to talk to rippled, include 'ledger_index':'current' in your request"
+ }
+ ]
+}
+```
+
+---
+
+## `version`
+
+> Retrieves API version information.
+
+The `version` command retrieves the API version information of the [Clio server](https://xrpl.org/docs/concepts/networks-and-servers/the-clio-server). For `rippled` servers, see `version` (`rippled`) instead.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required): none.
+
+### Returns
+
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing an info object as its only field.
+
+The `version` object returns some arrangement of the following fields:
+
+ * `first` (integer): Lowest supported API release.
+ * `last` (integer): Highest supported API release.
+ * `good` (integer): Default API if none specified.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "version",
+ "params": []
+ }'
+```
+
+### Response example
+
+```json
+{
+ "id": 1,
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "success",
+ "version": {
+ "first": "1.0.0",
+ "good": "1.0.0",
+ "last": "1.0.0"
+ }
+ }
+}
+```
+
+---
+
+**Utility Methods**:
+
+Use these methods to perform convenient tasks, such as ping and random number generation.
+
+## `ping`
+
+> Confirms connectivity with the server.
+
+The `ping` command returns an acknowledgement, so that clients can test the connection status and latency.
+
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required): none.
+
+### Returns
+
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing no fields. The client can measure the round-trip time from request to response as latency.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "ping",
+ "params": []
+ }'
+```
+
+### Response example
+
+```json
+{
+ "id": 1,
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "success"
+ }
+}
+```
+
+---
+
+## `random`
+
+> Generates a random number.
+
+The `random` command provides a random number to be used as a source of entropy for random number generation by clients.
+
+### Parameters
+
+ * `id` (integer; required): a request ID (example: 1).
+ * `jsonrpc` (string; required): a JSON-RPC spec used (example: 2.0).
+ * `method` (string; required): a method used for the request.
+ * `params` (array; required): none.
+
+### Returns
+
+The response follows the [standard format](https://xrpl.org/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following field:
+
+ * `random` (string): Random 256-bit hex value.
+
+### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "random",
+ "params": []
+ }'
+```
+
+### Response example
+
+```json
+{
+ "id": 1,
+ "jsonrpc": "2.0",
+ "result": {
+ "random": "3060417EAEBDB220E2CBED2B4BCBAEDD805D8A1A8D7C405A868F11ABB7249B2A",
+ "status": "success"
+ }
+}
+```
diff --git a/pages/rpc-service/chains/chains-list.mdx b/pages/rpc-service/chains/chains-list.mdx
index c2d63a43..538b7a57 100644
--- a/pages/rpc-service/chains/chains-list.mdx
+++ b/pages/rpc-service/chains/chains-list.mdx
@@ -31,8 +31,8 @@ Find the chain you require and go to its docs section by clicking it.
| [Avail](/rpc-service/chains/chains-list/#avail) | [Electroneum](/rpc-service/chains/chains-list/#electroneum) | [Horizen EON](/rpc-service/chains/chains-list/#horizen-eon) | [Moonbeam](/rpc-service/chains/chains-list/#moonbeam) | [Somnia](/rpc-service/chains/chains-list/#somnia) | [XDC](/rpc-service/chains/chains-list/#xdc) |
| [Avalanche](/rpc-service/chains/chains-list/#avalanche) | [Ethereum](/rpc-service/chains/chains-list/#ethereum) | [Iota](/rpc-service/chains/chains-list/#iota) | [Movement](/rpc-service/chains/chains-list/#movement) | [Sonic](/rpc-service/chains/chains-list/#sonic) | [X Layer](/rpc-service/chains/chains-list/#x-layer) |
| [B2 Network](/rpc-service/chains/chains-list/#b2-network) | [Ethereum Beacon](/rpc-service/chains/chains-list/#eth-beacon) | [Iota EVM](/rpc-service/chains/chains-list/#iota-evm) | [NEAR](/rpc-service/chains/chains-list/#near) | [Stellar](/rpc-service/chains/chains-list/#stellar) | [Xphere](/rpc-service/chains/chains-list/#xphere) |
-| [Bahamut](/rpc-service/chains/chains-list/#bahamut) | [Etherlink](/rpc-service/chains/chains-list/#etherlink) | [IoTeX](/rpc-service/chains/chains-list/#iotex) | [Nervos](/rpc-service/chains/chains-list/#nervos) | [Story](/rpc-service/chains/chains-list/#story) | [zkSync Era](/rpc-service/chains/chains-list/#zksync-era) |
-| [Base](/rpc-service/chains/chains-list/#base) | [Fantom](/rpc-service/chains/chains-list/#fantom) | [Kaia](/rpc-service/chains/chains-list/#kaia) | [Neura](/rpc-service/chains/chains-list/#neura) | [Sui](/rpc-service/chains/chains-list/#sui) | |
+| [Bahamut](/rpc-service/chains/chains-list/#bahamut) | [Etherlink](/rpc-service/chains/chains-list/#etherlink) | [IoTeX](/rpc-service/chains/chains-list/#iotex) | [Nervos](/rpc-service/chains/chains-list/#nervos) | [Story](/rpc-service/chains/chains-list/#story) | [XRP](/rpc-service/chains/chains-list/#xrp) |
+| [Base](/rpc-service/chains/chains-list/#base) | [Fantom](/rpc-service/chains/chains-list/#fantom) | [Kaia](/rpc-service/chains/chains-list/#kaia) | [Neura](/rpc-service/chains/chains-list/#neura) | [Sui](/rpc-service/chains/chains-list/#sui) | [zkSync Era](/rpc-service/chains/chains-list/#zksync-era) |
| [Bitcoin](/rpc-service/chains/chains-list/#bitcoin) | [Filecoin](/rpc-service/chains/chains-list/#filecoin) | [Kava](/rpc-service/chains/chains-list/#kava) | [Optimism](/rpc-service/chains/chains-list/#optimism) | [Swell](/rpc-service/chains/chains-list/#swell) | |
| [Bitlayer](/rpc-service/chains/chains-list/#bitlayer) | [Flare](/rpc-service/chains/chains-list/#flare) | [Kinto](/rpc-service/chains/chains-list/#kinto) | [Polkadot](/rpc-service/chains/chains-list/#polkadot) | [Syscoin](/rpc-service/chains/chains-list/#syscoin) | |
| [Blast](/rpc-service/chains/chains-list/#blast) | [Fuel](/rpc-service/chains/chains-list/#fuel) | [Kusama](/rpc-service/chains/chains-list/#kusama) | [Polygon](/rpc-service/chains/chains-list/#polygon) | [TAC](/rpc-service/chains/chains-list/#tac) | |
@@ -12128,6 +12128,93 @@ def test_block_number(self):
---
+## XRP
+
+
+Available for [Premium](/rpc-service/service-plans/#service-plans-comparison) users only.
+
+
+> XRP API is available on [Web3 API platform](https://www.ankr.com/rpc/xrp).
+
+The XRP Ledger (XRPL) is a decentralized blockchain optimized for fast, low-cost payments and asset transfers. It uses a federated consensus algorithm in which a trusted set of validators propose and agree on transactions; once 80%+ reach consensus, a new ledger is finalized in 3–5 seconds with deterministic finality. XRPL supports native issued assets, a built-in DEX, escrows, payment channels, and multi-signing.
+
+**XRPL Ecosystem Overview**
+
+ * **Core Servers**: The network is powered by rippled, the open-source server responsible for ledger synchronization, transaction processing, and consensus. Clio servers provide scalable, API-focused access without participating in the P2P consensus network.
+ * **Client Libraries**: SDKs streamline integration by wrapping XRPL APIs and performing secure local transaction signing.
+ * **Middleware**: Services built on XRPL APIs provide indexed data, higher-level abstractions, or custom interfaces, typically running continuously with their own storage layers.
+ * **Apps and Services**: Wallets, exchanges, token issuers, marketplaces, payment processors, and DEX interfaces form the user-facing layer, enabling transfers, trading, and broader financial use cases.
+
+### Networks
+
+ * Mainnet (`HTTPS` and `WSS`)
+
+### API methods
+
+For XRP, we support blockchain interaction via all the [applicable methods](/rpc-service/chains/chains-api/xrp/) except for those listed as unsupported.
+
+#### Unsupported
+
+
+ This section contains a list of methods we don't support for _Premium_ service plan.
+
+
+
+ If you require any of the methods from the list, contact our Sales (`sales@ankr.com`) about moving to the _Enterprise_ service plan that can provide the services tailored to your specific needs.
+
+
+None.
+
+### API querying
+
+#### Request example
+
+```shell
+curl 'https://rpc.ankr.com/xrp_mainnet/{your_token}' \
+-d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "account_channels",
+ "params": [
+ {
+ "account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
+ "destination_account": "ra5nK24KXen9AHvsdFTKHSANinZseWnPcX",
+ "ledger_index": "validated"
+ }
+ ]
+ }'
+```
+
+#### Response example
+
+```json
+{
+ "id": 1,
+ "jsonrpc": "2.0",
+ "result": {
+ "account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
+ "channels": [
+ {
+ "account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
+ "amount": "1000",
+ "balance": "0",
+ "channel_id": "C7F634794B79DB40E87179A9D1BF05D05797AE7E92DF8E93FD6656E8C4BE3AE7",
+ "destination_account": "ra5nK24KXen9AHvsdFTKHSANinZseWnPcX",
+ "public_key": "aBR7mdD75Ycs8DRhMgQ4EMUEmBArF8SEh1hfjrT2V9DQTLNbJVqw",
+ "public_key_hex": "03CFD18E689434F032A4E84C63E2A3A6472D684EAF4FD52CA67742F3E24BAE81B2",
+ "settle_delay": 60
+ }
+ ],
+ "ledger_hash": "42C4F4E81710B015B3BA2A81E357E30E261F58964A6AB6C012734FADB67AB40D",
+ "ledger_index": 99672209,
+ "status": "success",
+ "validated": true
+ }
+}
+```
+
+---
+
## zkSync Era