Operators
Activations and withdrawals state and status
GET
This endpoint returns data on the activation and exit activity of a specific pre-materialized view (e.g. operator, deposit address etc).
Hereβs how to interpret the inputs required to operate it π
Parameter | Context |
---|---|
operatorId | The name of the entity in question. This could be deposit address, a node operator, or a pool. Please see our docs to get a better understanding of how we aggregate validators. |
stakeAction | Direction of flow. This can be either of activation or exit . |
window | The time window of aggregation. You might ask for 1d , 7d , 30d or All-time data. |
idType | The type of entity class you would like returned. You might ask for pool , poolShare , nodeOperator , depositAddress , or withdrawalAddress . Note: it is optional and can be inferred automatically for pools, pool shares and node operators. It defaults to depositAddress if it is missing and an address is provided. |
Headers
Available options:
mainnet
, holesky
Path Parameters
Query Parameters
Available options:
activation
, exit
Available options:
1d
, 7d
, 30d
, all
Response
200
application/json
Available options:
1d
, 7d
, 30d
, all
Available options:
depositAddress
, withdrawalAddress
, nodeOperator
, pool
, poolShare
, entity
, validator
, privateSet
Available options:
activation
, exit
Required range:
x > 0
Required range:
x > 0
Required range:
x > 0
Required range:
x > 0