Self Report Validator Entity

curl --request POST \
  --url https://beaconcha.in/api/v2/ethereum/validators/self-report \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "validators": [
    {
      "public_key": "<string>",
      "sub_entity": "<string>"
    }
  ],
  "chain": "mainnet"
}
'

{
  "entity": "<string>",
  "accepted": 1,
  "created": 1,
  "updated": 1,
  "reaffirmed": 1
}

Entities

Self Report Validator Entity

Claims up to 1000 validator public keys for the entity assigned to the authenticated user on the requested chain.

The caller must have an active self-report assignment for the requested chain, and every validator public key in the request must exist on that chain.

To get a self-report assignment, contact beaconcha.in support with the API user that will submit claims and the entity/sub-entity name to assign. This endpoint returns forbidden until the assignment is active.

Each validator can optionally specify a sub_entity. The server trims surrounding whitespace from sub_entity; if it is omitted or empty after trimming, the server uses the caller’s assignment-level default sub-entity.

Duplicate validator public keys with the same resolved sub_entity are deduplicated before persistence. Duplicate validator public keys with conflicting resolved sub_entity values return a bad request error.

Re-submitting validators that are already claimed by the same entity with the same resolved sub-entity reaffirms the existing claim and leaves its entity and sub-entity unchanged.

Re-submitting validators that are already claimed by the same entity with a different resolved sub-entity updates the stored sub-entity.

If any validator in the batch is already claimed by a different entity, the request returns a conflict error and no claims from the request are applied.

Note: Accepted unique claims are persisted immediately, but visibility in downstream validator entity metadata and aggregate views remains eventually consistent with the next validator tagger/precompute cycle.

POST

/

api

/

v2

/

ethereum

/

validators

/

self-report

Self Report Validator Entity

curl --request POST \
  --url https://beaconcha.in/api/v2/ethereum/validators/self-report \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "validators": [
    {
      "public_key": "<string>",
      "sub_entity": "<string>"
    }
  ],
  "chain": "mainnet"
}
'

{
  "entity": "<string>",
  "accepted": 1,
  "created": 1,
  "updated": 1,
  "reaffirmed": 1
}

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

validators

object[]

required

Validator public keys to claim for the caller's assigned entity. The request may contain at most 1000 items before duplicate public keys are resolved.

Each item may include a sub_entity. If omitted or empty after trimming, the assignment-level default sub-entity is used.

Required array length: 1 - 1000 elements

Show child attributes

chain

enum<string>

default:mainnet

The Ethereum chain to query.

Available options:

mainnet,

hoodi

Response

Successful response.

entity

string

required

The name of the entity (e.g., "Lido", "Coinbase").

accepted

integer

required

Total number of unique validator pubkeys accepted after duplicate resolution. This equals created + updated + reaffirmed.

Required range: x >= 0

created

integer

required

Number of accepted unique validator pubkeys with no previous self-report claim.

Required range: x >= 0

updated

integer

required

Number of existing same-entity claims whose resolved sub-entity changed.

Required range: x >= 0

reaffirmed

integer

required

Number of existing same-entity claims whose resolved sub-entity already matched.

Required range: x >= 0

💎 Sub Entities

⌘I