Rewards

Body Params
string
enum
required

The granularity of the rewards data. Use epoch for one record per validator per epoch, daily for rewards aggregated by UTC calendar day, or all_time for cumulative rewards since validator activation.

Allowed:
string
required

Lower bound of rewards data. For epoch time_rollup: accepts an epoch number as an integer (e.g. 261702) or a date string ("YYYY-MM-DD"). For daily time_rollup: accepts a date string ("YYYY-MM-DD"). Ignored for all_time time_rollup.

string
required

Upper bound of rewards data. For epoch time_rollup: accepts an epoch number as an integer (e.g. 261703) or a date string ("YYYY-MM-DD"). For daily time_rollup: accepts a date string ("YYYY-MM-DD"). Ignored for all_time time_rollup.

string

Filter using comma-separated group uuids.

string
enum
Defaults to mainnet
Allowed:
pubkeys
array of strings

A list of validator pubkeys for filtering.

pubkeys
withdrawal_addresses
array of strings

A list of withdrawal addresses or credentials for filtering.

withdrawal_addresses
page
object
boolean
Defaults to false

When true, includes a separate consensus_penalty entry in the rewards array representing attestation and sync committee penalties for the period. Defaults to false. Data availability: Penalty data is available from epoch 427295 (2026-02-12) onward. For periods before this epoch/date, no consensus_penalty entry will be present in the response regardless of whether penalties were incurred. For all_time rollups, the penalty represents the sum from epoch 427295 (2026-02-12) to present, not the validator's full lifetime.

Responses

Language
LoadingLoading…
Response
Choose an example:
application/json