💎 Builder Withdrawal Slots
Returns the builder exit requests of EIP-8282, which the Glamsterdam hard fork introduces, for the selected builders. An exit request asks a builder to start its exit. Each item is one request. The chain does not report these outcomes. beaconcha.in derives each one by applying the protocol rules to the request and to the builder registry.
Select the builders with builder. A builder_pubkey returns the exit requests of that public key. Any other option returns the exit requests of every public key that its registry periods belong to. An index passes to a new builder once its builder exits and withdraws, so the exit requests of an earlier holder of the same index are not returned. Pass that earlier builder’s builder_pubkey to see them.
The response is 404 when the selector matches no builder: a builder_pubkey with no record of any kind, or any other option with no registry period. It is also 404 when the chain has not reached the Glamsterdam hard fork.
An exit request waits in the execution layer queue until a block carries it. The execution layer releases at most 16 exit requests into each block, oldest first. A request that is still queued does not appear. The chain applies each request in the block after the one that carried it. slot is that block, and its parent is the block that carried the request.
builder_execution_address is the source address of the request. A request has no amount.
outcome is completed when the chain applied the request, rejected with a reject_reason when the chain ignored it, and unknown with an unknown_reason when beaconcha.in cannot tell. Only rejected is a rejection. The chain does not retry a rejected request. To act again, send a new request.
Every item has observed_stages consensus_layer_processed, because beaconcha.in lists a request once the chain has processed it. For that reason this endpoint has no stage filter. Results can be filtered by a time range.
More type values will be added for builder payouts. Select items by type, and do not read every item as an exit request.
Results are paginated with a default and maximum page size of 10. Items are ordered by slot, newest first. Items in the same block are ordered by their position in that block, last position first.
Once an item has finality finalized and an outcome other than unknown, it does not change. An item with registry_pending gets its outcome once a finalized registry snapshot includes it, so query it again then. Cache items, not pages, because a new request adds an item to the first page.
You can combine this endpoint with:
- The builder’s registry periods, one per tenure: v2/ethereum/builders
- The slot of a request: v2/ethereum/slot/overview
Premium Endpoint: This endpoint requires a Scale or Enterprise plan.
Authorizations
Authorization header with value: Bearer YOUR_TOKEN. Refer to the API Keys section to create your API key.
Body
Select builders by one of these options. Every endpoint that uses this selector requires a Scale or Enterprise plan:
- builder_pubkey: One builder, by its public key, as in
execution_payload.builder_pubkey. The best way to follow one builder over time. - builder_index: The builder that holds this index now. To select the builder of a past slot, use that slot's
builder_pubkey. - builder_execution_address: Every builder that withdraws to this execution layer address. Use it for all the builders of one operator.
- builder_entity: Every builder that withdraws to an address that beaconcha.in curated under this name. Optionally include
builder_sub_entity. Matching is case-sensitive.
Note: When a builder exits and withdraws its whole balance, the chain gives its index to the next new builder, so one index can name different builders over time. Every option therefore resolves to builder public keys, and every request of such a key is listed, whichever registry period it falls in. Each item's builder_index is the index the key held when the chain processed it. The builder registry exists from the Glamsterdam hard fork on. An option that matches no builder returns 404. A builder that matches but has nothing in the result returns an empty list or zero counts, not 404.
Execution address and entity reach builders that entered the registry. Records of a public key that never became a builder, such as deposits the fork dropped, are found by builder_pubkey only.
- Builder Public Key
- Builder Index
- 💎 Builder Execution Address
- 💎 Builder Entity
Cursor value for pagination. See our pagination guide for more details.
Response
Successful response.
Response containing the exit requests of the selected builder, newest processed slot first.
The time span actually covered by the returned results — from the first to the last matching data point — specified in slots, epochs, and Unix timestamps.
This reflects the data that was found, not the range that was queried. When the response is 200 but no data is found, it falls back to the requested range, or to the full available history if no range was given. Some endpoints answer 404 instead when no data is found.
For arbitrary (custom) time-range queries the queried range is expanded outward to whole UTC days, so the covered range may be wider than requested. As stated above, the reported range still reflects the data that was actually found — a touched UTC day with no data for the selected validators will not extend it.

