Operators
Operator effectiveness
GET
This endpoint returns a bunch of useful information on the historical performance of a single operator. This includes rewards (aggregate and granular), performance (effectiveness and its components), slashing history and much more. For a glossary of the variables returned see effectiveness.
Hereβs how to interpret the inputs required to operate it π
Parameter | Context |
---|---|
filterType | hour, day and datetime |
from | Start day (integer) or datetime (e.g. from=β2022-12-01β) |
granularity | The size of time increments you are looking to query. Can be day / week / month / quarter / year . |
size | The number of results included per page |
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. |
include | A list of field names. Use it to filter the specific fields you want in the response payload |
Headers
Available options:
mainnet
, holesky
Path Parameters
Query Parameters
Available options:
depositAddress
, withdrawalAddress
, nodeOperator
, pool
, poolShare
, entity
, validator
, privateSet
Required range:
x > 0
Available options:
hour
, day
, week
, month
, quarter
, year
, all
Available options:
hour
, day
, datetime