RPC Providers

There are multiple RPC providers from which you can choose from. These providers will work as intermediaries to help you interact with the Avalanche network. You'll experience different latency levels depending on the provider's configurations. You can potentially use multiple providers for redundancy and balancing.

Mainnet RPC - Public API Server

There is a public API server that allows developers to access the Avalanche network without having to run a node themselves. The public API server is actually several AvalancheGo nodes behind a load balancer to ensure high availability and high request throughput.

Using the Public API Nodes

The public API server is at api.avax.network for Avalanche Mainnet and api.avax-test.network for Avalanche Fuji Testnet. To access a particular API, just append the relevant API endpoint, as documented here. Namely, use the following end points for each chain respectively:

HTTP

For C-Chain API, the URL is https://api.avax.network/ext/bc/C/rpc.
For X-Chain API, the URL is https://api.avax.network/ext/bc/X.
For P-Chain API, the URL is https://api.avax.network/ext/bc/P.

Note: on Fuji Testnet, use https://api.avax-test.network/ instead of https://api.avax.network/.

WebSocket

For C-Chain API, the URL is wss://api.avax.network/ext/bc/C/ws.

Note: on Fuji Testnet, the URL is wss://api.avax-test.network/ext/bc/C/ws.

Supported APIs

The public API server supports all the API endpoints that make sense to be available on a public-facing service, including APIs for the X-Chain, P-Chain, C-Chain, and full archival for the Primary Network. However, it doesn't support Index APIs, which includes the X-Chain API's getAddressTxs method.

For a full list of available APIs see here.

Limitations

The public API only supports C-Chain WebSocket API calls for API methods that don't exist on the C-Chain's HTTP API.

For batched C-Chain requests on the public API node, the maximum number of items is 40. We're working on to support a larger batch size.

The maximum number of blocks to serve per getLogs request is 2048, which is set by api-max-blocks-per-request.

Sticky Sessions

Requests to the public API server API are distributed by a load balancer to an individual node. As a result, consecutive requests may go to different nodes. That can cause issues for some use cases. For example, one node may think a given transaction is accepted, while for another node the transaction is still processing. To work around this, you can use 'sticky sessions', as documented here. This allows consecutive API calls to be routed to the same node.

If you're using AvalancheJS to access the public API, simply set the following in your code:

avalanche.setRequestConfig("withCredentials", true);

Availability

Usage of public API nodes is free and available to everyone without any authentication or authorization. Rate limiting is present, but many of the API calls are cached, and the rate limits are quite high. If your app is running up against the limits, please contact us or try using a community RPC provider.

Support

If you have questions, problems, or suggestions, join the official Avalanche Discord.

Note

Provided for informational purposes only, without representation, warranty or guarantee of any kind. None of this is as an endorsement by the Avalanche Foundation Limited, Ava Labs, Inc. or any of their respective subsidiaries or affiliates, nor is any of this investment or financial advice. Please review this Notice and conduct your own research to properly evaluate the risks and benefits of any project.

ANKR

Mainnet

Standard EVM API, the URL is https://rpc.ankr.com/avalanche.
For C-Chain API, the URL is https://rpc.ankr.com/avalanche-c. On ANKR the C-Chain API doesn't support standard EVM APIs. For that use the Standard EVM API.
For X-Chain API, the URL is https://rpc.ankr.com/avalanche-x.
For P-Chain API, the URL is https://rpc.ankr.com/avalanche-p.

Testnet (Fuji)

Standard EVM API, the URL is https://rpc.ankr.com/avalanche_fuji.
For C-Chain API, the URL is https://rpc.ankr.com/avalanche_fuji-c. On ANKR the C-Chain API doesn't support standard EVM APIs. For that use the Standard EVM API.
For X-Chain API, the URL is https://rpc.ankr.com/avalanche_fuji-x.
For P-Chain API, the URL is https://rpc.ankr.com/avalanche_fuji-p.

Features:

Archive Data Included.
Automatic geo-routing across North America, Europe, and Asia.

Note: soft limited to 1 million daily requests per IP or referring domain. Batch calls limited to 1000.

For C-Chain RPC Endpoint ETH, the URL is https://ava-mainnet.public.blastapi.io/ext/bc/C/rpc
For C-Chain RPC Endpoint AVAX, the URL is https://ava-mainnet.public.blastapi.io/ext/bc/C/avax
For X-Chain RPC Endpoint, the URL is https://ava-mainnet.public.blastapi.io/ext/bc/X
For P-Chain RPC Endpoint, the URL is https://ava-mainnet.public.blastapi.io/ext/P

Websockets

For C-Chain WSS Endpoint, the URL is wss://ava-mainnet.public.blastapi.io/ext/bc/C/ws

Testnet (Fuji)

HTTP

For C-Chain RPC Endpoint ETH, the URL is https://ava-testnet.public.blastapi.io/ext/bc/C/rpc
For C-Chain RPC Endpoint AVAX, the URL is https://ava-testnet.public.blastapi.io/ext/bc/C/avax
For X-Chain RPC Endpoint, the URL is https://ava-testnet.public.blastapi.io/ext/bc/X
For P-Chain RPC Endpoint, the URL is https://ava-testnet.public.blastapi.io/ext/P

