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

# 💎 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](/api-reference/ethereum/builders/overview)
- The slot of a request: [v2/ethereum/slot/overview](/api-reference/ethereum/slot/overview)

**Premium Endpoint:** This endpoint requires a Scale or Enterprise plan.


> [!WARNING]
>
> **Experimental.** This endpoint returns data only on chains past the Glamsterdam hard fork. Hoodi forks first; mainnet returns `404` until it forks. The request and response may change before the mainnet release. See [Glamsterdam API](https://docs.beaconcha.in/api/glamsterdam.md).


## OpenAPI

````yaml /v3/bundled.yaml post /api/v2/ethereum/builders/withdrawal-slots
openapi: 3.0.4
info:
  title: External Service API
  version: 1.0.3
servers:
  - url: https://beaconcha.in
    description: Production API
security:
  - ApiKeyAuth: []
paths:
  /api/v2/ethereum/builders/withdrawal-slots:
    post:
      tags:
        - Builders
      summary: 💎 Builder Withdrawal Slots
      description: >
        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](/api-reference/ethereum/builders/overview)

        - The slot of a request:
        [v2/ethereum/slot/overview](/api-reference/ethereum/slot/overview)


        **Premium Endpoint:** This endpoint requires a Scale or Enterprise plan.
      operationId: GetBuilderWithdrawalSlots
      requestBody:
        $ref: '#/components/requestBodies/builderRequestSlots'
      responses:
        '200':
          $ref: '#/components/responses/BuilderWithdrawals'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '405':
          $ref: '#/components/responses/MethodNotAllowed'
        '429':
          $ref: '#/components/responses/RateLimitExceeded'
        '500':
          $ref: '#/components/responses/InternalServerError'
        default:
          $ref: '#/components/responses/DefaultError'
