---
title: "Validator"
method: POST
path: "/api/v2/ethereum/validators"
tags: ["General"]
---

# Validator

`POST /api/v2/ethereum/validators`

Returns basic information about a set of validators at the current epoch. 

Data returned by the endpoint is based on the latest completed epoch of the beacon chain (not finalized).

## Request body

- object
  - `chain` 'mainnet' | 'hoodi' — The Ethereum chain to query.
  - `cursor` string — Cursor value for pagination. See our [pagination guide](/api/pagination) for more details.
  - `page_size` integer — The number of items to return per page.
  - `validator` union, 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.
    - ValidatorsByIdentifiers
      - `validator_identifiers` ValidatorIndexPublicKey[], required — An array containing either validator indices or public keys. Index and public key can be mixed in the same array. Subscribed users (Hobbyist, Business, and Scale tiers) can include up to 100 entries; free trial users and legacy subscription users (Sapphire, Emerald, Diamond) are limited to 20.
        - union
          - integer — Validator Index
          - string — Public key of a validator
    - ValidatorsByDashboard
      - `dashboard_id` integer, required — beaconcha.in dashboard ID. You can find your dashboard ID in the URL of your dashboard page on beaconcha.in (e.g., https://beaconcha.in/dashboard/12345).
      - `group_id` integer, nullable — Optional beaconcha.in dashboard group ID. If no group ID is provided, all validators in the dashboard are considered.
    - ValidatorsByDeposit
      - `deposit_address` string, required — A standard Ethereum address (20-byte hex string with 0x prefix).
    - ValidatorsByWithdrawal
      - `withdrawal` string, required — Either an execution layer address (20-byte hex string with 0x prefix) or a full 32-byte withdrawal credential.
    - ValidatorsByEntity — Select validators by their assigned entity (e.g., staking provider) and optionally a sub-entity. Entity and sub-entity names are matched exactly and are case-sensitive.
      - `entity` string, required — The name of the entity to filter validators by (e.g., "Lido", "Coinbase"). Matching is case-sensitive; use the exact name as returned by the entities overview endpoint.
      - `sub_entity` string — Optional sub-entity name to further filter validators within the entity. Matching is case-sensitive; use the exact name as returned by the sub-entities overview endpoint.

## Response `200`

Successful response.

- object — Response containing basic information about the validator.
  - `data` ValidatorOverviewData[], required
    - `validator` Validator, required
      - `index` integer — Validator Index
      - `public_key` string — Public key of a validator
    - `slashed` boolean, required
    - `status` 'pending_initialized' | 'pending_queued' | 'active_ongoing' | 'active_exiting' | 'active_slashed' | 'exited_unslashed' | 'exited_slashed' | 'withdrawal_possible' | 'withdrawal_done' | 'unknown', required
    - `online` boolean, nullable
    - `withdrawal_credentials` WithdrawalCredential, required
      - `type` 'bls' | 'execution_address', required — Specifies whether the withdrawal credential is a BLS withdrawal credential or an execution address withdrawal credential.
      - `prefix` '0x00' | '0x01' | '0x02', required — Hexadecimal prefix indicating the type of withdrawal credential: - "0x00": BLS withdrawal credential - "0x01": Execution address withdrawal credential - "0x02": Execution address withdrawal credential with consolidation support (Electra Fork) Credentials can be upgraded in one direction only: - From "0x00" (BLS) to "0x01" (execution address) - From "0x01" to "0x02" (consolidation-enabled execution address) Downgrades are not permitted.
      - `credential` string, required — A full 32-byte withdrawal credential represented as a hex string with 0x prefix.
      - `address` string — A standard Ethereum address (20-byte hex string with 0x prefix).
    - `life_cycle_epochs` LifeCycleEpochs, required — Epochs marking significant lifecycle events for the validator. Unlike the official spec, null is returned for events that have not yet occurred, instead of using "FAR_FUTURE_EPOCH" (max uint64), to simplify client handling.
      - `activation_eligibility` integer, nullable — The epoch at which the validator became eligible for activation by meeting the activation criteria.
      - `activation` integer, nullable — The epoch at which the validator was activated and started participating in the consensus process & earning rewards.
      - `exit` integer, nullable — The epoch at which the validator exited and stopped participating in the consensus process.
      - `withdrawable` integer, nullable — The epoch at which the validator became eligible for withdrawal after they have exited.
    - `balances` ValidatorBalancesHead, required — The balances object provides detailed information about a validator's balances at the head of the chain. Balances are measured immediately before the first slot of the head chain. For example, a balance reported for epoch 10 reflects the state after the final slot of epoch 9 and before the first slot of epoch 10. For more details about balances, see: https://eth2book.info/latest/part2/incentives/balances/
      - `current` string, required — Amount in wei (1 ETH = 10^18 wei)
      - `effective` string, required — Amount in wei (1 ETH = 10^18 wei)
    - `finality` 'not_finalized', required — Indicates the finality status of the data provided. - Finalized data cannot be changed without slashing at least one-third of all validators, providing strong economic guarantees. - Data marked as not_finalized does not have this guarantee and may still change.
  - `paging` Paging
    - `next_cursor` string — Cursor to the next page of results. See our [pagination guide](/api/pagination) for more details. If empty, there are no more pages to fetch.
  - `range` ResultRange, required — The range of data covered by the results, specified in slots, epochs, and Unix timestamps.
    - `slot` SlotRange, required
      - `start` integer, required — Slot by number.
      - `end` integer, required — Slot by number.
    - `epoch` EpochRange, required
      - `start` integer, required
      - `end` integer, required
    - `timestamp` TimeRange, required
      - `start` integer, required
      - `end` integer, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `405` — Method Not Allowed
- `429` — Rate Limit Exceeded
- `500` — Internal Server Error
- `default` — An unexpected error response.

---

[API](https://skmtc.dev/beaconcha/apis/external-service-api.md) · [All operations](https://skmtc.dev/beaconcha/apis/external-service-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/beaconcha/external-service-api/revisions/ad26ad970b4e/schema)