> ## Documentation Index
> Fetch the complete documentation index at: https://docs.validationcloud.io/llms.txt
> Use this file to discover all available pages before exploring further.
# /eth/v1/validator/sync_committee_contribution
> Produce a sync committee contribution
```bash title="Mainnet" theme={"theme":{"light":"github-light","dark":"github-dark-default"}}
curl -X GET \
"https://mainnet.ethereum.validationcloud.io/v1//eth/v1/validator/sync_committee_contribution?slot=1&subcommittee_index=1&beacon_block_root=0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2" \
-H "Content-Type: application/json"
```
```bash title="Testnet" theme={"theme":{"light":"github-light","dark":"github-dark-default"}}
curl -X GET \
"https://sepolia.ethereum.validationcloud.io/v1//eth/v1/validator/sync_committee_contribution?slot=1&subcommittee_index=1&beacon_block_root=0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2" \
-H "Content-Type: application/json"
```
## OpenAPI
````yaml nodeapi/openapi/beacon-node-oapi-v2.json GET /eth/v1/validator/sync_committee_contribution
openapi: 3.0.3
info:
title: Eth Beacon Node API
description: >
API specification for the beacon node, which enables users to query and
participate in Ethereum 2.0 phase 0 beacon chain.
All requests by default send and receive JSON, and as such should have
either or both of the "Content-Type: application/json"
and "Accept: application/json" headers. In addition, some requests can
return data in the SSZ format. To indicate that SSZ
data is required in response to a request the header "Accept:
application/octet-stream" should be sent. Note that only a subset
of requests can respond with data in SSZ format; these are noted in each
individual request.
API endpoints are individually versioned. As such, there is no direct
relationship between all v1 endpoints, all v2 endpoints,
_etc._ and no such relationship should be inferred. All JSON responses
return the requested data under a `data` key in the top
level of their response. Additional metadata may or may not be present in
other keys at the top level of the response, dependent
on the endpoint. The rules that require an increase in version number are
as follows:
- no field that is listed in an endpoint shall be removed without an increase in the version number
- no field that is listed in an endpoint shall be altered in terms of format (_e.g._ from a string to an array) without an
increase in the version number
Note that it is possible for a field to be added to an endpoint's data or
metadata without an increase in the version number.
version: v2.3.0 - Eth2Spec v1.1.0
contact:
name: Ethereum Github
url: https://github.com/ethereum/beacon-apis/issues
license:
name: CC0-1.0
url: https://creativecommons.org/publicdomain/zero/1.0/
servers:
- url: https://mainnet.ethereum.validationcloud.io/v1//
description: Mainnet Beacon API
- url: https://sepolia.ethereum.validationcloud.io/v1//
description: Sepolia Beacon API
security: []
tags:
- name: Beacon
description: Set of endpoints to query beacon chain.
- name: Config
description: Endpoints to query chain configuration, specification, and fork schedules.
- name: Debug
description: Set of endpoints to debug chain and shouldn't be exposed publicly.
- name: Events
description: Set of endpoints to for event subscription.
- name: Node
description: Endpoints to query node related informations
- name: Validator
description: Endpoints intended for validator clients
- name: ValidatorRequiredApi
description: >
Minimal set of endpoints to enable a working validator implementation.
[Checkout validator
flow](https://github.com/ethereum/beacon-APIs/blob/master/validator-flow.md)
to learn how to use this api.
paths:
/eth/v1/validator/sync_committee_contribution:
get:
tags:
- ValidatorRequiredApi
- Validator
summary: Produce a sync committee contribution
description: Requests that the beacon node produce a sync committee contribution.
operationId: produceSyncCommitteeContribution
parameters:
- name: slot
in: query
required: true
description: The slot for which a sync committee contribution should be created.
schema:
type: string
example: '1'
- name: subcommittee_index
in: query
description: the subcommittee index for which to produce the contribution.
required: true
schema:
type: string
example: '1'
- name: beacon_block_root
in: query
description: the block root for which to produce the contribution.
required: true
schema:
type: string
example: '0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2'
pattern: ^0x[a-fA-F0-9]{64}$
responses:
'200':
description: Success response
content:
application/json:
schema:
title: produceSyncCommitteeContributionResponse
type: object
properties:
data:
type: object
properties:
slot:
allOf:
- type: string
example: '1'
- description: >-
The slot at which the validator is providing a
sync committee contribution.
beacon_block_root:
allOf:
- type: string
example: >-
0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2
pattern: ^0x[a-fA-F0-9]{64}$
- description: Block root for this contribution.
subcommittee_index:
allOf:
- type: string
example: '1'
- description: >-
The index of the subcommittee that the
contribution pertains to.
aggregation_bits:
allOf:
- description: >-
A bit is set if a signature from the validator at
the corresponding index in the subcommittee is
present in the aggregate `signature`.
- type: string
pattern: ^0x[a-fA-F0-9]{2,}$
- example: '0x01'
signature:
allOf:
- type: string
pattern: ^0x[a-fA-F0-9]{192}$
example: >-
0x1b66ac1fb663c9bc59509846d6ec05345bd908eda73e670af888da41af171505cc411d61252fb6cb3fa0017b679f8bb2305b26a285fa2737f175668d0dff91cc1b66ac1fb663c9bc59509846d6ec05345bd908eda73e670af888da41af171505
- description: >-
Signature by the validator(s) over the block root
of `slot`
'400':
description: Invalid request syntax.
content:
application/json:
schema:
type: object
properties:
code:
description: >-
Either specific error code in case of invalid request or
http status code
type: number
example: 400
message:
description: Message describing error
type: string
stacktraces:
description: Optional stacktraces, sent when node is in debug mode
type: array
items:
type: string
'404':
description: Not found
content:
application/json:
schema:
type: object
properties:
code:
description: >-
Either specific error code in case of invalid request or
http status code
type: number
example: 404
message:
description: Message describing error
type: string
stacktraces:
description: Optional stacktraces, sent when node is in debug mode
type: array
items:
type: string
example:
code: 404
message: Requested item not found
'500':
description: Beacon node internal error.
content:
application/json:
schema:
type: object
properties:
code:
description: >-
Either specific error code in case of invalid request or
http status code
type: number
example: 404
message:
description: Message describing error
type: string
stacktraces:
description: Optional stacktraces, sent when node is in debug mode
type: array
items:
type: string
example:
code: 500
message: Internal server error
'503':
description: Beacon node is currently syncing, try again later.
content:
application/json:
schema:
type: object
properties:
code:
description: >-
Either specific error code in case of invalid request or
http status code
type: number
example: 404
message:
description: Message describing error
type: string
stacktraces:
description: Optional stacktraces, sent when node is in debug mode
type: array
items:
type: string
example:
code: 503
message: >-
Beacon node is currently syncing and not serving request on
that endpoint
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.