Skip to main content
GET
/
api
/
v1
/
validator
/
{indexOrPubkey}
/
attestations
Validator attestations history
curl --request GET \
  --url 'https://beaconcha.in/api/v1/validator/{indexOrPubkey}/attestations?apikey='
{
"status": "OK",
"data": [
{
"attesterslot": 12779525,
"committeeindex": 0,
"epoch": 399360,
"inclusionslot": 12779526,
"status": 1,
"validatorindex": 20,
"week": 253,
"week_start": "2025-10-07T12:00:23Z",
"week_end": "2025-10-14T12:00:23Z"
}
]
}

Authorizations

apikey
string
query
required

Path Parameters

indexOrPubkey
string
required

Comma-separated validator indices and/or public keys (maximum 100 items by default). 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.
Example:

"1,2,3"

Query Parameters

startEpoch
integer

Start epoch for the query window. Defaults to latest - 99. Must be within [latest-99, latest] and less than or equal to endEpoch when provided.

Required range: x >= 0
Example:

399260

endEpoch
integer

End epoch for the query window. Defaults to latest. Must be within [startEpoch, latest] when provided.

Required range: x >= 0
Example:

399359

slim
boolean
default:false

When true, return a slimmed response that excludes week, week_start, week_end, and committeeindex fields from each item.

Example:

true

Response

Matching attestations were retrieved successfully. The data array contains one entry per scheduled attestation for the specified validators within the requested epoch window. Items are sorted by epoch (descending) and then by validator index (ascending).

Standard success envelope used by all API endpoints.

status
enum<string>

HTTP-independent status of the API operation. For successful responses this is always "OK".

Available options:
OK
data
object[]

Response payload specific to the endpoint.