Skip to main content
POST
Staking Queues History

Authorizations

Authorization
string
header
required

Authorization header with value: Bearer YOUR_TOKEN. Refer to the API Keys section to create your API key.

Body

application/json
chain
enum<string>
default:mainnet

The Ethereum chain to query.

Available options:
mainnet,
hoodi
range
Unix Timestamp · object

Time window to query, given as Unix timestamps, epoch numbers, or slot numbers (inclusive). If omitted or null, the last 30 days are returned. The newest epochs may not yet be finalized — each snapshot carries a finality field. Results are paginated via cursor/page_size.

Example:
granularity
enum<string>
default:daily

Resolution of the returned time series.

  • daily — one entry per UTC day, taken at the first epoch that started on that day.
  • epoch — one entry per epoch (225 epochs per day on mainnet).

The two resolutions reach back different distances, because the queue snapshots were recomputed from archived beacon state at daily resolution only.

daily covers the whole recorded range, which begins at the Pectra fork — the pending deposit, consolidation and partial-withdrawal queues are Pectra state fields, so no queue history exists before it.

epoch is served only from the point where every consecutive epoch was recorded correctly, which is a shorter window ending at the chain head.

A range reaching below either floor is served from that floor, and a range entirely below it returns an empty series rather than an error. Read range on the response to see the span actually served.

Available options:
daily,
epoch
Example:

"daily"

cursor
string
default:""

Cursor value for pagination. See our pagination guide for more details.

page_size
integer
default:10

The number of items to return per page.

Required range: 1 <= x <= 10

Response

Successful response.

Response containing the staking queues history with the resolved range.

data
object[]
required
range
object
required

The time span actually covered by the returned results — from the first to the last matching data point — specified in slots, epochs, and Unix timestamps.

This reflects the data that was found, not the range that was queried. When no data is found, it falls back to the requested range, or to the full available history if no range was given.

For arbitrary (custom) time-range queries the queried range is expanded outward to whole UTC days, so the covered range may be wider than requested. As stated above, the reported range still reflects the data that was actually found — a touched UTC day with no data for the selected validators will not extend it.

paging
object