Skip to main content
Asks the server for a human-readable version of various information about the server being queried. Our XRPL endpoint answers from Clio, so the response describes the Clio server plus the rippled it is connected to. This method will use 20 Compute Units.

Reference: Here

Parameters

  • counters (boolean, optional) If true, return metrics about the job queue, ledger store, and API method activity. The default is false.

Returns

  • info (object) Server information. Clio returns complete_ledgers (the full-history range available), load_factor, time, uptime, clio_version, libxrpl_version, rippled_version, network_id, validation_quorum, cache (Clio’s ledger cache state) and validated_ledger (age, hash, seq, base_fee_xrp, reserve_base_xrp, reserve_inc_xrp).
  • validated (boolean) If true, the information comes from a validated ledger version.
Over WebSocket, send {"id":1,"command":"server_info"} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.
To see the rippled server’s own server_info (build version, peers, server state, state accounting) send "ledger_index": "current" in the request; Clio then forwards the call to rippled.