Skip to main content
POST
/
api
/
v2
/
ethereum
/
sync-committee
Sync Committee
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"
}
'
{
  "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"
​
chain
enum<string>
default:mainnet

The Ethereum chain to query.

Available options:
mainnet,
hoodi

Response

Successful response.

Response containing basic information about the sync committee.

​
data
object
required
​
range
object
required

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