POST /eth/v1/beacon/rewards/sync_committee/{block_id}

Get sync committee rewards.

Asks the beacon node to report whether any validators have been seen to be active during a specific Sync committee members' rewards information can be retrieved using an array of public keys or a validator index. Return each committee member's reward information if no array is supplied.

Example Request and Result for /v1/beacon/rewards/sync_committee/{block_id}

In this section, we provide an illustrative example of a request made to retrieve details contents using the /v1/beacon/rewards/sync_committee/{block_id} endpoint. Additionally, we present the resulting response containing information about getting sync committee rewards.

Parameters

Fields	Type	Description
block_id*	string	Block identifier. Can be one of: "head" (canonical head in node's view), "genesis", "finalized", <slot>, <hex encoded blockRoot with 0x prefix>. Example : head

The example in this section uses a non-existing project id.

Make sure you replace it with your Ethereum Holesky Beacon endpoint when issuing the API calls.

Don't have a project id? Here's a straightforward guide on how to obtain one!

Get sync committee rewards.

POST https://eth-holesky-beacon.blastapi.io/<project-id>/eth/v1/beacon/rewards/sync_committee/{block_id}

Path Parameters

Name	Type	Description
block_id*	string	head

200: OK Expand for a detailed response example

{
  "execution_optimistic": false,
  "finalized": false,
  "data": [
    {
      "validator_index": "0",
      "reward": "2000"
    }
  ]
}

Curl Request example

curl -X 'POST' \
  'https://eth-holesky-beacon.blastapi.io/<project-id>/eth/v1/beacon/rewards/sync_committee/head' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '[
  "string"
]'