---
title: "List chains"
method: GET
path: "/v1/chains"
tags: ["EVM Chains"]
---

# List chains

`GET /v1/chains`

Lists the AvaCloud supported EVM-compatible chains. Filterable by network.

## Query parameters

- `network` 'mainnet' | 'fuji' | 'testnet'
- `feature` 'nftIndexing' | 'webhooks' | 'teleporter'

## Response `200`

Successful response

- ListChainsResponse
  - `chains` ChainInfo[], required
    - `chainId` string, required
    - `status` 'OK' | 'UNAVAILABLE', required — Status of chain nodes. Chain nodes can become temporarily `UNAVAILABLE` for several reasons, such as validator stake falling below threshold. If chain nodes are `UNAVAILABLE`, requests that rely on data from the chain nodes may return 503 errors.
    - `chainName` string, required
    - `description` string, required
    - `platformChainId` string
    - `subnetId` string
    - `vmId` string
    - `vmName` 'EVM' | 'BITCOIN' | 'ETHEREUM', required
    - `explorerUrl` string
    - `rpcUrl` string, required
    - `wsUrl` string
    - `isTestnet` boolean, required
    - `utilityAddresses` UtilityAddresses
      - `multicall` string
    - `networkToken` NetworkToken, required
      - `name` string, required — The contract name.
      - `symbol` string, required — The contract symbol.
      - `decimals` number, required — The number of decimals the token uses. For example `6`, means to divide the token amount by `1000000` to get its user representation.
      - `logoUri` string — The logo uri for the address.
      - `description` string
    - `chainLogoUri` string
    - `private` boolean
    - `enabledFeatures` string[]

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