Skip to main content
BOTScan, BOT Chain’s block explorer, runs on Blockscout and serves two HTTP APIs: a REST API (v2) and an Etherscan-compatible API. Both need no API key. Every example on this page was run against testnet on 2026-10-01. BOT Chain doesn’t publish rate limits for these APIs. Cache responses and back off on errors.

REST API (v2)

Pagination

List endpoints return page, page_size, total_pages and total_count. Pass page and page_size as query parameters. The default page size is 50.
address-transactions.sh
On 2026-10-01 BOTScan ignored the type and filter query parameters on /transactions. Filter results in your own code.

Examples

The token info call returns JSON like this (trimmed to the main fields):
response.json
Ignore exchange_rate and coin_price on testnet. On 2026-10-01 the testnet explorer reported a price for tBOT, which has no real-world value.

Etherscan-style API

Use this API with tools built for Etherscan. Requests take module and action query parameters. Responses have status, message and result fields.

Read event logs

This is the main workaround for eth_getLogs being documented as disabled on the RPC. It returns up to 1,000 logs per request. Use page and offset to read more.
get-logs.sh
topic0 above is the hash of Transfer(address,address,uint256). To filter by two topics, also pass an operator such as topic0_1_opr=and. Without it, BOTScan returns Required query parameters missing: topic0_1_opr. See Use the BOTScan API.

More examples

The balance call returns:
response.json

Verify contracts

Foundry and Hardhat verify contracts through the Etherscan-style endpoint. Use --verifier blockscout and the /api/ URL. See the quickstart.

Known limitations

Why you need the explorer for logs.

Contract addresses

Addresses to query.
Last modified on October 2, 2026