> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.chainstack.com/feedback

```json
{
  "path": "/reference/getcommitteesbystateidepochindexandslot",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Committees by state, epoch, index, and slot

<Note>
  **No response in the interactive API**

  The response to the call might be too big for the web app to handle, so if you are not getting it here, copy the CURL example and run in your terminal—this will work.
</Note>

The `eth/v1/beacon/states/{state_id}/committees` method is a significant API endpoint in the Ethereum Beacon Chain. It provides comprehensive information about the committees for a given state. In the context of Ethereum, committees are groups of validators assigned to specific duties, such as proposing and attesting to blocks. Understanding the composition and assignments of these committees is crucial for validators and network participants, as it impacts their roles and responsibilities in the network's consensus process.

<Check>
  **Get your own node endpoint today**

  [Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.

  You can sign up with your GitHub, X, Google, or Microsoft account.
</Check>

## Parameters

* `{state_id}`: This parameter specifies the state identifier for which the committee information is being requested. It can be a specific slot number, an epoch number, a block root, or special values like 'genesis' or 'head'.

## Response

* `array` — list of committee objects.
  * Each `object` in the array represents a committee at the specified state, containing:
    * `index` — the index or identifier of the committee. This is used to distinguish different committees within the same epoch or state.
    * `slot` — the slot number at which the committee is assigned duties. Slots are discrete time intervals in the Beacon Chain when various operations occur.
    * `validators` — a list of validator indices that are members of this committee. These indices identify the specific validators assigned to the committee's duties.

The `eth/v1/beacon/states/{state_id}/committees` method is vital for validators and network operators in the Ethereum ecosystem. It provides essential insights into how validators are grouped into committees and assigned duties, which is fundamental to the network's operation and security.


## OpenAPI

````yaml /openapi/ethereum_beacon_chain_api/state/getCommitteesByStateIdEpochIndexAndSlot.json GET /beacon/states/{state_id}/committees
openapi: 3.0.0
info:
  title: Ethereum Committee API
  version: 1.0.0
servers:
  - url: >-
      https://beacon-nd-422-757-666.p2pify.com/0a9d79d93fb2f4a4b1e04695da2b77a7/eth/v1
security: []
paths:
  /beacon/states/{state_id}/committees:
    get:
      summary: Get committees by state, epoch, index, and slot
      operationId: getCommitteesByStateIdEpochIndexAndSlot
      parameters:
        - name: state_id
          in: path
          description: >-
            State identifier, e.g., 'head', 'finalized', 'genesis', or a
            specific slot number.
          required: true
          schema:
            type: string
            default: head
        - name: epoch
          in: query
          description: Epoch number
          required: false
          schema:
            type: integer
            format: int64
            example: 194213
        - name: index
          in: query
          description: Committee index
          required: false
          schema:
            type: integer
            format: int64
            example: 1
        - name: slot
          in: query
          description: Slot number
          required: false
          schema:
            type: integer
            format: int64
      responses:
        '200':
          description: Committee data successfully retrieved
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommitteeData'
        '404':
          description: Committee data not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    CommitteeData:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/CommitteeItem'
      required:
        - data
    Error:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
      required:
        - code
        - message
    CommitteeItem:
      type: object
      properties:
        index:
          type: integer
          format: int64
        slot:
          type: integer
          format: int64
        validators:
          type: array
          items:
            type: integer
            format: int64
      required:
        - index
        - slot
        - validators

````