components:
  requestBodies:
    builderRequestSlots:
      x-go-name: BuilderRequestSlotsRequestBody
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/BuilderRequestSlotsRequest'
          example:
            chain: hoodi
            builder:
              builder_index: 1889
            page_size: 10
  responses:
    BuilderWithdrawals:
      description: Successful response.
      content:
        application/json:
          schema:
            allOf:
              - $ref: '#/components/schemas/BuilderWithdrawals.ContainerList'
              - $ref: '#/components/schemas/PagingRangeTemplate'
            description: >-
              Response containing the exit requests of the selected builder,
              newest processed slot first.
    BadRequest:
      description: Bad Request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Bad request. Please check your input and try again.
    Unauthorized:
      description: Unauthorized
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Unauthorized. Please provide a valid API key.
    Forbidden:
      description: Forbidden
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: >-
              endpoint not allowed for your subscription tier. upgrade your
              subscription at https://beaconcha.in/pricing.
    NotFound:
      description: Not Found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: The requested resource was not found.
    MethodNotAllowed:
      description: Method Not Allowed
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: 'method not allowed: GET. all public API endpoints use POST.'
    RateLimitExceeded:
      description: Rate Limit Exceeded
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Rate limit exceeded. Please try again later.
    InternalServerError:
      description: Internal Server Error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: internal server error. please try again later.
    DefaultError:
      description: An unexpected error response.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: An unexpected error occurred.
  schemas:
    BuilderRequestSlotsRequest:
      type: object
      properties:
        chain:
          $ref: '#/components/schemas/Chain'
        builder:
          allOf:
            - $ref: '#/components/schemas/buildersSelector'
          description: >
            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.
        range:
          $ref: '#/components/schemas/timeRangeSelectorNullable'
        cursor:
          $ref: '#/components/schemas/Cursor'
        page_size:
          $ref: '#/components/schemas/PageSize'
      required:
        - builder
    BuilderWithdrawals.ContainerList:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/BuilderWithdrawals.Data'
      required:
        - data
    PagingRangeTemplate:
      type: object
      properties:
        paging:
          $ref: '#/components/schemas/Paging'
        range:
          $ref: '#/components/schemas/ResultRange'
      required:
        - range
    Error:
      type: object
      properties:
        error:
          type: string
    Chain:
      type: string
      enum:
        - mainnet
        - hoodi
      default: mainnet
      description: The Ethereum chain to query.
    buildersSelector:
      description: >
        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 a proposal counts for a builder only from the epoch it took
        the index until the epoch the next builder took 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.
      oneOf:
        - $ref: '#/components/schemas/BuildersByPubkey'
        - $ref: '#/components/schemas/BuildersByIndex'
        - $ref: '#/components/schemas/BuildersByExecutionAddress'
        - $ref: '#/components/schemas/BuildersByEntity'
    timeRangeSelectorNullable:
      description: >
        Specify a time range using either Unix timestamps or epoch numbers. If
        left null, the API will query the entire available history of the
        selected validators.
      nullable: true
      default: null
      oneOf:
        - $ref: '#/components/schemas/timeRangeSelectorTime'
        - $ref: '#/components/schemas/timeRangeSelectorEpoch'
        - $ref: '#/components/schemas/timeRangeSelectorSlot'
    Cursor:
      type: string
      description: >-
        Cursor value for pagination. See our [pagination guide](/api/pagination)
        for more details.
      default: ''
    PageSize:
      type: integer
      description: The number of items to return per page.
      minimum: 1
      maximum: 10
      default: 10
    BuilderWithdrawals.Data:
      type: object
      description: One builder exit request sent to the builder request contract.
      properties:
        slot:
          allOf:
            - $ref: '#/components/schemas/Slot'
          x-sortable: true
          description: The slot that processed the request.
        observed_stages:
          type: array
          description: >-
            Always `consensus_layer_processed`, because a request is listed once
            the chain has processed it.
          items:
            $ref: '#/components/schemas/QueueType'
        builder_pubkey:
          $ref: '#/components/schemas/BuilderPublicKey'
        builder_index:
          nullable: true
          allOf:
            - $ref: '#/components/schemas/BuilderIndex'
          description: >-
            Index the builder held when the chain processed the request, from
            the registry period (tenure, see
            [v2/ethereum/builders](/api-reference/ethereum/builders/overview))
            that covers the processed epoch. Null when no registry period covers
            that epoch. Also null when beaconcha.in has no registry record for
            the public key. It can differ from the index that `builder`
            selected, because an index can pass to another builder.
        request_index:
          type: integer
          description: >-
            Position of the exit request among the builder exit requests of the
            block at `slot`.
        builder_execution_address:
          allOf:
            - $ref: '#/components/schemas/ExecutionLayerAddress'
          description: The source address of the request.
        type:
          allOf:
            - $ref: '#/components/schemas/BuilderWithdrawals.Type'
          description: The kind of the request.
        outcome:
          allOf:
            - $ref: '#/components/schemas/BuilderRequestOutcome'
          description: Whether the chain applied the request.
        reject_reason:
          nullable: true
          allOf:
            - $ref: '#/components/schemas/BuilderRequestRejectReason'
          description: >-
            Why the chain ignored the request. Set only when `outcome` is
            `rejected`.
        unknown_reason:
          nullable: true
          allOf:
            - $ref: '#/components/schemas/BuilderRequestUnknownReason'
          description: >-
            Why beaconcha.in cannot tell whether the chain applied the request.
            Set only when `outcome` is `unknown`.
        block_root:
          nullable: true
          allOf:
            - $ref: '#/components/schemas/ConsensusLayerBlockRoot'
          description: The root of the block at `slot`. Null when that slot has no block.
        finality:
          $ref: '#/components/schemas/FinalityParams'
      required:
        - slot
        - observed_stages
        - builder_pubkey
        - builder_index
        - request_index
        - builder_execution_address
        - type
        - outcome
        - reject_reason
        - unknown_reason
        - block_root
        - finality
    Paging:
      type: object
      properties:
        next_cursor:
          description: >-
            Cursor to the next page of results. See our [pagination
            guide](/api/pagination) for more details. If empty, there are no
            more pages to fetch.
          type: string
          example: eyJfc2FtcGxlX2N1cnNvciI6MTIzNDU2Nzg5MH0
    ResultRange:
      type: object
      description: >
        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.
      properties:
        slot:
          $ref: '#/components/schemas/SlotRange'
        epoch:
          $ref: '#/components/schemas/EpochRange'
        timestamp:
          $ref: '#/components/schemas/TimeRange'
      required:
        - slot
        - epoch
        - timestamp
    BuildersByPubkey:
      type: object
      title: Builder Public Key
      description: >-
        Select a builder by its public key in the beacon chain's builder
        registry. Use the key, not the builder index, to follow a builder over
        time. The chain gives the index of a builder that has exited and
        withdrawn its balance to the next new builder, and a builder that
        registers again with the same key can get a different index. The key
        matches every period in which the builder was registered.
      properties:
        builder_pubkey:
          $ref: '#/components/schemas/BuilderPublicKey'
      required:
        - builder_pubkey
    BuildersByIndex:
      type: object
      title: Builder Index
      description: >-
        Select the builder that holds this index now, with its full history, as
        `builder_pubkey` would. An index passes to a new builder after its
        builder exits and withdraws, so an index from an old slot may now name
        someone else. For the builder of a past slot, pass that slot's
        `execution_payload.builder_pubkey` from 💎
        [v2/ethereum/builders/proposal-slots](/api-reference/ethereum/builders/proposal-slots)
        or
        [v2/ethereum/validators/proposal-slots](/api-reference/ethereum/validators/proposal-slots)
        instead.
      properties:
        builder_index:
          $ref: '#/components/schemas/BuilderIndex'
      required:
        - builder_index
    BuildersByExecutionAddress:
      type: object
      title: 💎 Builder Execution Address
      description: >-
        Select every builder whose entry in the beacon chain's builder registry
        names this execution layer address for its withdrawals. One address can
        belong to many builders. The address comes from the deposit that
        registers the builder and does not change while that registration lasts.
        Anyone can register a builder with any withdrawal address, so a match
        does not prove that the owner of the address runs the builder.
      properties:
        builder_execution_address:
          allOf:
            - $ref: '#/components/schemas/ExecutionLayerAddress'
          example: '0x8f2e4c6a91b3d5e7f0a2c4e6b8d0f1a3c5e7b9d2'
          description: >-
            Execution layer address that a builder's registry entry names for
            its withdrawals.
      required:
        - builder_execution_address
    BuildersByEntity:
      type: object
      title: 💎 Builder Entity
      description: >-
        Select every builder whose registry entry withdraws to an execution
        layer address that beaconcha.in curated under this builder entity name,
        optionally only the addresses of one sub-entity. Names come from
        [v2/ethereum/builders/entities](/api-reference/ethereum/builders/entities).
        A name without a registered builder returns 404. Builder entity labels
        may take a few days after a chain's Glamsterdam hard fork to settle,
        while we observe how builders operate in the first days; until then a
        name can return 404 because no address carries it yet.
      properties:
        builder_entity:
          $ref: '#/components/schemas/BuilderEntityName'
        builder_sub_entity:
          allOf:
            - $ref: '#/components/schemas/SubEntityName'
          description: >-
            Optional sub-entity of `builder_entity`. Omit it or pass an empty
            string to select the whole entity. Matching is case-sensitive.
      required:
        - builder_entity
    timeRangeSelectorTime:
      type: object
      title: Unix Timestamp
      description: Range provided via Unix timestamp (inclusive)
      properties:
        timestamp:
          $ref: '#/components/schemas/timeRangeStartEnd'
      required:
        - timestamp
    timeRangeSelectorEpoch:
      type: object
      title: Epoch
      description: Range provided via epoch number
      properties:
        epoch:
          $ref: '#/components/schemas/epochRangeStartEnd'
      required:
        - epoch
    timeRangeSelectorSlot:
      type: object
      title: Slot
      description: Range provided via slot number
      properties:
        slot:
          $ref: '#/components/schemas/slotRangeStartEnd'
      required:
        - slot
    Slot:
      type: integer
      minimum: 0
      description: Slot by number.
    QueueType:
      type: string
      enum:
        - execution_layer_queued
        - execution_layer_processed
        - consensus_layer_queued
        - consensus_layer_processed
    BuilderPublicKey:
      type: string
      pattern: ^0x[a-fA-F0-9]{96}$
      example: >-
        0xa0df2d753f8a123bb822a90e421a552c28008778920345a0510a22a346c25fc7c60bfc8c1f9cfd9b7ecd945fdcef68d3
      description: >-
        BLS public key of a builder in the beacon chain's builder registry,
        which exists from the Glamsterdam hard fork on. The registry is separate
        from the builder keys that relays report, such as on
        [v2/ethereum/block/mev-bids](/api-reference/ethereum/block/mev-bids); a
        relay-reported key matches only if that builder also registered it on
        chain.
    BuilderIndex:
      type: integer
      minimum: 0
      example: 1889
      maximum: 1099511627775
      description: >-
        Index of a builder in the beacon chain's builder registry, which exists
        from the Glamsterdam hard fork on. Always below 2^40 (1099511627776). A
        builder payment withdrawal on chain carries the builder index plus 2^40
        (`BUILDER_INDEX_FLAG`) as its validator index, so subtract 2^40 before
        you pass it here. 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.
    ExecutionLayerAddress:
      type: string
      pattern: ^0x[a-fA-F0-9]{40}$
      description: A standard Ethereum address (20-byte hex string with 0x prefix).
      example: '0x388C818CA8B9251b393131C08a736A67ccB19297'
    BuilderWithdrawals.Type:
      type: string
      description: >
        The kind of a builder withdrawal request.


        - `exit`: a request that asks a builder to start its exit.


        More values will be added for builder payouts. Select items by `type`,
        and do not read every item as an exit request.
      enum:
        - exit
      x-enum-varnames:
        - BuilderWithdrawalsTypeExit
      example: exit
    BuilderRequestOutcome:
      type: string
      description: >
        Whether the chain applied a builder request.


        - `completed`: the chain applied the request.

        - `rejected`: the chain ignored the request. `reject_reason` says why.

        - `unknown`: beaconcha.in cannot tell whether the chain applied the
        request. `unknown_reason` says why. An `unknown` outcome is never a
        rejection. For a deposit, `type` is best effort: `top_up` depends on the
        registry, so an `unknown` deposit can show the wrong type.
      enum:
        - completed
        - rejected
        - unknown
      x-enum-varnames:
        - BuilderRequestOutcomeCompleted
        - BuilderRequestOutcomeRejected
        - BuilderRequestOutcomeUnknown
      example: completed
    BuilderRequestRejectReason:
      type: string
      description: >
        Why the chain ignored a builder request.


        - `invalid_credential_prefix`: a deposit whose withdrawal credential
        does not start with `0xB0`. The chain ignores it, also when the public
        key already holds a builder, and its amount is locked in the builder
        deposit contract (`stake_locked`).

        - `invalid_signature`: a deposit for a new public key whose signature is
        invalid. The chain ignores it, and its amount is locked in the builder
        deposit contract (`stake_locked`). The signature of a top-up is not
        checked, so an invalid signature on a top-up is not a rejection.

        - `unknown_builder`: an exit for a public key that the registry and the
        request history do not show as a builder at that slot.

        - `registration_not_finalized`: an exit for a builder whose registration
        the finalized state had not yet reached.

        - `already_exiting`: an exit for a builder that had already started its
        exit.

        - `wrong_source_address`: an exit whose source address is not the
        builder's execution address.

        - `pending_obligations`: an exit for a builder that still owed pending
        payments or withdrawals. beaconcha.in cannot read those, so this reason
        is inferred: the other checks passed, and the registry shows no exit
        that started in that epoch.
      enum:
        - invalid_credential_prefix
        - invalid_signature
        - unknown_builder
        - registration_not_finalized
        - already_exiting
        - wrong_source_address
        - pending_obligations
      x-enum-varnames:
        - BuilderRequestRejectReasonInvalidCredentialPrefix
        - BuilderRequestRejectReasonInvalidSignature
        - BuilderRequestRejectReasonUnknownBuilder
        - BuilderRequestRejectReasonRegistrationNotFinalized
        - BuilderRequestRejectReasonAlreadyExiting
        - BuilderRequestRejectReasonWrongSourceAddress
        - BuilderRequestRejectReasonPendingObligations
      example: invalid_signature
    BuilderRequestUnknownReason:
      type: string
      description: >
        Why beaconcha.in cannot tell whether the chain applied a builder
        request.


        - `no_finalized_checkpoint`: beaconcha.in did not record the finalized
        checkpoint for the block at the request's `slot`, which applied the
        exit, so it cannot check the builder's registration against finality.

        - `registry_gap`: no registry period (tenure, see
        [v2/ethereum/builders](/api-reference/ethereum/builders/overview))
        covers the request, but the chain made the key a builder, or the
        registry was not observed for the request's slot. A gap in our data, not
        a verdict.

        - `registry_pending`: the request is newer than beaconcha.in's latest
        finalized registry snapshot, so the outcome is not checked yet. This is
        transient: it appears on recent items, normally before they are
        finalized. Query again after the request is finalized.

        - `several_candidates`: two or more exit requests for this builder in
        one epoch could each have started the exit. The chain accepted one of
        them, and beaconcha.in cannot tell which.
      enum:
        - no_finalized_checkpoint
        - registry_gap
        - registry_pending
        - several_candidates
      x-enum-varnames:
        - BuilderRequestUnknownReasonNoFinalizedCheckpoint
        - BuilderRequestUnknownReasonRegistryGap
        - BuilderRequestUnknownReasonRegistryPending
        - BuilderRequestUnknownReasonSeveralCandidates
      example: registry_gap
    ConsensusLayerBlockRoot:
      type: string
      pattern: ^0x[a-fA-F0-9]{64}$
      description: A 32-byte block root represented as a hex string with 0x prefix.
    FinalityParams:
      type: string
      description: |
        Indicates the finality status of the data provided. 
          - Finalized data cannot be changed without slashing at least one-third of all validators, providing strong economic guarantees.
          - Data marked as not_finalized does not have this guarantee and may still change.
      enum:
        - not_finalized
        - finalized
      example: finalized
    SlotRange:
      type: object
      properties:
        start:
          $ref: '#/components/schemas/Slot'
        end:
          $ref: '#/components/schemas/Slot'
      required:
        - start
        - end
    EpochRange:
      type: object
      properties:
        start:
          $ref: '#/components/schemas/Epoch'
        end:
          $ref: '#/components/schemas/Epoch'
      required:
        - start
        - end
    TimeRange:
      type: object
      properties:
        start:
          $ref: '#/components/schemas/timestamp'
        end:
          $ref: '#/components/schemas/timestamp'
      required:
        - start
        - end
    BuilderEntityName:
      type: string
      example: Titan
      description: >-
        Curated name of a builder operator, such as a block builder or a relay.
        Builder entity names share one namespace with staking entity names, so
        one company has one name, and the same name can stand for a staking
        entity in a `validator` selector and for a builder operator in a
        `builder` selector. A relay's name ends in " relay", so a relay never
        shares an entity with a builder that the same company runs. Matching is
        case-sensitive.
    SubEntityName:
      type: string
      description: The name of the sub-entity.
      example: Lido CSM
    timeRangeStartEnd:
      type: object
      description: Unix timestamp range (inclusive)
      properties:
        start:
          $ref: '#/components/schemas/timestamp'
          example: 0
          description: Start Unix Timestamp
        end:
          $ref: '#/components/schemas/timestamp'
          example: 2147483647
          description: End Unix Timestamp
      required:
        - start
        - end
    epochRangeStartEnd:
      type: object
      description: Epoch range (inclusive)
      properties:
        start:
          $ref: '#/components/schemas/EpochSelector'
          description: Start Epoch
        end:
          $ref: '#/components/schemas/EpochSelector'
          description: End Epoch
      required:
        - start
        - end
    slotRangeStartEnd:
      type: object
      description: Slot range (inclusive)
      properties:
        start:
          $ref: '#/components/schemas/SlotSelector'
          description: Start Slot
        end:
          $ref: '#/components/schemas/SlotSelector'
          description: End Slot
    Epoch:
      type: integer
      minimum: 0
    timestamp:
      type: integer
      minimum: 0
    EpochSelector:
      description: |
        Specify an epoch using one of the following methods.
        - epoch number
        - View: "latest", "finalized" 
      oneOf:
        - $ref: '#/components/schemas/EpochByNumber'
        - $ref: '#/components/schemas/EpochByChainView'
    SlotSelector:
      description: |
        Specify a slot using one of the following methods.
        - Slot number
        - Consensus layer block root
        - View: "latest", "finalized" 
      oneOf:
        - $ref: '#/components/schemas/SlotByNumber'
        - $ref: '#/components/schemas/SlotByConsensusLayerBlockRoot'
        - $ref: '#/components/schemas/SlotByChainView'
      default: latest
    EpochByNumber:
      title: Number
      type: object
      properties:
        number:
          $ref: '#/components/schemas/Epoch'
      required:
        - number
    EpochByChainView:
      title: View
      type: object
      properties:
        view:
          allOf:
            - $ref: '#/components/schemas/ChainView'
          description: >
            - "latest": Refers to the most recent epoch, which may not yet be
            finalized.

            - "finalized": Refers to the latest epoch that has been finalized
            and is not subject to change.
      required:
        - view
    SlotByNumber:
      title: Number
      type: object
      properties:
        number:
          $ref: '#/components/schemas/Slot'
      required:
        - number
    SlotByConsensusLayerBlockRoot:
      title: Root
      type: object
      properties:
        root:
          $ref: '#/components/schemas/ConsensusLayerBlockRoot'
      required:
        - root
    SlotByChainView:
      title: View
      type: object
      properties:
        view:
          allOf:
            - $ref: '#/components/schemas/ChainView'
          description: >
            - "latest": Refers to the most recent slot, which may be subject to
            reorganization.

            - "finalized": Refers to the latest slot that has been finalized and
            is not subject to change.
      required:
        - view
    ChainView:
      type: string
      enum:
        - latest
        - finalized
      description: >
        - "latest": Refers to the most recent block, which may be subject to
        reorganization.

        - "finalized": Refers to the latest block that has been finalized and is
        not subject to change.
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      description: >-
        Authorization header with value: Bearer YOUR_TOKEN. Refer to the [API
        Keys](/api/overview#api-keys) section to create your API key.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.