cURL

curl is the fastest way to poke at OP Mainnet without pulling in an SDK — ideal for sanity-checking your endpoint, debugging a malformed payload, or scripting a quick query in a shell or CI job. Every JSON-RPC call is an HTTP POST carrying a Content-Type: application/json header and a JSON body. Your API key lives in the URL path: https://optimism.therpc.io/YOUR_API_KEY. Since OP Mainnet is EVM-equivalent (chain ID 10), the same eth_* methods you would use on Ethereum L1 work here.

There are two ways to authenticate against OP Mainnet: put the key directly in the URL path (https://optimism.therpc.io/YOUR_API_KEY), or send it as a Bearer token in the Authorization header. Either way, the request itself must be an HTTP POST with Content-Type: application/json — JSON-RPC does not accept GET.

Basic Usage

1curl -X POST \
2  -H "Content-Type: application/json" \
3  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' \
4  https://optimism.therpc.io/YOUR_API_KEY

Authentication

1curl -X POST \
2  -H "Content-Type: application/json" \
3  -H "Authorization: Bearer YOUR_API_KEY" \
4  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' \
5  https://optimism.therpc.io/YOUR_API_KEY

Common Operations

1curl -X POST \
2  -H "Content-Type: application/json" \
3  --data '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0x742d35Cc6634C0532925a3b844Bc454e4438f44e","latest"],"id":1}' \
4  https://optimism.therpc.io/YOUR_API_KEY

1curl -X POST \
2  -H "Content-Type: application/json" \
3  --data '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b"],"id":1}' \
4  https://optimism.therpc.io/YOUR_API_KEY

cURL

Basic Usage

Authentication

Common Operations

准备好在生产环境中调用了吗？

cURL

Basic Usage

Authentication

Common Operations