GET
/
v0
/
eth
/
operators
/
{operator_id}
/
effectiveness

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 πŸ‘‡

ParameterContext
filterTypehour, day and datetime
fromStart day (integer) or datetime (e.g. from=β€œ2022-12-01”)
granularityThe size of time increments you are looking to query. Can be day / week / month / quarter / year.
sizeThe number of results included per page
idTypeThe 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.
includeA list of field names. Use it to filter the specific fields you want in the response payload

Headers

X-Rated-Network
enum<string>
Available options:
mainnet,
holesky

Path Parameters

operator_id
string
required

Query Parameters

idType
enum<string> | null
Available options:
depositAddress,
withdrawalAddress,
nodeOperator,
pool,
poolShare,
entity,
validator,
privateSet
from
Required range: x > 0
size
integer
default:
10
granularity
enum<string>
Available options:
hour,
day,
week,
month,
quarter,
year,
all
filterType
enum<string>
Available options:
hour,
day,
datetime
include
string[] | null

Response

200
application/json
page
object
required
total
integer
required
Required range: x > 0
data
object[]
required
next
string | null
required