Validators overview (POST)
Retrieve validator information by index or public key using a JSON request body. Use this endpoint when the list of identifiers is too long for the GET path parameter. Provide up to 100 identifiers (higher limits may apply to authenticated premium users) as a comma-separated string in the indicesOrPubkey field. Each identifier must be either a validator index (base-10 integer) or a 48-byte BLS public key as 0x-prefixed hex (96 hex characters after 0x) or without the 0x prefix.
Authorizations
Body
Comma-separated list of validator indices and/or public keys to query (maximum 100 items by default).
Validator lookup request specifying validator indices and/or public keys.
Comma-separated list (no spaces) of validator identifiers. Each identifier must be either:
- A validator index as a base-10 integer (for example, 652648)
- A BLS public key as a 96-hex-character string with or without the 0x prefix (case-insensitive)
Resolution and limits:
- The server resolves public keys to validator indices before querying data.
- The total number of identifiers must not exceed the server-enforced limit (default 100).
- Identifiers that cannot be parsed or resolved result in HTTP 400.
"1,2,3"
Response
Matching validators were retrieved successfully. The data field contains either a single validator object (when one identifier is provided/resolved) or an array of validator objects (when multiple identifiers are provided/resolved).
Standard success envelope used by all API endpoints.
HTTP-independent status of the API operation. For successful responses this is always "OK".
OK State and metadata for a single validator, including status, balances, epochs, and withdrawal summary.
- Multiple validators · object[]
- Single validator · object

