Get Ledgers Within Range
POST
Retrieves the list of Ledgers within a specific range.
Path Parameters
chainstringrequired
Parameter specifying the target chain to query.networkstringrequired
Parameter specifying the network of the target chain.Request Body
fromLedgerstringrequired
Parameter specifying the starting ledger for the query. You can enter one of the following formats:- **ledger index**: Enter ledger number as a decimal string
- **ledger hash**: 64-character hexadecimal string (excluding 0x prefix)
- **ledger tag**: Enter "earliest" or "latest" (oldest or most recent ledger)
- If provided without toLedger, results are queried from this ledger to the latest ledger.
- fromLedger value cannot be greater than toLedger value.
- If fromLedger and toLedger have the same value, only that ledger is queried.
- "latest" for fromLedger is only allowed when toLedger is "latest".
toLedgerstringrequired
Parameter specifying the ending ledger for the query. You can enter one of the following formats:- **ledger index**: Enter ledger number as a decimal string
- **ledger hash**: 64-character hexadecimal string (excluding 0x prefix)
- **ledger tag**: Enter "earliest" or "latest" (oldest or most recent ledger)
- If provided without fromLedger, results are queried from genesis ledger to this ledger.
- toLedger value cannot be less than fromLedger value.
- If fromLedger and toLedger have the same value, only that ledger is queried.
- "earliest" for toLedger is only allowed when fromLedger is "earliest".
fromDatestring
Parameter specifying the start date for the query. Date must follow ISO 8601 format (YYYY-MM-DDThh:mm:ss{time zone}) including seconds.Notes:- If provided without toDate, results are queried from this date to the latest block.
- fromDate value must be equal to or earlier than toDate value.
- If fromDate and toDate have the same value, only blocks from that date are queried.
- This field cannot be used together with fromBlock and toBlock.
- If
fromDateandtoDateare not provided, the API queries data from the latest 30 days.
toDatestring
Parameter specifying the end date for the query. Date must follow ISO 8601 format (YYYY-MM-DDThh:mm:ss{time zone}) including seconds.Notes:- If provided without fromDate, results are queried from genesis block to this date.
- toDate value must be equal to or later than fromDate value.
- If fromDate and toDate have the same value, only blocks from that date are queried.
- This field cannot be used together with fromBlock and toBlock.
- If
fromDateandtoDateare not provided, the API queries data from the latest 30 days.
pageinteger
The page parameter specifies the data page to query. It accepts values up to 100; for pages exceeding 100, use the cursor pagination method.The page and cursor parameters cannot be used together. If both page and cursor are empty, cursor pagination is used.rppinteger
rpp stands for results per page and specifies the page size. You can specify a number greater than 0 and up to 100.cursorstring
The cursor parameter supports pagination and data navigation between pages. Provide the cursor value from the previous page in the next request to load the next page of data.The page and cursor parameters cannot be used together. If both page and cursor are empty, cursor pagination is used.withCountboolean
Parameter specifying whether to include the count field in the response. The count field indicates the total number of requested data items. When set to true, the count field is included and response speed may be slower.Responses
pageinteger
Field representing the page number specified in the page parameter. This field is only included in the response when a value greater than 0 is specified for the page parameter.rppinteger
Field representing the number of results per page specified in the rpp parameter.cursorstring
A field for cursor pagination. This value must be provided in the next request to load the next page of data.countinteger
Field representing the total count of requested data. This field is only included in the response when true is set for the withCount parameter.Field representing the actual range applied to the query. The same kind of values used in the request's range parameters are returned. A Date-based request returns fromDate and toDate, a Block-based request returns fromBlock and toBlock, and a Ledger-based request returns fromLedger and toLedger; different kinds are never mixed in a single response. When all range parameters are omitted, a default window of the last 30 days is applied and fromDate, toDate are returned. Block and Ledger values are always returned as heights (numbers), even if a hash or tag (latest, earliest) was provided in the request.
fromDatestring
Field representing the start of the query range in Date mode. Returned in ISO 8601 format.toDatestring
Field representing the end of the query range in Date mode. Returned in ISO 8601 format.fromBlockinteger
Field representing the start block height of the query range in Block mode.toBlockinteger
Field representing the end block height of the query range in Block mode.fromLedgerinteger
Field representing the start ledger index of the query range in Ledger mode.toLedgerinteger
Field representing the end ledger index of the query range in Ledger mode.ledgerHashstringrequired
Unique identifier of the current ledger, a 256-bit (64-digit hexadecimal) cryptographic hash. Used for ledger data integrity verification and identification.ledgerIndexintegerrequired
Integer value indicating the creation order of the ledger, used to identify its position (sequence number) on the network.ledgerTimestampintegerrequired
The ledger's close time converted to a Unix timestamp. The close time recorded in the ledger header is expressed in seconds since the Ripple Epoch (January 1, 2000 00:00 UTC), which differs from the Unix Epoch (January 1, 1970 00:00 UTC) by 946,684,800 seconds. Thus ledgerTimestamp is the recorded close time plus 946,684,800 seconds.parentLedgerHashstringrequired
256-bit (64-digit hexadecimal) hash identifying the ledger immediately preceding the current ledger. References the previous ledger's hash to maintain chain integrity.accountHashstringrequired
256-bit (64-digit hexadecimal) hash summarizing all account state information recorded in the ledger. Used to verify consistency and integrity of account data.totalCoinsstringrequired
Total quantity of XRP (in XRP units) owned by accounts recorded in the ledger. This value excludes XRP burned as transaction fees. The actual circulating XRP may be lower than this value because some accounts may be in a "black hole" state (accounts with no key).transactionHashstringrequired
256-bit (64-digit hexadecimal) Merkle tree root hash summarizing all transaction data included in the ledger. Used for transaction history integrity verification.transactionCountintegerrequired
Integer value indicating the total number of transactions included in the ledger. Used to assess the scale and activity of ledger transaction history.transactionsarrayrequired
Array of transaction hashes included in the ledger. Each hash is a 256-bit (64-digit hexadecimal) cryptographic hash uniquely identifying a transaction, used for transaction data integrity and identification.codestringrequired
Code identifying the cause of the failed request.messagestringrequired
Detailed message including the name and value of the invalid parameter.{"code": "MISSING_REQUIRED_PARAMETER","message": "Missing required parameter: { PARAMETER_NAME }"}
cURL
curl -X POST 'https://web3.nodit.io/v1/xrpl/mainnet/blockchain/getLedgersWithinRange' \-H 'Content-Type: application/json' \-H 'X-API-KEY: nodit-demo' \-d '{"fromDate": "2025-01-01T00:00:00+00:00","toDate": "2025-01-31T00:00:00+00:00","page": 1,"rpp": 10}'