---
title: "List L1 validators"
method: GET
path: "/v1/networks/{network}/l1Validators"
tags: ["Primary Network"]
---

# List L1 validators

`GET /v1/networks/{network}/l1Validators`

Lists details for L1 validators. By default, returns details for all active L1 validators. Filterable by validator node ids, subnet id, and validation id.

## Path parameters

- `network` 'mainnet' | 'fuji' | 'testnet', required

## Query parameters

- `pageToken` string
- `pageSize` integer
- `l1ValidationId` string
- `includeInactiveL1Validators` boolean
- `nodeId` string
- `subnetId` unknown

## Response `200`

Successful response

- ListL1ValidatorsResponse
  - `nextPageToken` string — A token, which can be sent as `pageToken` to retrieve the next page. If this field is omitted or empty, there are no subsequent pages.
  - `validators` L1ValidatorDetailsFull[], required — The list of L1 validations for the given Subnet ID, NodeId or validationId
    - `validationId` string, required — Unique L1 validation ID used network-wide to identify L1 validation until its weight is reduced to 0 i.e. removed.
    - `validationIdHex` string, required — Unique L1 validation ID used network-wide to identify L1 validation until its weight is reduced to 0 i.e. removed. In hex format
    - `nodeId` string, required
    - `subnetId` string, required
    - `weight` number, required — Weight of the L1 validator used while sampling validators within the L1. A zero-weight L1 validator means it has been removed from the L1, and the validationID is no longer valid
    - `remainingBalance` number, required — Remaining L1 validator balance in nAVAX until inactive. It can rejoin L1 sampling by increasing balance with IncreaseL1ValidatorBalanceTx
    - `creationTimestamp` number, required — The timestamp of the transaction which created this L1 validator
    - `blsCredentials` object, required
    - `remainingBalanceOwner` BalanceOwner, required
      - `addresses` string[], required
      - `threshold` number, required
    - `deactivationOwner` BalanceOwner, required
      - `addresses` string[], required
      - `threshold` number, required
  - `blockHeight` string, required — Block height at which the L1 validator's remaining balance is calculated

## Other responses

- `400` — Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error.
- `401` — When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401.
- `403` — When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403.
- `404` — The 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.
- `429` — This error is returned when the client has sent too many, and has hit the rate limit.
- `500` — The 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.
- `502` — This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server.
- `503` — The 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.

---

[API](https://skmtc.net/avax/apis/data-api.md) · [All operations](https://skmtc.net/avax/apis/data-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/avax/data-api/versions/745a94fa47f5/schema)