Skip to main content
POST
Proposal Timing Aggregate
Experimental. This endpoint returns data only on chains past the Glamsterdam hard fork. Hoodi forks first; mainnet returns 404 until it forks. The request and response may change before the mainnet release. See Glamsterdam API.

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
validator
Indices/Pubkeys · object
required

Free selectors available to all users:

  • validator_identifiers: One or more validator indices or public keys to filter by.
  • dashboard_id: Your beaconcha.in dashboard ID (requires a free account).

Premium selectors for Scale & Enterprise plans (https://beaconcha.in/pricing):

  • withdrawal: The validator's withdrawal credential or the Ethereum wallet address used for withdrawals.
  • deposit_address: The Ethereum wallet address used for the validator's deposit.
  • entity: The name of the assigned entity (e.g., "Lido", "Coinbase"). Optionally include sub_entity for more specific filtering. Matching is case-sensitive.

Note: The set of validators matched by deposit_address and withdrawal selectors is updated once per epoch (~6.4 minutes). Newly deposited validators may take up to one epoch to appear in query results.

Note: The set of validators matched by entity selector is updated once per day.

range
Fixed Window · object
required
chain
enum<string>
default:mainnet

The Ethereum chain to query.

Available options:
mainnet,
hoodi

Response

Successful response.

Response containing when the proposals of the validators reached one beaconcha.in node over the evaluation window.

data
object
required

Proposal timing of the validators over the evaluation window. The window ends at the last finalized slot and starts no earlier than the Glamsterdam hard fork.

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 the response is 200 but no data is found, it falls back to the requested range, or to the full available history if no range was given. Some endpoints answer 404 instead when no data is found.

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.