XRPL.to
GET /ledger
GET

/v1/ledger

Current validated ledger info

AuthNone — works without a key

Request

GEThttps://api.xrpl.to/v1/ledger
curl 'https://api.xrpl.to/v1/ledger'

Response

200Example response4 ms · just now · 0.4 KB · 13 lines
https://api.xrpl.to/v1/ledger
{
  "success": true,
  "ledger_index": 107595344,
  "ledger_hash": "E277C41AE47CDCBE4E53C9BE2F58F4984A76DF64D503854AB6B87109A7691201",
  "close_time": 1791767050000,
  "close_time_human": "2026-10-12T01:04:10.000Z",
  "parent_hash": "B9948CDE6DBBA5EF5597CC94F5ECBF55374E6F2DAC1C9B9675AD62A47928F69C",
  "total_coins": "99985592368908526",
  "txn_count": 0,
  "validated": true,
  "reserve_base_drops": 1000000,
  "reserve_inc_drops": 200000
}
Shapeas documented
{
  ledger_index,
  ledger_hash,
  close_time (ms),
  close_time_human,
  parent_hash,
  total_coins,
  txn_count,
  validated,
  reserve_base_drops,
  reserve_inc_drops
}

What it does

Current validated ledger info

Notes
reserve_base_drops / reserve_inc_drops are the validator-voted account reserve settings, in drops. reserve_inc_drops is the Fee an AccountDelete or AMMCreate MUST carry (one owner reserve) — read it here, never hardcode it: validators can vote the increment, and a stale constant means telINSUF_FEE_P if it rose or a silent overpayment if it fell.
Transaction hashes are 64-character hex. Submit relays whatever you signed: the type list below is what the ledger accepts today. Every transaction type you can submit →
OpenAPI
NextGET/ledger/{index}