Withdrawals (beta)

Querying into when a withdrawal is expected to land.

This endpoint is still in beta. If you spot inconsistencies or unexpected results, please get in touch via [e-mail] or under #product-feedback in our Discord.

The Withdrawals endpoints offer a view into the future, relating to when a set of withdrawals are expected to land. You can use this endpoint to query withdrawals relating to:

• Pools (e.g. Rocketpool)

• Operators (e.g. Chorus One)

• Deposit addresses (e.g. 0x102f792028a56f13d6d99ed4ec8a6125de98582a)

If you are looking for stats on a specific validator index, try querying for its associated deposit address.

Withdrawals predicted by operator

Get Withdrawals Predicted By Operator

GET/v0/eth/withdrawals/predicted/operators/{operator_id}

Authorization

OAuth2PasswordBearer

Path parameters

operator_id*Operator Id

Query parameters

Header parameters

Response

200400

Successful Response

Body

application/json

page*Page

total*Total

data*Data

nextNext

Request

JavaScriptCurl

const response = await fetch('/v0/eth/withdrawals/predicted/operators/{operator_id}', {
    method: 'GET',
    headers: {},
});
const data = await response.json();

Response

{
  "page": {
    "granularity": "hour",
    "filterType": "hour"
  },
  "data": [
    {
      "id": "Lido",
      "idType": "pool",
      "validatorIndex": 262966,
      "withdrawableAmount": 1899013868,
      "withdrawalEpoch": 194148,
      "withdrawalSlot": 6212758,
      "withdrawalType": "partial"
    }
  ],
  "next": "text"
}

This endpoint gives you information about the expectation of a withdrawal fulfilment, on a per validator index level––such that if an operator is withdrawing multiple validators, the response gives you information on all the validator indices related to the operator.

Here's how to interpret the inputs required to operate it 👇

Parameter	Context
from	Start day (integer) or datetime (e.g. from=“2022-12-01”)
to	End day (integer) or datetime (e.g. from=“2022-12-01”)
size	The number of results included per page
granularity	The size of time increments you are looking to query. Can be day / week / month / quarter / year
filterType	hour, day and datetime

Withdrawals predicted by slot

Get Withdrawals Predicted By Slot

GET/v0/eth/withdrawals/predicted/slot/{withdrawal_slot}

Authorization

OAuth2PasswordBearer

Path parameters

withdrawal_slot*Withdrawal Slot

Header parameters

Response

200400

Successful Response

Body

application/json

validatorIndex*Validatorindex

withdrawalType*WithdrawalType

An enumeration.

fullpartial

withdrawableAmount*Withdrawableamount

id*Id

idType*IdType

An enumeration.

depositAddresswithdrawalAddressnodeOperatorpoolpoolShareentityvalidator

withdrawalSlot*Withdrawalslot

withdrawalEpoch*Withdrawalepoch

Request

JavaScriptCurl

const response = await fetch('/v0/eth/withdrawals/predicted/slot/{withdrawal_slot}', {
    method: 'GET',
    headers: {},
});
const data = await response.json();

Response

[
  {
    "id": "Lido",
    "idType": "pool",
    "validatorIndex": 262966,
    "withdrawableAmount": 1899013868,
    "withdrawalEpoch": 194148,
    "withdrawalSlot": 6212758,
    "withdrawalType": "partial"
  }
]

This endpoint is the inverse of the one above. Instead of the subject being an operator, the question is inverted such that the subject is a future slot. The response should return all the validators that are expected to withdraw at the specified slot, along with a bunch of useful information around those.