Sync Committee

Returns basic sync committee information for a particular sync period. Use this to determine the range of epochs a given sync period entails.

You can combine this endpoint with:

• Validators in sync committee period:
  v2/ethereum/sync-committee/validators

POST /api/v2/ethereum/sync-committee

Sync Committee

cURL

curl --request POST \
  --url https://beaconcha.in/api/v2/ethereum/sync-committee \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "sync_committee_period": {
    "view": "latest"
  },
  "chain": "mainnet"
}
'

200

{
  "data": {
    "period": 1,
    "finality": "not_finalized"
  },
  "range": {
    "slot": {
      "start": 1,
      "end": 1
    },
    "epoch": {
      "start": 1,
      "end": 1
    },
    "timestamp": {
      "start": 1,
      "end": 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

sync_committee_period · Number · object · required

Specify a sync committee period using one of the following methods.

• Sync committee period number
• View: "latest", "next"

Number

View

Show child attributes

chain · enum<string> · default: mainnet

The Ethereum chain to query.

Available options: mainnet, hoodi

Response

200

application/json

Successful response.

Response containing basic information about the sync committee.

data · object · required

Show child attributes

range · object · required

The range of data covered by the results, specified in slots, epochs, and Unix timestamps.

Show child attributes