Node API Overview

The Node API reference documents selected JSON-RPC methods available through W3API chain-specific node endpoints. Use it when your application needs direct access to raw blockchain node data, including blocks, transactions, balances, logs, account data, execution traces, debugging output, and cluster status.

The generated method pages are built from curated OpenRPC specifications. Those specs are the source of truth for method names, parameters, response schemas, examples, and generated endpoint pages:

• Ethereum Standard API: fern/openrpc/node-api/openrpc.json
• Ethereum Trace API: fern/openrpc/trace-api/openrpc.json
• Ethereum Debug API: fern/openrpc/debug-api/openrpc.json
• Solana Standard API: fern/openrpc/solana-api/openrpc.json

Endpoints and Requests

Node API requests use JSON-RPC 2.0 over HTTPS. Production applications call a chain-specific endpoint with a project API key:

https://rpc.ankr.com/eth/<apiKey>
https://rpc.ankr.com/solana/<apiKey>

Replace <apiKey> with your project API key. Request bodies include the JSON-RPC version, method name, positional params array, and request ID:

1
{
2
  "jsonrpc": "2.0",
3
  "method": "eth_blockNumber",
4
  "params": [],
5
  "id": 1
6
}

The interactive Try it playground uses a docs proxy to make sample requests without exposing a project API key. Production applications should call the chain-specific endpoint directly with their own project API key.

Responses and Errors

Successful JSON-RPC responses include a result value. Failed JSON-RPC responses include an error object with a code, message, and optional data field. Node API requests can also fail at the HTTP layer before or while the request reaches the backing node.

Use the chain-specific error pages when troubleshooting request shape, authentication, rate limits, method availability, or upstream node execution:

Where to Start

The Node API references are chain-specific. Select the one you’d like to interact with to view its details: