List validators

get

https://glacier-api.avax.network/v1/networks/{network}/validators

Lists details for validators. By default, returns details for all validators. Filterable by validator node ids and minimum delegation capacity.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

network

string

enum

required

Either mainnet or a testnet.

Allowed:

Query Params

pageToken

string

A page token, received from a previous list call. Provide this to retrieve the subsequent page.

pageSize

integer

1 to 100

Defaults to 10

The maximum number of items to return. The minimum page size is 1. The maximum pageSize is 100.

nodeIds

string

A comma separated list of node ids to filter by.

sortBy

string

enum

Which property to sort by, in conjunction with sortOrder.

Note: Delegation fee is only available for mainnet validators. Set subnetId to 11111111111111111111111111111111LpoYY to use this option.

Allowed:

sortOrder

string

enum

The order by which to sort results. Use "asc" for ascending order, "desc" for descending order. Sorted by timestamp or the sortBy query parameter, if provided.

Allowed:

validationStatus

string

enum

Validation status of the node.

Allowed:

minDelegationCapacity

string

The minimum delegation capacity, in nAVAX, used to filter the set of nodes being returned. Accepts values between 0 and 720,000,000,000,000,000

maxDelegationCapacity

string

The maximum delegation capacity, in nAVAX, used to filter the set of nodes being returned. Accepts values between 0 and 720,000,000,000,000,000.

minTimeRemaining

number

0 to 2147483647

The minimum validation time remaining, in seconds, used to filter the set of nodes being returned.

maxTimeRemaining

number

0 to 2147483647

The maximum validation time remaining, in seconds, used to filter the set of nodes being returned.

minFeePercentage

number

2 to 100

The minimum fee percentage, used to filter the set of nodes being returned. If this field is populated no subnet validations will be returned, as their fee percentage is null, since subnet delegations are not supported. Default is 2.0, as per the Avalanche spec.

maxFeePercentage

number

2 to 100

The maximum fee percentage, used to filter the set of nodes being returned. If this field is populated no subnet validations will be returned, as their fee percentage is null, since subnet delegations are not supported. Default is 100.0.

minUptimePerformance

number

0 to 100

The minimum node uptime performance percentage, which represents node health, used to filter the set of nodes being returned Default is 90.

maxUptimePerformance

number

0 to 100

The maximum node uptime performance percentage, which represents node health, used to filter the set of nodes being returned. Default is 100.

subnetId

string

The subnet ID to filter by. If not provided, then all subnets will be returned.

Responses

200Successful response

400Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error.

401When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401.

403When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403.

404The error is mostly returned when the client requests with either mistyped URL, or the passed resource is moved or deleted, or the resource doesn't exist.

429This error is returned when the client has sent too many, and has hit the rate limit.

500The error is a generic server side error that is returned for any uncaught and unexpected issues on the server side. This should be very rare, and you may reach out to us if the problem persists for a longer duration.

502This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server.

503The error is returned for certain routes on a particular Subnet. This indicates an internal problem with our Subnet node, and may not necessarily mean the Subnet is down or affected.