XRPL.to
GET /testnet/health
GET

/v1/testnet/health

Both collectors' head ledger against the network, and whether that is current

AuthNone — works without a key

Request

GEThttps://api.xrpl.to/v1/testnet/health
curl 'https://api.xrpl.to/v1/testnet/health'

Response

200Example response715 ms · just now · 0.4 KB · 23 lines
https://api.xrpl.to/v1/testnet/health
{
  "success": true,
  "took": 714,
  "ok": true,
  "validated": 21467353,
  "node": {
    "state": "full",
    "networkId": 1,
    "ledgers": "13075065-21467353"
  },
  "stages": {
    "tokens": {
      "ledger": 21467353,
      "at": 1791767076216,
      "lag": 0
    },
    "nfts": {
      "ledger": 21467353,
      "at": 1791767076234,
      "lag": 0
    }
  }
}
Shapeas documented
{
  ok,
  validated,
  node: { state, networkId, ledgers },
  stages: {
    tokens: { ledger, at, lag },
    nfts: { ledger, at, lag }
  }
}

What it does

Both collectors' head ledger against the network, and whether that is current

Start at GET /v1/testnet/fixtures: it names live accounts, a busy token, an NFT with offers and one of every ledger object that xrpl.to keeps alive on Testnet, plus a real transaction of every type. The busiest token gains holders every hour, so its GET /v1/testnet/tokens/{md5}/holders is the place to test paginating a long list. Testnet resets without warning; the data is rebuilt from the chain within minutes, and only objects touched since count. Open the Testnet sandbox →
OpenAPI
PrevGET/testnet/fixturesNextGET/testnet/tokens