Arbitrum One
Arbitrum One
Bereit, das in der Produktion aufzurufen?
Das Free-Tier deckt persönliche Projekte ab. Pay-as-you-go skaliert ohne Karte.
Arbitrum One
Das Free-Tier deckt persönliche Projekte ab. Pay-as-you-go skaliert ohne Karte.
TheRPC exposes Arbitrum One through a fully standard JSON-RPC 2.0 API, so any Ethereum-compatible client or library works against chain ID 42161 without custom code. The service is built on four principles: standard HTTP and WebSocket endpoints under arbitrum.therpc.io, API-key authentication on every request, a unified response format identical across all calls, and cross-network compatibility — the same request shape and tooling you use for Arbitrum One carries over to every other network TheRPC serves, so you only ever swap the endpoint host.
The HTTP endpoint is the right choice for single requests and straightforward integrations against Arbitrum One — reading a balance, fetching a block, estimating gas, or submitting a signed transaction to the sequencer. Each call is a self-contained POST, which keeps server-side stateless backends and serverless functions simple. See the HTTP/Curl guide for ready-to-run examples.
The WebSocket endpoint is ideal for subscriptions and real-time data on Arbitrum One. Because the sequencer issues sub-second soft confirmations, a persistent connection lets you react to new heads, logs, and pending transactions the moment they appear instead of polling. See the eth_subscribe reference for subscription examples.
Every call to the Arbitrum One API uses the JSON-RPC 2.0 request format. Four fields make up each request: jsonrpc, which is always the string "2.0"; method, the RPC method name such as eth_blockNumber; params, an array of arguments (empty when the method takes none); and id, a client-chosen identifier that lets you match responses to requests.
Every response from the Arbitrum One API follows the same consistent structure: a jsonrpc version field, the matching id from your request, and then either a result field on success or an error object on failure. This predictability means you can write one response handler that works across every method and namespace.
Every request to the Arbitrum One endpoint must carry your API key in the Authorization header using the Bearer scheme. The key both authenticates you and ties usage to your plan's quotas. See the full Authentication guide for setup, environment-variable handling, and security best practices.
Arbitrum One methods on TheRPC fall into two groups. Standard methods cover everyday work: eth_ for the core protocol (balances, blocks, transactions, contract calls on chain 42161), net_ for network status, and web3_ for utility helpers. Advanced methods unlock deeper analysis: debug_ for opcode-level debugging of ArbOS execution, trace_ for full transaction and block call traces, and txpool_ for inspecting the sequencer's pending pool. Each prefix links through to the specific method documentation on the All Methods page.
The Arbitrum One API returns the five standard JSON-RPC error codes: -32700 for a parse error (malformed JSON), -32600 for an invalid request, -32601 when the method is not found, -32602 for invalid parameters, and -32603 for an internal error. Always inspect the error field before reading result. See the FAQ for detailed error-handling strategies, including retry and backoff patterns.
arbitrum.therpc.io endpoint