Skip to main content
Asks the server for machine-readable information about the rippled server’s current state. The response is almost the same as server_info, but uses units that are easier to process. Clio forwards this call to the rippled it is connected to. This method will use 20 Compute Units.

Reference: Here

Parameters

None

Returns

  • state (object) Server state information: build_version, complete_ledgers (the range held by rippled, not the Clio full-history range), io_latency_ms, jq_trans_overflow, last_close (converge_time in milliseconds and proposers), load_base, load_factor and the related load_factor_* fields, network_id, peers, ports, pubkey_node, server_state, server_state_duration_us, state_accounting, time, uptime, validated_ledger (base_fee, close_time, hash, reserve_base, reserve_inc, seq), validation_quorum and validator_list_expires.
Over WebSocket, send {"id":1,"command":"server_state"} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.
The example above is trimmed; ports and state_accounting are shortened and admin-only sections are omitted.