---
title: "PostValidatorRegisterValidator"
method: POST
path: "/{apiKey}/eth/v1/validator/register_validator"
---

# PostValidatorRegisterValidator

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

Provide beacon node with registrations for the given validators to the external builder network.

Prepares the beacon node for engaging with external builders. The
information must be sent by the beacon node to the builder network. It is
expected that the validator client will send this information periodically
to ensure the beacon node has correct and timely registration information
to provide to builders. The validator client should not sign blinded beacon
blocks that do not adhere to their latest fee recipient and gas limit
preferences.

Note that only registrations for active or pending validators must be sent to the builder network.
Registrations for unknown or exited validators must be filtered out and not sent to the builder network.

## 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[]
  - `message` object, required — The `ValidatorRegistration` object from the Builder API specification.
    - `fee_recipient` string, hex, required — Address to receive fees from the block.
    - `gas_limit` string, required — Preferred gas limit of validator.
    - `timestamp` string, required — Unix timestamp of registration.
    - `pubkey` string, hex, required — BLS public key of validator.
  - `signature` string, hex, required

## Response `200`

Registration information has been received.

---

[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)