Sonic (S) API Documentation

Sonic

Sonic (S) is an EVM-compatible Layer 1 secured by a proof-of-stake, DAG-based asynchronous Byzantine fault-tolerant consensus mechanism, with mainnet launched on December 18, 2024. Solidity and other EVM languages compile to EVM bytecode against account-based state, while full nodes validate transactions and maintain balances, contract code, storage, blocks, receipts, and logs. Because Sonic preserves EVM execution semantics while using its own consensus layer, standard Ethereum transaction formats, tooling, and JSON-RPC conventions remain the shared application-facing baseline.

Sonic API Methods and Endpoints

NOWNodes exposes Sonic's interface, plus a few others, depending on what your integration needs: JSON-RPC for reading chain state and broadcasting transactions, and Trace/Debug for step-level execution analysis. Archive mode extends any of these to historical states and data beyond standard retention.

Browse the interfaces below for endpoint details, request parameters, response formats, and integration examples. Create an API key, select Mainnet or Testnet, choose the required interface, and start sending requests from your application.

Weighing Sonic RPC providers against each other? Read the comparison guide on our blog — this page stays focused on integration reference.