---
title: "Sync Committee Periods"
method: POST
path: "/api/v2/ethereum/sync-committee"
tags: ["Sync Committee"]
---

# Sync Committee Periods

`POST /api/v2/ethereum/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](/api-reference/ethereum/sync-committee/validators)

## Request body

- object
  - `chain` 'mainnet' | 'hoodi' — The Ethereum chain to query.
  - `sync_committee_period` union, required — Specify a sync committee period using one of the following methods. - Sync committee period number - View: "latest", "next"
    - SyncCommitteePeriodByNumber
      - `number` integer, required — The sync committee period number. Each sync committee period spans 256 epochs (approximately 27.3 hours with 6.4 minute epochs). The first sync committee period (period 290 on Ethereum Mainnet) started at the Altair hard fork on Oct 27, 2021, 10:56:23am UTC (epoch 74240).
    - SyncCommitteePeriodByChainView
      - `view` 'latest' | 'next', required

## Response `200`

Successful response.

- SyncCommitteeOverviewContainer — Response containing basic information about the sync committee.
  - `data` SyncCommitteeOverviewData, required
    - `period` integer, required — The sync committee period number. Each sync committee period spans 256 epochs (approximately 27.3 hours with 6.4 minute epochs). The first sync committee period (period 290 on Ethereum Mainnet) started at the Altair hard fork on Oct 27, 2021, 10:56:23am UTC (epoch 74240).
    - `finality` 'not_finalized' | 'finalized', required — Indicates the finality status of the data provided. - Finalized data cannot be changed without slashing at least one-third of all validators, providing strong economic guarantees. - Data marked as not_finalized does not have this guarantee and may still change.
  - `range` ResultRange, required — The range of data covered by the results, specified in slots, epochs, and Unix timestamps.
    - `slot` SlotRange, required
      - `start` integer, required — Slot by number.
      - `end` integer, required — Slot by number.
    - `epoch` EpochRange, required
      - `start` integer, required
      - `end` integer, required
    - `timestamp` TimeRange, required
      - `start` integer, required
      - `end` integer, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `405` — Method Not Allowed
- `429` — Rate Limit Exceeded
- `500` — Internal Server Error
- `default` — An unexpected error response.

---

[API](https://skmtc.dev/beaconcha/apis/external-service-api.md) · [All operations](https://skmtc.dev/beaconcha/apis/external-service-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/beaconcha/external-service-api/revisions/ad26ad970b4e/schema)