---
title: "PostValidatorBeaconCommitteeSubscriptions"
method: POST
path: "/{apiKey}/eth/v1/validator/beacon_committee_subscriptions"
---

# PostValidatorBeaconCommitteeSubscriptions

`POST /{apiKey}/eth/v1/validator/beacon_committee_subscriptions`

Signal beacon node to prepare for a committee subnet.

After beacon node receives this request,
search using discv5 for peers related to this subnet
and replace current peers with those ones if necessary
If validator `is_aggregator`, beacon node must:
- announce subnet topic subscription on gossipsub
- aggregate attestations received on that subnet

## Path parameters

- `apiKey` string, required — <style> .custom-style { color: #048FF4; } </style> For higher throughput, please <span class="custom-style"><a href="../docs/quick-start-guide#-creating-your-api-key-on-the-zan-platform" target="_blank">create your own API key</a></span>.

## Request body

- object[]
  - `validator_index` string, required
  - `committee_index` string, required
  - `committees_at_slot` string, required — Number of committees at the returned slot
  - `slot` string, required — Should be slot at which validator is assigned to attest
  - `is_aggregator` boolean, required — Signals to BN that a validator on the VC has been chosen for aggregator role.

## Response `200`

Slot signature is valid and beacon node has prepared the attestation subnet.

Note that we cannot be certain the Beacon node will find peers for that subnet for various reasons.

---

[API](https://skmtc.dev/zan/apis/zan-getnftmetadata.md) · [All operations](https://skmtc.dev/zan/apis/zan-getnftmetadata/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/zan/zan-getnftmetadata/revisions/be8fa2338895/schema)