Switch to the Blockscout Pro API

On July 1, 2026, all Blockscout API traffic moves to the Pro API. The Pro API gives you a single endpoint for 120+ chains, advanced metadata, and full REST coverage. The free tier is enough to build and test. The Builder and Pro plans add higher RPS and larger call allowances for production.

You'll need an API key. This guide covers getting one and switching from a Blockscout per-instance API, Etherscan, or Routescan. Most migrations are a base URL swap plus a key.

"Blockscout's Pro API is a clean way to integrate multiple chains with minimal friction." — Cointracker

Action required before July 1

If you use a legacy per-instance Blockscout API key (a UUID from your MyAccount dashboard, e.g. cd6bd6d9-...), that key becomes inactive on July 1 and will be removed from MyAccount. Generate a free Pro API key to replace it.

Get a Pro API key

1. Go to the Pro API portal at https://dev.blockscout.com/ and click Login.
2. Create an account with any email you can access, or sign in with Google or GitHub. This account is fully separate from your Blockscout explorer account. It does not affect Merits, tags, watchlists, or anything else. You can reuse the same email or use a different one.
3. Confirm your email. If you signed up by email, paste the activation code you receive to activate the account.
4. Open the dashboard. From here you can monitor usage, see per-call credit costs, compare plans, and manage keys.
5. Create your key. Click Create API Key, give it a name, and optionally set an expiration (leave blank for none). Copy the key and store it somewhere safe (not in a Git repo). Every key starts with the proapi_ prefix.

You can hold up to 50 keys and generate more anytime. Keys are shown once and can't be re-copied. If you lose one, just generate a new key and rotate it in.

Check the dashboard regularly to track credit usage, top calls, and chain usage.

Switching from a Blockscout per-instance API

Swap your per-instance host for the unified Pro API host (api.blockscout.com) and add your key. Use the chainid parameter to target a chain. The following example is for the blocks REST endpoint.

# Old (per-instance, Ethereum)
https://eth.blockscout.com/api/v2/blocks

# New (Pro API, Ethereum = chainid 1)
https://api.blockscout.com/1/api/v2/blocks/?apikey=proapi_xxxxxxxx

Switching from Etherscan

The Pro API is compatible with Etherscan's v2 API. Change the base URL to api.blockscout.com and use your Blockscout Pro API key. Every other parameter stays the same. This is an JSON RPC example to get block number by timestamp.

# Etherscan
https://api.etherscan.io/v2/api?apikey=YOUR_KEY&chainid=1&module=block&action=getblocknobytime&timestamp=1716196385&closest=before

# Blockscout
https://api.blockscout.com/v2/api?apikey=proapi_YOUR_KEY&chainid=1&module=block&action=getblocknobytime&timestamp=1716196385&closest=before

Switching from Routescan

Change the base URL, drop the extra network path segments Routescan requires, and add your Blockscout key. Keep the other parameters the same.

# Routescan
https://api.routescan.io/v2/network/mainnet/evm/1/etherscan/api?apikey=YOUR_KEY&module=block&action=getblocknobytime&timestamp=1716196385&closest=before

# Blockscout
https://api.blockscout.com/v2/api?apikey=proapi_YOUR_KEY&chainid=1&module=block&action=getblocknobytime&timestamp=1716196385&closest=before

Beyond JSON-RPC: REST