Skip to main content
POST
Validator Queue Consolidation Details

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.

chain
enum<string>
default:mainnet

The Ethereum chain to query.

Available options:
mainnet,
hoodi
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
status_filter
enum<string> | null

Filter results to a single consolidation status. If not specified, results include all statuses.

  • pending: recorded on the execution layer; not yet picked up by the consensus layer.
  • queued: included by the consensus layer; the source validator is exiting.
  • completed: balance sweep finalized.
  • rejected: rejected at consensus-layer inclusion.
Available options:
pending,
queued,
completed,
rejected
Example:

"rejected"

role_filter
enum<string> | null

Restrict results to the role the selected validators play in the consolidation. If not specified, a validator matches in either role.

  • source: only requests where a selected validator is the source — the validator that exits and whose balance is merged away.
  • target: only requests where a selected validator is the target — the validator that stays active and receives the balance.

A validator is usually only ever one or the other, because a source validator exits as part of the consolidation. Use this filter when you want that guarantee rather than checking source_validator and target_validator yourself, or to avoid paging through the other role's entries for a validator that has served in both.

Available options:
source,
target
Example:

"target"

Response

Successful response.

data
object[]
required
paging
object
required