---
title: "Get beacon-chain status for a batch of validator pubkeys"
method: POST
path: "/v1/validators/{network}/status"
tags: ["Validators"]
---

# Get beacon-chain status for a batch of validator pubkeys

`POST /v1/validators/{network}/status`

Proxies beaconcha.in /api/v1/validator/{pubkeys} server-side so the Launchpad ships no beaconcha.in API key in its bundle. Upstream field names (pubkey, withdrawalcredentials, status, validatorindex) are preserved.

## Path parameters

- `network` string, required

## Request body

- ValidatorsRequestDto
  - `pubkeys` string[], required — Validator BLS pubkeys (96 hex chars, 0x prefix optional). Max 1000 per request.

## Response `200`

Validator status rows (beaconcha.in shape)

- ValidatorStatusResponse
  - `data` ValidatorStatusDto[], required — Validator status rows for the requested pubkeys (upstream beaconcha.in shape)
    - `pubkey` string, required — 0x-prefixed validator BLS pubkey
    - `withdrawalcredentials` string, required — Withdrawal credentials (upstream field name)
    - `status` string, required — Validator status (e.g. active_online, exited)
    - `validatorindex` number, required — Validator index

## Other responses

- `400` — Unsupported network or malformed pubkeys
- `429` — Rate limited (either this API or the upstream)
- `500` — An unknown error occurred
- `502` — Upstream beaconcha.in request failed

---

[API](https://skmtc.net/obol/apis/obol-api.md) · [All operations](https://skmtc.net/obol/apis/obol-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/obol/obol-api/revisions/707a88e0b355/schema)