Blockbook API
Overview
Blockbook is a blockchain indexer that provides a unified API for querying address balances, transaction history, UTXOs, and block data. QuickNode exposes the Blockbook API as a marketplace add-on, supporting both REST and JSON-RPC interfaces for Bitcoin Cash.
How to Access Blockbook
To enable the Blockbook add-on on your QuickNode endpoint:
- Navigate to your QuickNode Dashboard
- Select your Bitcoin Cash endpoint (or create a new one)
- Go to the Add-ons tab
- Find Blockbook in the marketplace and enable it
Once enabled, the Blockbook API is accessible via your endpoint URL using the add-on path: /addon/1118/api/v2/
Supported Interfaces
REST API
The REST API provides a familiar HTTP interface with path and query parameters for querying blockchain data.
Base path: /addon/1118/api/v2/
Example:
curl -X GET \
"https://YOUR_QUICKNODE_ENDPOINT_HERE.com/addon/1118/api/v2/address/bitcoincash:qr69gudr25kgz2fk9nk5wz0dltfzh5z8u3p0gyvxa?details=txids"
JSON-RPC API
The JSON-RPC API wraps Blockbook methods behind standard JSON-RPC calls (e.g., bb_getAddress, bb_getTx). This is useful if your application already uses JSON-RPC for other blockchain interactions.
Example:
curl -X POST \
"https://YOUR_QUICKNODE_ENDPOINT_HERE.com" \
-H "Content-Type: application/json" \
--data '{"method":"bb_getAddress","params":["bitcoincash:qr69gudr25kgz2fk9nk5wz0dltfzh5z8u3p0gyvxa",{"page":1,"size":1000,"details":"txids"}],"id":1,"jsonrpc":"2.0"}'
REST to RPC Method Mapping
| REST Endpoint | JSON-RPC Method |
|---|---|
GET /api/v2/address/{address} | bb_getAddress |
GET /api/v2/balancehistory/{address} | bb_getBalanceHistory |
GET /api/v2/block-index/{blockHeight} | bb_getBlockHash |
GET /api/v2/block/{blockHash} | bb_getBlock |
GET /api/v2/tx/{txid} | bb_getTx |
GET /api/v2/tx-specific/{txid} | bb_getTxSpecific |
GET /api/v2/utxo/{addressOrXpub} | bb_getUTXOs |
GET /api/v2/xpub/{xpub} | bb_getXpub |
GET /api/v2/tickers-list/ | bb_getTickersList |
GET /api/v2/tickers/ | bb_getTickers |
POST /api/v2/sendtx/ | bb_sendTx |
We ❤ Feedback!
If you have any feedback or questions about this documentation, let us know. We'd love to hear from you!