Websockets

For C-Chain WSS Endpoint, the URL is wss://ava-testnet.public.blastapi.io/ext/bc/C/ws

BlockSpaces

BlockSpaces supports the C-Chain.

HTTP

For C-Chain RPC Endpoint AVAX, the URL is https://web3endpoints.com/avax-mainnet

Chainstack

Chainstack supports the C-Chain, X-Chain, P-Chain, and the Fuji Testnet.

Features:

Globally distributed infrastructure for optimal performance.
Crypto payments natively.
24/7 customer support.

Mainnet

HTTP

For C-Chain API, the regional elastic node URL is https://nd-123-145-789.p2pify.com/API_KEY/ext/bc/C/rpc, and the global elastic node URL is https://avalanche-mainnet.core.chainstack.com/ext/bc/C/rpc/API_KEY
For X-Chain API, the regional elastic node URL is https://nd-123-145-789.p2pify.com/API_KEY/ext/bc/X, and the global elastic node URL is https://avalanche-mainnet.core.chainstack.com/ext/bc/X/API_KEY
For P-Chain API, the regional elastic node URL is https://nd-123-145-789.p2pify.com/API_KEY/ext/P, and the global elastic node URL is https://avalanche-mainnet.core.chainstack.com/ext/P/API_KEY

Websockets

Websockets are available for the C-chain and the X-chain.

For C-Chain API, the regional elastic node URL is wss://ws-nd-123-145-789.p2pify.com/API_KEY/ext/bc/C/ws, and the global elastic node URL is wss://avalanche-mainnet.core.chainstack.com/ws/ext/bc/C/ws/API_KEY
For X-Chain API, the regional elastic node URL is wss://ws-nd-123-145-789.p2pify.com/API_KEY/ext/bc/X/events, and the global elastic node URL is wss://avalanche-mainnet.core.chainstack.com/ws/ext/bc/X/events/API_KEY

Testnet (Fuji)

HTTP

For C-Chain API, the URL is https://nd-123-145-789.p2pify.com/API_KEY/ext/bc/C/rpc
For X-Chain API, the URL is https://nd-123-145-789.p2pify.com/API_KEY/ext/bc/X
For P-Chain API, the URL is https://nd-123-145-789.p2pify.com/API_KEY/ext/P

Websockets

Websockets are available for the C-chain and the X-chain.

For C-Chain API, the URL is wss://ws-nd-123-145-789.p2pify.com/API_KEY/ext/bc/C/ws
For X-Chain API, the URL is wss://ws-nd-123-145-789.p2pify.com/API_KEY/ext/bc/X/events

DRPC

DRPC supports the C-Chain.

Mainnet

For C-Chain RPC Endpoint, the URL is https://avalanche.drpc.org

Testnet (Fuji)

For C-Chain RPC Endpoint, the URL is https://avalanche-fuji.drpc.org
Decentralized RPC nodes
Node balancing
Unlimited compute units per month on the free tier
On free-tier is available Websockets

GetBlock

GetBlock currently only supports the C-Chain.

HTTP

For C-Chain API, the URL is https://avax.getblock.io/api_key/mainnet/ext/bc/C/ws?api_key=

Note: on Fuji Testnet, the URL is https://avax.getblock.io/api_key/testnet/ext/bc/C/ws?api_key=.

Websockets

For C-Chain API, the URL is wss://avax.getblock.io/api_key/mainnet/ext/bc/C/ws?api_key=

Note: on Fuji Testnet, the URL is wss://avax.getblock.io/api_key/testnet/ext/bc/C/ws?api_key=.

Infura

Infura currently only supports the C-Chain.

HTTP

For C-Chain API, the URL is https://avalanche-mainnet.infura.io/v3/YOUR-API-KEY

Note: on Fuji Testnet, the URL is https://avalanche-fuji.infura.io/v3/YOUR-API-KEY.

Moralis

Moralis currently supports the C-Chain.

Mainnet

NFT API for getting NFT metadata, balances, transfers, sales and more
Token API for getting ERC20 metadata, balances, transfers, prices, burns, mints and more
Wallet API for getting wallet balances, transaction history, net worth and more
Blockchain API for getting data about blocks, transactions, logs and events
Streams API for getting real-time webhooks about any on-chain event

Features:

Free plan available
Supports all major EVM networks

Nodies

Nodies supports the C, X, P, and DFK Subnet chains.

Features:

Generous free tier
Globally distributed infrastructure in 3+ geographic regions
Decentralized and Centralized API's

HTTP

For C-Chain, the URL is https://lb.nodies.app/v1/105f8099e80f4123976b59df1ebfb433/ext/bc/C/rpc
For X-Chain, the URL is https://lb.nodies.app/v1/105f8099e80f4123976b59df1ebfb433/ext/bc/X
For P-Chain, the URL is https://lb.nodies.app/v1/105f8099e80f4123976b59df1ebfb433/ext/bc/P
For DFK-Subnet, the URL is https://lb.nodies.app/v1/105f8099e80f4123976b59df1ebfb433/ext/bc/q2aTwKuyzgs8pynF7UXBZCU7DejbZbZ6EUyHr3JQzYgwNPUPi/rpc