Skip to main content
POST
💎 Sub Entities

Authorizations

Authorization
string
header
required

Authorization header with value: Bearer YOUR_TOKEN. Refer to the API Keys section to create your API key.

Body

application/json
entity
string
required

The name of the entity to retrieve sub-entities for (e.g., "Lido", "Coinbase"). Matching is case-sensitive.

range
Fixed Window · object
required
chain
enum<string>
default:mainnet

The Ethereum chain to query.

Available options:
mainnet,
hoodi
cursor
string
default:""

Cursor value for pagination. See our pagination guide for more details.

page_size
integer
default:10

The number of items to return per page.

Required range: 1 <= x <= 10
sort_by
enum<string>
default:net_share

The field to sort sub-entities by.

  • beaconscore: Sort by BeaconScore (validator efficiency)
  • net_share: Sort by network share (default)
  • validator_count: Sort by number of validators
Available options:
beaconscore,
net_share,
validator_count
sort_order
enum<string>
default:desc

The sort order for the results.

  • asc: Ascending order (lowest first)
  • desc: Descending order (highest first, default)
Available options:
asc,
desc

Response

Successful response.

Response containing an overview of sub-entities for a given entity with their validator count, BeaconScore, and net share.

data
object[]
required
last_updated
integer
required

Unix timestamp indicating when the sub-entities data was last computed. The underlying data is precomputed and updated hourly.

Required range: x >= 0
range
object
required

The time span actually covered by the returned results — from the first to the last matching data point — specified in slots, epochs, and Unix timestamps.

This reflects the data that was found, not the range that was queried. When no data is found, it falls back to the requested range, or to the full available history if no range was given.

paging
object