> ## 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. # Validator Queue Compounding Switch Details > Returns a paginated list of compounding switch requests for the selected validators. A compounding switch changes a validator's withdrawal credential prefix from `0x01` to `0x02`, unlocking effective balances above 32 ETH (up to 2048 ETH). Unlike a consolidation, the validator stays active throughout — no exit, no balance transfer. This endpoint covers **self-consolidation requests only** (source pubkey equals target pubkey). For cross-validator consolidations where one validator's balance is merged into another, use [/api/v2/ethereum/validators/queues/consolidations](/api-reference/ethereum/validators/queues/consolidations). A `pending` entry becomes `completed` or `rejected` once the consensus layer picks the request up out of the execution-layer contract, which releases at most two requests per block. Unlike consolidations, switches have no intermediate queued phase — they are accepted or rejected immediately at consensus-layer inclusion. Pending entries appear first. Completed and rejected entries follow, ordered by submission time (most recent first). Use `status_filter` to narrow the response to a single status, e.g. only `rejected` entries. Use this endpoint alongside the queue overview at [/api/v2/ethereum/validators/queues](/api-reference/ethereum/validators/queues) for a complete picture. **Temporary restriction:** the validator selector must resolve to no more than 50,000 validators. A larger selection returns `400`. Narrow the selection — for example, select a sub-entity instead of a whole entity — or page through it with a set of validator indices. This limit will be raised. ## OpenAPI ````yaml /v3/bundled.yaml post /api/v2/ethereum/validators/queues/compounding-switches 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/validators/queues/compounding-switches: post: tags: - Network summary: Validator Queue Compounding Switch Details description: > Returns a paginated list of compounding switch requests for the selected validators. A compounding switch changes a validator's withdrawal credential prefix from `0x01` to `0x02`, unlocking effective balances above 32 ETH (up to 2048 ETH). Unlike a consolidation, the validator stays active throughout — no exit, no balance transfer. This endpoint covers **self-consolidation requests only** (source pubkey equals target pubkey). For cross-validator consolidations where one validator's balance is merged into another, use [/api/v2/ethereum/validators/queues/consolidations](/api-reference/ethereum/validators/queues/consolidations). A `pending` entry becomes `completed` or `rejected` once the consensus layer picks the request up out of the execution-layer contract, which releases at most two requests per block. Unlike consolidations, switches have no intermediate queued phase — they are accepted or rejected immediately at consensus-layer inclusion. Pending entries appear first. Completed and rejected entries follow, ordered by submission time (most recent first). Use `status_filter` to narrow the response to a single status, e.g. only `rejected` entries. Use this endpoint alongside the queue overview at [/api/v2/ethereum/validators/queues](/api-reference/ethereum/validators/queues) for a complete picture. **Temporary restriction:** the validator selector must resolve to no more than 50,000 validators. A larger selection returns `400`. Narrow the selection — for example, select a sub-entity instead of a whole entity — or page through it with a set of validator indices. This limit will be raised. operationId: GetValidatorQueueCompoundingSwitchDetails requestBody: $ref: >- #/components/requestBodies/validatorChainCursorPageSizeCompoundingSwitchStatusFilter responses: '200': $ref: '#/components/responses/ValidatorQueueCompoundingSwitchDetail' '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: validatorChainCursorPageSizeCompoundingSwitchStatusFilter: content: application/json: schema: allOf: - $ref: '#/components/schemas/ValidatorChainCursorPageSizeBase' - type: object properties: status_filter: $ref: '#/components/schemas/CompoundingSwitchStatusFilter' required: - validator responses: ValidatorQueueCompoundingSwitchDetail: description: Successful response. content: application/json: schema: type: object properties: data: type: array items: $ref: >- #/components/schemas/ValidatorQueueCompoundingSwitchDetail.Data paging: $ref: '#/components/schemas/Paging' required: - data - paging 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: ValidatorChainCursorPageSizeBase: type: object properties: chain: $ref: '#/components/schemas/Chain' cursor: $ref: '#/components/schemas/Cursor' page_size: $ref: '#/components/schemas/PageSize' validator: $ref: '#/components/schemas/validatorsSelector' CompoundingSwitchStatusFilter: type: string nullable: true default: null description: > Filter results to a single compounding switch status. If not specified, results include all statuses. - `pending`: recorded on the execution layer; not yet included by the consensus layer. - `completed`: the switch was applied. - `rejected`: rejected at consensus-layer inclusion. enum: - pending - completed - rejected example: rejected x-enum-varnames: - CompoundingSwitchStatusFilterPending - CompoundingSwitchStatusFilterCompleted - CompoundingSwitchStatusFilterRejected ValidatorQueueCompoundingSwitchDetail.Data: type: object description: > A single compounding switch request for one of the selected validators. A compounding switch changes the validator's withdrawal credential prefix from `0x01` to `0x02`, enabling it to hold balances above the standard 32 ETH effective balance cap (up to 2048 ETH). Unlike a full consolidation, no validator exits and no balance is transferred — the validator remains active throughout. Status semantics: - `pending`: recorded on the execution layer; the consensus layer has not yet included it. `execution_layer` is set. Transitions to `completed` or `rejected` once the request is read out of the contract, which releases at most two requests per block. - `completed`: the switch was applied on the consensus layer. `processed_slot` is set. - `rejected`: the consensus layer rejected the request at inclusion time (e.g. validator already exiting or already compounding). `reject_reason` is set. properties: validator: allOf: - $ref: '#/components/schemas/validator' description: The validator switching to compounding withdrawal credentials. status: type: string enum: - pending - completed - rejected description: Current status of the compounding switch request. example: rejected x-enum-varnames: - ValidatorQueueCompoundingSwitchDetailStatusPending - ValidatorQueueCompoundingSwitchDetailStatusCompleted - ValidatorQueueCompoundingSwitchDetailStatusRejected execution_layer: allOf: - $ref: '#/components/schemas/ExecutionLayerRequestInfo' description: > Execution-layer transaction details for this request. Present for `pending` entries; null for `completed` and `rejected` entries (the EL↔CL linkage is not tracked once the consensus layer has processed the request). nullable: true reject_reason: allOf: - $ref: '#/components/schemas/ValidatorConsolidations.RejectReason' description: > Set when `status` is `rejected`. May be null if the rejection reason was not recognized by the server (e.g. client-specific errors or future protocol additions). nullable: true processed_slot: type: integer description: > The consensus layer slot in which the compounding switch was applied. Set only when `status` is `completed`. nullable: true required: - validator - status 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 Error: type: object properties: error: type: string Chain: type: string enum: - mainnet - hoodi default: mainnet description: The Ethereum chain to query. 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 validatorsSelector: description: >- Free selectors available to all users: - validator_identifiers: One or more validator indices or public keys to filter by. - dashboard_id: Your beaconcha.in dashboard ID (requires a free account). **Premium selectors** for Scale & Enterprise plans (https://beaconcha.in/pricing): - withdrawal: The validator's withdrawal credential or the Ethereum wallet address used for withdrawals. - deposit_address: The Ethereum wallet address used for the validator's deposit. - entity: The name of the assigned entity (e.g., "Lido", "Coinbase"). Optionally include `sub_entity` for more specific filtering. Matching is case-sensitive. Note: The set of validators matched by `deposit_address` and `withdrawal` selectors is updated once per epoch (~6.4 minutes). Newly deposited validators may take up to one epoch to appear in query results. Note: The set of validators matched by `entity` selector is updated once per day. oneOf: - $ref: '#/components/schemas/ValidatorsByIdentifiers' - $ref: '#/components/schemas/ValidatorsByDashboard' - $ref: '#/components/schemas/ValidatorsByDeposit' - $ref: '#/components/schemas/ValidatorsByWithdrawal' - $ref: '#/components/schemas/ValidatorsByEntity' validator: type: object properties: index: allOf: - $ref: '#/components/schemas/validatorIndex' nullable: true public_key: $ref: '#/components/schemas/validatorPublicKey' ExecutionLayerRequestInfo: type: object description: >- Execution-layer transaction details for a request submitted via the EL request queue. properties: tx_hash: type: string description: The transaction hash, in 0x-prefixed hex. from_address: type: string description: The EOA address that submitted the transaction, in 0x-prefixed hex. required: - tx_hash - from_address ValidatorConsolidations.RejectReason: type: string description: Reason a consolidation request was rejected at the consensus layer. enum: - source_equals_target - full_queue - insufficient_consolidation_churn - source_unknown_pubkey - target_unknown_pubkey - source_no_execution_withdrawal_credentials - source_address_mismatch - target_not_compounding - source_inactive - target_inactive - source_exiting - target_exiting - source_too_young - source_pending_withdrawals - source_slashed example: source_inactive ValidatorsByIdentifiers: type: object title: Indices/Pubkeys properties: validator_identifiers: $ref: '#/components/schemas/validatorIndexPublicKeys' required: - validator_identifiers ValidatorsByDashboard: type: object title: Dashboard properties: dashboard_id: $ref: '#/components/schemas/dashboardID' group_id: $ref: '#/components/schemas/dashboardGroupID' required: - dashboard_id ValidatorsByDeposit: type: object title: 💎 Deposit properties: deposit_address: $ref: '#/components/schemas/ExecutionLayerAddress' required: - deposit_address ValidatorsByWithdrawal: type: object title: 💎 Withdrawal properties: withdrawal: $ref: '#/components/schemas/AddressOrCredential' required: - withdrawal ValidatorsByEntity: type: object title: 💎 Entity description: > Select validators by their assigned entity (e.g., staking provider) and optionally a sub-entity. Entity and sub-entity names are matched exactly and are case-sensitive. properties: entity: type: string description: > The name of the entity to filter validators by (e.g., "Lido", "Coinbase"). Matching is case-sensitive; use the exact name as returned by the entities overview endpoint. sub_entity: type: string description: > Optional sub-entity name to further filter validators within the entity. Matching is case-sensitive; use the exact name as returned by the sub-entities overview endpoint. required: - entity validatorIndex: description: Validator Index type: integer minimum: 0 validatorPublicKey: type: string description: Public key of a validator pattern: ^0x[a-fA-F0-9]{96}$ validatorIndexPublicKeys: description: > An array containing either validator indices or public keys. Index and public key can be mixed in the same array. Subscribed users (Hobbyist, Business, and Scale tiers) can include up to 100 entries; free trial users and legacy subscription users (Sapphire, Emerald, Diamond) are limited to 20. type: array items: $ref: '#/components/schemas/validatorIndexPublicKey' minItems: 1 maxItems: 100 dashboardID: description: > beaconcha.in dashboard ID. You can find your dashboard ID in the URL of your dashboard page on beaconcha.in (e.g., https://beaconcha.in/dashboard/12345). type: integer x-go-type: '*int' minimum: 0 dashboardGroupID: description: >- Optional beaconcha.in dashboard group ID. If no group ID is provided, all validators in the dashboard are considered. type: integer minimum: 0 nullable: true ExecutionLayerAddress: type: string pattern: ^0x[a-fA-F0-9]{40}$ description: A standard Ethereum address (20-byte hex string with 0x prefix). AddressOrCredential: type: string pattern: ^(0x)?[0-9a-fA-F]{40}$|^(0x)?0[012][0-9a-fA-F]{62}$ description: > Either an execution layer address (20-byte hex string with 0x prefix) or a full 32-byte withdrawal credential. validatorIndexPublicKey: oneOf: - $ref: '#/components/schemas/validatorIndex' - $ref: '#/components/schemas/validatorPublicKey' 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. ````