Skip to main content
You need an API key first. If you do not have one, set it up here.
1

Call the API

This reads the native ETH balance of an address on Ethereum. Replace YourApiKey with your key, then run it in your command line:
  • chainid: selects the chain. E.g. 1 (Ethereum).
  • module and action: choose the endpoint. E.g. account and balance.
  • address: the account you are querying. E.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045.
  • tag: the block to read the balance at. E.g. latest.
  • apikey: your API key. Replace YourApiKey with your API key.
Alternatively, you can open the API playground and paste the example values in blue to call the endpoint.
The same key and endpoint work on every chain, just switch the chainid. For example, set chainid=42161 to read the same address on Arbitrum. See Supported chains for the full list.
Your key counts against your plan rate limits, so treat it like a credential. See Keep your key secure below.
2

Read the response

  • status: 1 on success, 0 on error.
  • message: OK on success, NOTOK on error.
  • result: the data. Here, the balance in wei. Divide by 10^18 for ETH. On error, result holds the cause. See Common error messages.

​
Keep your key secure

Your key counts against your rate limits, so treat it like a credential.
Never commit keys to public repositories or ship them in client-side code. Route API calls through your own backend instead.
  • Store keys in environment variables or a secrets manager, not in source files.
  • Rotate a key if it leaks: stop using the exposed key, remove it from your API dashboard, and create a new one there.

Rate Limits

The calls per second and daily limits for each plan.

Common Use Cases

Find the right endpoints for what you are building.