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

# Introduction

> Overview of the Queue APIs — track Ethereum's staking queues at network and validator level

## Overview

Every state change in Ethereum staking passes through a queue: deposits wait to become active stake, exits wait to leave the active set, and withdrawn ETH waits for the sweep to credit it. The Queue APIs expose all of these queues — network-wide and per validator — with sizes, balances, churn rates, and estimated processing times.

<Note>
  **API Endpoints:** This section covers [`/api/v2/ethereum/queues`](/api-reference/ethereum/queues) for network-wide queue statistics and [`/api/v2/ethereum/validators/queues`](/api-reference/ethereum/validators/queues) for per-validator queue positions.
</Note>

<Info>
  Queue data reflects the **current** state of the chain, and processing times are estimates based on the current churn rate. Balance values are returned in wei (1 ETH = 10¹⁸ wei).
</Info>

***

## Use Case Guides

<CardGroup cols={2}>
  <Card title="Estimate Queue Wait Times" icon="clock" href="/use-cases/queue-wait-times">
    Activation and exit ETAs from queue lengths and churn rates — for customer communication and operations planning.
  </Card>

  <Card title="Staking Inflows & Outflows" icon="arrow-right-arrow-left" href="/use-cases/staking-inflows-outflows">
    Measure pending ETH in transit — deposits awaiting activation and exits awaiting redemption.
  </Card>
</CardGroup>

***

## The Queues at a Glance

Use the network snapshot to compare pending inflows, outflows, withdrawal processing, consolidations, and compounding credential switches at the same point in time. See the [network queue API reference](/api-reference/ethereum/queues).

***

## Choosing the Right Endpoint

| Endpoint                                                       | Best For                                               | Response                                |
| -------------------------------------------------------------- | ------------------------------------------------------ | --------------------------------------- |
| **Network Queue Overview** (`/api/v2/ethereum/queues`)         | Network totals: queue sizes, churn, overall wait times | Single object, one entry per queue      |
| **Validator Queue ETA** (`/api/v2/ethereum/validators/queues`) | Queue positions and ETAs for selected validators       | Paginated list, one entry per validator |

### Use the Network Queue Overview endpoint when you need:

* Network-wide queue lengths and total pending balances
* Overall activation/exit wait-time estimates
* A demand signal for staking analytics

### Use the Validator Queue ETA endpoint when you need:

* Individual activation or exit ETAs for specific validators
* Queue positions for your own fleet — by index, public key, `dashboard_id`, or (on [Scale & Enterprise plans](https://beaconcha.in/pricing)) withdrawal credential, deposit address, or entity
* Validators still in the deposit queue: select them by public key; `index` is `null` until activation

***

## Quick Start: Network Queue Snapshot

```bash theme={null}
curl --request POST \
  --url https://beaconcha.in/api/v2/ethereum/queues \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/vnd.beaconcha.in.v2.1+json' \
  --data '{"chain": "mainnet"}'
```

```json theme={null}
{
  "data": {
    "deposit_queue": {
      "deposit_count": 1184,
      "deposit_balance": "37888000000000000000000",
      "topup_count": 243,
      "topup_balance": "1850000000000000000000",
      "estimated_processed_at": {
        "epoch": 454155,
        "timestamp": 1781099520
      },
      "churn": {
        "amount": "256000000000000000000",
        "interval_seconds": 384
      }
    },
    "exit_queue": {
      "count": 420,
      "balance": "13440000000000000000000",
      "estimated_processed_at": {
        "epoch": 454053,
        "timestamp": 1781060352
      },
      "churn": {
        "amount": "256000000000000000000",
        "interval_seconds": 384
      }
    },
    "manual_withdrawal_queue": {
      "count": 310,
      "balance": "5120000000000000000000",
      "estimated_processed_at": {
        "epoch": 454210,
        "timestamp": 1781120640
      }
    },
    "withdrawal_sweep": {
      "estimated_sweep_delay": 777600,
      "last_swept_validator_index": 1284503
    },
    "finality": "not_finalized"
  }
}
```

The full response also includes the `consolidation_queue` and `compounding_switch_queue` (omitted above). See the [network queue API reference](/api-reference/ethereum/queues) and [Estimate Queue Wait Times](/use-cases/queue-wait-times).

***

## Related Resources

* [Estimate Queue Wait Times](/use-cases/queue-wait-times) — Read queue statistics and turn them into ETAs
* [Staking Inflows & Outflows](/use-cases/staking-inflows-outflows) — Measure pending ETH in transit
* [Understanding Validator Queues](/faqs/understanding-validator-queues) — How the queues work at the protocol level
* [Deposit Process](/faqs/deposit-process) — The full lifecycle of a deposit
* [How Withdrawals Work](/faqs/how-withdrawals-work) — Eligibility delay and the withdrawal sweep

<Tip>
  API references: [Network Queue Overview](/api-reference/ethereum/queues) and [Validator Queue ETA](/api-reference/ethereum/validators/queues).
</Tip>