> ## 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. # Deposits for a slot > Retrieve all validator deposit operations included in the beacon block for a specific slot. Deposits include the validator public key, withdrawal credentials, amount (gwei), and signature. Use pagination parameters to page through results when many deposits are present. ## OpenAPI ````yaml /api/v1/bundled.yaml get /api/v1/slot/{slot}/deposits 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= ``` #### Example: Request Header ```bash curl -H 'apikey: ' 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}/deposits: get: tags: - Slots summary: Deposits for a slot description: >- Retrieve all validator deposit operations included in the beacon block for a specific slot. Deposits include the validator public key, withdrawal credentials, amount (gwei), and signature. Use pagination parameters to page through results when many deposits are present. operationId: listSlotDeposits 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 - name: offset in: query description: >- Number of items to skip from the start of the result set. Use 0 for the first page. required: false style: form explode: true schema: type: integer minimum: 0 example: 0 default: 0 - name: limit in: query description: >- Upper bound for the range of items to return. The effective page size is computed as min(100, limit - offset). Must be greater than `offset`. To request N items, set limit = offset + N. When omitted or out of range, the service uses offset + 100. required: false style: form explode: true schema: type: integer minimum: 1 example: 40 responses: '200': description: >- The slot was found and its deposits are returned in the `data` array. If the slot has no deposits, 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.APIDepositsResponse' '400': description: >- The request is invalid (for example, a negative slot or malformed parameters). 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.APIDepositsResponse: type: object description: >- Validator deposit included in a beacon block, with block inclusion metadata and deposit data fields. properties: amount: type: integer description: Deposited amount in gwei (1 gwei = 1e9 wei). example: 32000000000 block_index: type: integer description: >- Zero-based index of this deposit within the including block’s deposits list. example: 1 block_root: type: string description: >- Root of the beacon block that included this deposit (0x-prefixed, 32-byte hex). example: '0x538d7fba9f4ed29d396d18c225e91e35a5c5bd0aa9a51bd53f18df8fffaf0e4c' block_slot: type: integer description: Slot number of the block that included this deposit. example: 11648084 proof: type: string nullable: true description: >- SSZ Merkle proof for the deposit inclusion as 0x-prefixed hex; null when not recorded. example: null publickey: type: string description: >- BLS12-381 validator public key (48 bytes; 0x-prefixed hex with 96 hex characters). example: >- 0x88527b5e326c4837d765e522995e2937aaa945e79a1183a53fc369db70097484c656efa1cf216c57d88b9d2551c97ce9 signature: type: string description: >- BLS signature over the deposit message (96 bytes; 0x-prefixed hex with 192 hex characters). example: >- 0xa8c663fa0386ba988a5916a76b10bc5922ce4e2d03b1baf852e138316c0b296df1ef46aba5063b8fdc2ab7c7163fdd5d05733f7ec334009fddec1f02d78f5f7324f4d696577ef453d29937b2fd1b5b2d610edaa253a8423dd1f17e621f3493cf withdrawalcredentials: type: string description: >- 32-byte withdrawal credentials (0x-prefixed hex). Values beginning with 0x01 encode an ETH1 address; values beginning with 0x00 indicate BLS withdrawal credentials. example: '0x01000000000000000000000096fb413349cb4ec17410df929898ae9c0e56ae40' 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: ' 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: '' ````