Last updated



The fetch_info command returns information about objects that this server is currently fetching from the network, and how many peers have that information. It can also be used to reset current fetches.

The fetch_info method is an admin method that cannot be run by unprivileged users.

Request Format

An example of the request format:

  1. WebSocket
  3. Commandline
    "id": 91,
    "command": "fetch_info",
    "clear": false

The request includes the following parameters:

clearBooleanIf true, reset current fetches. Otherwise, only get status of fetches in progress.

Response Format

An example of a successful response:

  2. Commandline
   "result" : {
      "info" : {
         "348928" : {
            "hash" : "C26D432B06F84861BCACD7942EDC3FE0B2E1DEB966A9E516A0FD275A375C2010",
            "have_header" : true,
            "have_state" : false,
            "have_transactions" : true,
            "needed_state_hashes" : [
            "peers" : 2,
            "timeouts" : 0
      "status" : "success"

The response follows the standard format, with a successful result containing the following fields:

infoObjectMap of objects being fetched and the status of that object being fetched. A ledger being fetched may be identified by its ledger index; ledgers and other objects being fetched may also be identified by their hashes.

The fields describing a fetch in progress are subject to change without notice. The following fields may be included:

hashStringThe hash of the item being fetched.
have_headerBooleanFor a ledger, whether this server has already obtained the ledger's header section.
have_transactionsBooleanFor a ledger, whether this server has already obtained the transaction section of that ledger.
needed_state_hashesArray of (Hash) StringsThe hash values of state objects still needed from this item. If more than 16 are needed, the response contains only the first 16.
peersNumberThe number of peers who have this item available.
timeoutsNumberThe number of times that fetching this item has resulted in a timeout (2.5 seconds).

Possible Errors