Skip to main content
POST
Withdrawal & Consolidation Request Fees

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

range and type_filter are optional in this request body

chain
enum<string>
default:mainnet
required

The Ethereum chain to query.

Available options:
mainnet,
hoodi
range
Unix Timestamp · object

Specify a time range using either Unix timestamps or epoch numbers. If left null, the API will query the entire available history of the selected validators.

type_filter
enum<string>[] | null

Filter results to one or more request contracts. If omitted, both contracts are returned and a block that saw activity on both contributes one entry per contract.

Which EIP-7685 execution-layer request contract the fee applies to.

  • withdrawal: the EIP-7002 withdrawal request contract (0x00000961Ef480Eb55e80D19ad83579A64c007002), used for execution-layer triggered partial withdrawals and full exits.
  • consolidation: the EIP-7251 consolidation contract (0x0000BBdDc7CE488642fb579F8B00f3a590007251), used for both consolidations and compounding switches.

Deposits (EIP-6110) are not listed: the deposit contract charges no request fee.

Available options:
withdrawal,
consolidation
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 fees observed per execution layer block for EIP-7002 and EIP-7251 requests, most recent block first.

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