---
title: "Get network details"
method: GET
path: "/v1/networks/{network}"
tags: ["Primary Network"]
---

# Get network details

`GET /v1/networks/{network}`

Gets network details such as validator and delegator stats.

## Path parameters

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

## Response `200`

Successful response

- GetNetworkDetailsResponse
  - `validatorDetails` ValidatorsDetails, required
    - `validatorCount` number, required
    - `totalAmountStaked` string, required
    - `estimatedAnnualStakingReward` string, required — Total potential rewards from currently active validations and delegations.
    - `stakingDistributionByVersion` StakingDistribution[], required
      - `version` string, required — AvalancheGo version for the validator node.
      - `amountStaked` string, required — The total amount staked by validators using this version.
      - `validatorCount` number, required — The number of validators using this version.
    - `stakingRatio` string, required — Ratio of total active stake amount to the current supply.
  - `delegatorDetails` DelegatorsDetails, required
    - `delegatorCount` number, required
    - `totalAmountStaked` string, required

## 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)