---
title: "Rewards"
method: POST
path: "/api/v2/ethereum/slot/sync-committee-duties"
tags: ["Slot"]
---

# Rewards

`POST /api/v2/ethereum/slot/sync-committee-duties`

## Request

- Base URL: `https://beaconcha.in`
- URL: `https://beaconcha.in/api/v2/ethereum/slot/sync-committee-duties`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/beaconcha/apis/external-service-api/docs/api/v2/ethereum/slot/sync-committee-duties/post.ts> (a function with typed inputs; its response is checked against the schema)

Provides status and reward information about sync committee duties for a specific slot for each validator. 
The validator filter is optional; if omitted, results include all validators assigned sync duties for the slot.
This endpoint currently only supports finalized data.

Use the reward endpoints for epoch based attestation rewards information.

You can combine this endpoint with:
- Find periods your validators were part in:
  [v2/ethereum/validators/sync-committee-periods](/api-reference/ethereum/validators/sync-committee-periods)
- Sync committee overview:
  [v2/ethereum/sync-committee](/api-reference/ethereum/sync-committee/overview)

## Request body

- object: Specify a slot using one of the slot number. Selecting by a consensus view may soon be available in a future update.
  - `slot` SlotByNumber, required
    - `number` integer, required: Slot by number.
  - `chain` 'mainnet' | 'hoodi', required: The Ethereum chain to query.
  - `cursor` string: Cursor value for pagination. See our [pagination guide](/api/pagination) for more details.
  - `page_size` integer: The number of items to return per page.
  - `validator` union: Free selectors available to all users: - validator_identifiers: One or more validator indices or public keys to filter by. - dashboard_id: Your beaconcha.in dashboard ID (requires a free account). **Premium selectors** for Scale & Enterprise plans (https://beaconcha.in/pricing): - withdrawal: The validator's withdrawal credential or the Ethereum wallet address used for withdrawals. - deposit_address: The Ethereum wallet address used for the validator's deposit. - entity: The name of the assigned entity (e.g., "Lido", "Coinbase"). Optionally include `sub_entity` for more specific filtering. Matching is case-sensitive. Note: The set of validators matched by `deposit_address` and `withdrawal` selectors is updated once per epoch (~6.4 minutes). Newly deposited validators may take up to one epoch to appear in query results. Note: The set of validators matched by `entity` selector is updated once per day.
    - ValidatorsByIdentifiers
      - `validator_identifiers` ValidatorIndexPublicKey[], required: An array containing either validator indices or public keys. Index and public key can be mixed in the same array. Subscribed users (Hobbyist, Business, and Scale tiers) can include up to 100 entries; free trial users and legacy subscription users (Sapphire, Emerald, Diamond) are limited to 20.
        - union
          - integer: Validator Index
          - string: Public key of a validator
    - ValidatorsByDashboard
      - `dashboard_id` integer, required: beaconcha.in dashboard ID. You can find your dashboard ID in the URL of your dashboard page on beaconcha.in (e.g., https://beaconcha.in/dashboard/12345).
      - `group_id` integer, nullable: Optional beaconcha.in dashboard group ID. If no group ID is provided, all validators in the dashboard are considered.
    - ValidatorsByDeposit
      - `deposit_address` string, required: A standard Ethereum address (20-byte hex string with 0x prefix).
    - ValidatorsByWithdrawal
      - `withdrawal` string, required: Either an execution layer address (20-byte hex string with 0x prefix) or a full 32-byte withdrawal credential.
    - ValidatorsByEntity: Select validators by their assigned entity (e.g., staking provider) and optionally a sub-entity. Entity and sub-entity names are matched exactly and are case-sensitive.
      - `entity` string, required: The name of the entity to filter validators by (e.g., "Lido", "Coinbase"). Matching is case-sensitive; use the exact name as returned by the entities overview endpoint.
      - `sub_entity` string: Optional sub-entity name to further filter validators within the entity. Matching is case-sensitive; use the exact name as returned by the sub-entities overview endpoint.

## Response `200`

Successful response.

- object: Response containing detailed information about past or future sync committee duties.
  - `data` SlotSyncCommitteeData[], required
    - `validator` Validator, required
      - `index` integer: Validator Index
      - `public_key` string: Public key of a validator
    - `reward` RewardBreakdown
      - `total` string, required: Amount in wei (1 ETH = 10^18 wei)
      - `reward` string, required: Amount in wei (1 ETH = 10^18 wei)
      - `penalty` string, required: Amount in wei (1 ETH = 10^18 wei)
      - `missed_reward` string, required: Amount in wei (1 ETH = 10^18 wei)
    - `status` 'success' | 'missed' | 'scheduled', required: Indicates the status of the sync committee duty assigned to the validator for the specified slot. Possible values: - "scheduled": The duty is scheduled for a future slot or the current head slot. Duties can only be performed starting from the next slot. - "success": The validator successfully performed the sync committee duty for this slot. - "missed": The validator missed the assigned sync committee duty for this slot. For future slots, the status will always be "scheduled". For the current head slot, the status is also "scheduled" since duties are only eligible for inclusion in the next slot.
    - `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.
  - `paging` Paging
    - `next_cursor` string: Cursor to the next page of results. See our [pagination guide](/api/pagination) for more details. If empty, there are no more pages to fetch.

## 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.dev/beaconcha/apis/external-service-api/revisions/ad26ad970b4e?raw)