> ## 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.

# Withdrawals for a slot

> Retrieve all withdrawal operations included in the execution payload of the beacon block for a specific slot. A withdrawal moves ETH from the beacon chain to an execution-layer address after a validator has eligible balance.
Provide a slot number or use the keyword `latest` to fetch from the most recently processed slot. The response lists each withdrawal with the recipient address, amount in gwei, the originating validator index, and the global withdrawal index.



## OpenAPI

````yaml /api/v1/bundled.yaml get /api/v1/slot/{slot}/withdrawals
openapi: 3.0.4
info:
  title: beaconcha.in API Documentation
  license:
    name: GPL-3.0
    url: https://www.gnu.org/licenses/gpl-3.0.en.html
  description: >-
    > ⚠️ No new features or endpoints will be added to V1. We recommend the [V2
    API](/api/overview) for all new projects. See the [migration
    guide](/api/v1-to-v2-migration).

    ## Introduction

    **Advanced and reliable API for accessing comprehensive Ethereum blockchain
    data.**


    - **Free Usage Policy:** The API is free to use under a fair use policy,
    with rate limits of 10 requests per minute per IP.

    - **Caching:** All responses are cached for 1 minute.

    - **Higher Usage Plans:** For higher usage plans, visit:
    [https://beaconcha.in/pricing](https://beaconcha.in/pricing). An API key is
    required to use these plans.


    ### API Key Usage

    API keys can be obtained at
    [/user/settings](https://beaconcha.in/user/settings) and must be included in
    requests either as a query string parameter or in the request header.


    #### Example: Query String Parameter

    ```bash

    curl https://beaconcha.in/api/v1/slot/1?apikey=<your_key>

    ```


    #### Example: Request Header

    ```bash

    curl -H 'apikey: <your_key>' https://beaconcha.in/api/v1/slot/1

    ```
  contact: {}
  version: '1.1'
servers:
  - url: https://beaconcha.in
    description: Ethereum mainnet
  - url: https://hoodi.beaconcha.in
    description: Hoodi Ethereum testnet
security:
  - ApiKeyAuthQuery: []
  - ApiKeyAuthHeader: []
tags:
  - name: Epoch
    description: Data related to consensus layer epochs
  - name: Slots
    description: Data related to consensus layer slots
  - name: Validators
    description: Data related to consensus layer validators
  - name: Rewards
    description: Data related to validator rewards
  - name: Sync Committees
    description: Data related to sync committees
  - name: Rocketpool
    description: Data related to the rocketpool protocol
  - name: ETH.Store®
    description: Data related to the ETH.Store® metric
  - name: Validator deposits
    description: Data related to execution layer validator deposits
  - name: Blocks
    description: Data related to execution layer blocks
  - name: Gas
    description: Data related to gas prices
  - name: Address
    description: Data related to ethereum addresses
  - name: Network
    description: Network data
  - name: Misc
    description: Miscellaneous data
  - name: User
    description: User data
  - name: Machine Metrics
    description: Submit machine, beacon-node, and validator-client monitoring metrics
paths:
  /api/v1/slot/{slot}/withdrawals:
    get:
      tags:
        - Slots
      summary: Withdrawals for a slot
      description: >-
        Retrieve all withdrawal operations included in the execution payload of
        the beacon block for a specific slot. A withdrawal moves ETH from the
        beacon chain to an execution-layer address after a validator has
        eligible balance.

        Provide a slot number or use the keyword `latest` to fetch from the most
        recently processed slot. The response lists each withdrawal with the
        recipient address, amount in gwei, the originating validator index, and
        the global withdrawal index.
      operationId: listSlotWithdrawals
      parameters:
        - name: slot
          in: path
          description: >-
            The slot to fetch. Provide an integer slot number (>= 0) or the
            special tag `latest` for the most recently processed slot.
          required: true
          style: simple
          explode: false
          schema:
            oneOf:
              - type: integer
                minimum: 0
                description: Slot number (>= 0)
                example: 12751688
              - type: string
                enum:
                  - latest
                description: Latest processed slot
                example: latest
      responses:
        '200':
          description: >-
            The slot was found and its withdrawals are returned in the `data`
            array. If the slot has no withdrawals, the array is empty.
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/types.ApiResponse'
                  - type: object
                    properties:
                      data:
                        type: array
                        items:
                          $ref: '#/components/schemas/types.APIWithdrawalResponse'
        '400':
          description: >-
            The request is invalid (for example, a negative slot or a slot in
            the future).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/types.ApiErrorResponse'
              examples:
                invalidSlot:
                  summary: Invalid slot parameter
                  value:
                    status: 'ERROR: invalid block slot provided'
                    data: null
        '500':
          description: An unexpected server error occurred while processing your request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/types.ApiErrorResponse'
              examples:
                serverError:
                  summary: Internal error
                  value:
                    status: 'ERROR: internal server error'
                    data: null
components:
  schemas:
    types.ApiResponse:
      type: object
      description: Standard success envelope used by all API endpoints.
      properties:
        status:
          type: string
          description: >-
            HTTP-independent status of the API operation. For successful
            responses this is always "OK".
          enum:
            - OK
        data:
          description: Response payload specific to the endpoint.
          nullable: true
          x-omitempty: true
    types.APIWithdrawalResponse:
      type: object
      description: >-
        Withdrawal included in a beacon block's execution payload, with
        recipient, amount, and provenance.
      properties:
        address:
          type: string
          description: >-
            Recipient execution-layer address (0x-prefixed, 20-byte hex; 40 hex
            characters after 0x).
          example: '0xb10edd6fa6067dba8d4326f1c8f0d1c791594f13'
        amount:
          type: integer
          description: Withdrawn amount in gwei (1 gwei = 1e9 wei).
          minimum: 0
          example: 18429837
        block_slot:
          type: integer
          description: Slot number of the block that included this withdrawal.
          minimum: 0
          example: 12771160
        validatorindex:
          type: integer
          description: Index of the validator whose balance was withdrawn (>= 0).
          minimum: 0
          example: 1120967
        withdrawalindex:
          type: integer
          description: Global sequential index assigned to this withdrawal (>= 0).
          minimum: 0
          example: 104169659
    types.ApiErrorResponse:
      type: object
      description: Standard error envelope returned when a request fails.
      properties:
        status:
          type: string
          description: >-
            Human-readable error indicator and message. The value begins with
            "ERROR:" followed by details.
          example: 'ERROR: <Message>'
        data:
          type: string
          description: Optional additional context for the error. Null in most cases.
          nullable: true
          default: null
  securitySchemes:
    ApiKeyAuthQuery:
      type: apiKey
      in: query
      name: apikey
      description: ''
    ApiKeyAuthHeader:
      type: apiKey
      in: header
      name: apikey
      description: ''

````