Free Bitcoin Cash RPC (BCH)
Learn about Bitcoin Cash, a fast and low-fee blockchain for peer-to-peer transactions. Discover how it empowers global decentralized payments.
Connect to Bitcoin Cash
Access reliable, enterprise-grade endpoints that power your dApp with ultra-low latency and 99.9% uptime.
Connect to Bitcoin Cash Gateway
Make your first RPC call on Bitcoin Cash's Blockchain Gateway.
Testnet
Testnet* Rate limit enabled - perfect for testing and development. For production, we recommend to Upgrade.
Get 200 requests/second, priority support and advanced blockchain features.
Global Load Balancer
Route to nearest node
Batch RPC Calls
Multiple requests at once
Archive Nodes
Historical blockchain data
Debug & Trace
Advanced debugging
Advanced Analytics
Usage & performance
Bring Your Own RPC
Custom RPC gateways
Increase your limit and access all network features in Tatum Development Platform.
No signup. No paywalls. Just RPC that works. Great ideas come from everywhere.
With love by Tatum
Bitcoin Cash methods
Every method the Bitcoin Cash gateway accepts, grouped by interface. 42 in total, read live from the node rather than kept by hand.
Mainnet is the live Bitcoin Cash network. Every transaction it
accepts is final, and every BCH balance it
reports is real money.
Testnet answers the same methods on a network funded with tokens that have no market value. Develop there, then change the URL to Mainnet when the code is stable. Nothing else about your integration has to change.
Bitcoin Cash answers over 2 interfaces: JSON-RPC and REST. Each is listed once below with every method it accepts. The endpoints differ per network, and all of them are in the gateway list above.
What sits between you and Bitcoin Cash
A node is a machine running Bitcoin Cash with a copy of the chain. Your code cannot ask the chain directly, it asks a node. The gateway picks a healthy one for every call, so you point at one URL instead of one machine.
- One URL, nothing to run or keep patched yourself.
- Calls routed to a node that is up and in sync.
- A failing node is skipped rather than returned to you as an error.
JSON-RPC
31 methodsThe default. Every wallet, library and framework speaks it, and it is what you want unless you specifically need something else.
One POST carries a method name, its parameters and an id, and the response comes back on the same connection carrying that same id. Requests are independent, so there is no session to keep alive and nothing to reconnect, which is why it runs unchanged behind a load balancer or inside a serverless function. Send an array instead of a single object and the node works through the whole batch in one round trip.
Where it fits
- Anything your library already does for you. ethers, web3.js, viem and their equivalents all target this.
- Batching reads. One array of twenty calls costs one round trip instead of twenty.
- Stateless and serverless deployments, because nothing has to stay connected between calls.
- Historical queries, by passing a block number where you would otherwise pass latest.
Trade-offs
- It cannot push. Finding out that a block landed means polling for it, or moving to WebSocket.
- Wide log queries get refused. Page through in fixed block windows and merge the results yourself.
- Batch responses may come back in any order. Match them on id, never on position.
Enabled and tested methods
Read live from the endpoint, so this is what it actually serves today rather than what the protocol allows in principle. Anything not on this list returns a method-not-found error.
- createrawtransaction
- Builds an unsigned raw transaction from a set of inputs and outputs.
- decoderawtransaction
- Decodes a serialized transaction into readable JSON.
- decodescript
- Decodes a hex script into its assembly form and any addresses it implies.
- estimatefee
- Estimates the fee per kilobyte for confirmation within a number of blocks.
- estimatesmartfee
- Estimates the fee rate needed for confirmation within a target number of blocks.
- getbestblockhash
- Returns the hash of the current chain tip.
- getblock
- Returns a block by hash, either as a summary or with full transaction detail.
- getblockchaininfo
- Returns chain state: height, difficulty, verification progress and active soft forks.
- getblockcount
- Returns the height of the chain tip.
- getblockhash
- Returns the block hash at a given height.
- getblockheader
- Returns a block header without its transactions.
- getblockstats
- Returns per-block statistics such as fee rates, size and transaction counts.
- getchaintips
- Lists known chain tips, including stale and orphaned branches.
- getdifficulty
- Returns the current proof-of-work difficulty.
- getmempoolancestors
- Lists the unconfirmed ancestors of a transaction in the mempool.
- getmempoolcluster
- Returns the cluster of related transactions a mempool entry belongs to.
- getmempooldescendants
- Lists the unconfirmed descendants of a transaction in the mempool.
- getmempoolentry
- Returns mempool details for one transaction, including fees and dependencies.
- getmempoolfeeratediagram
- Returns the fee-rate distribution of the current mempool.
- getmempoolinfo
- Returns mempool size, memory usage and the minimum relay fee.
- getnetworkinfo
- Returns node version, protocol version and connection details.
- getrawmempool
- Lists the transaction IDs currently sitting in the mempool.
- getrawtransaction
- Returns a transaction, either serialized or decoded.
- gettxout
- Returns an unspent transaction output (UTXO), if it is still unspent.
- gettxoutproof
- Returns a Merkle proof that given transactions are included in a block.
- searchrawtransactions
- Returns transactions involving a given address.
- sendrawtransaction
- Broadcasts a signed, serialized transaction to the network.
- testmempoolaccept
- Checks whether a transaction would be accepted into the mempool, without broadcasting it.
- validateaddress
- Checks whether an address is well formed and returns what is known about it.
- verifymessage
- Verifies a message signed by the private key behind an address.
- verifytxoutproof
- Verifies a Merkle proof and returns the transactions it commits to.
Common JSON-RPC errors
What you are most likely to hit calling this interface, and what to do about it.
- -32700
- Parse error. The request body was not valid JSON. Check that the body is serialised JSON and that Content-Type is application/json.
- -32600
- Invalid request. The JSON parsed, but it is not a well-formed JSON-RPC call. Include jsonrpc, method and id fields. A batch must be a non-empty array.
- -32601
- Method not found. This node does not expose the method you called. Check the spelling and the namespace, and confirm the method is in the list above for this network. Tracing methods in particular are not enabled everywhere.
- -32602
- Invalid params. The method exists but the arguments are wrong. Check argument order and types. Most EVM methods want hex-encoded quantities, and a block parameter such as latest or a hex height.
- -32603
- Internal error. The node failed while handling an otherwise valid request. Retry with backoff. If it persists on one method, it is usually that method rather than the node.
- -32000
- Server error. A catch-all the node uses for execution failures, most often a reverted call or a request over a limit. Read the accompanying message. Execution reverted means your call failed on chain, not in transport. Narrow the block range if you are querying logs.
- HTTP 429
- Rate limited. You have exceeded the free tier request allowance. Back off and retry, batch reads into single calls, or move to a dedicated endpoint for production traffic.
- HTTP 413
- Payload too large. The request body exceeded what the node accepts. Split large batches into smaller ones.
REST
11 methodsEvery resource has its own URL, so a request is just an address you can open.
Paste it into a browser, curl it, or bookmark it. There is no body to construct and no method name to look up, and because a read is a plain GET, ordinary HTTP caching applies at the CDN and in your own client. Responses are JSON, and the path itself usually tells you what you are getting.
Where it fits
- Getting oriented on an unfamiliar chain without writing any code first.
- Caching, because a GET can be cached by anything sitting between you and the node.
- Debugging, since the request that failed is a URL you can paste to a colleague.
Trade-offs
- You get exactly what the endpoint returns. There is no way to ask for less, or for more.
- Building a full picture takes several round trips where one batched JSON-RPC call would do.
- Paths carry version prefixes and shift between node releases more readily than method names do.
Enabled and tested methods
Read live from the endpoint, so this is what it actually serves today rather than what the protocol allows in principle. Anything not on this list returns a method-not-found error.
- GET /block/{block-hash}
- Returns a block, including its transactions.
- GET /block/notxdetails/{block-hash}
- Returns a block without its transaction details.
- GET /blockhashbyheight/{height}
- Returns the block hash at a given height.
- GET /chaininfo.json
- Returns chain state: height, difficulty, verification progress and soft forks.
- GET /getutxos/{outpoint}/{outpoint}/.../{outpoint}
- Returns the unspent outputs for a list of outpoints, confirmed only.
- GET /getutxos/checkmempool/{outpoint}/{outpoint}/.../{outpoint}
- Returns the unspent outputs for a list of outpoints, counting the mempool.
- GET /headers/{block-hash}
- Returns block headers starting at a given hash.
- GET /headers/{count}/{block-hash}
- Returns a set number of block headers starting at a given hash.
- GET /mempool/contents.json
- Returns the full contents of the mempool.
- GET /mempool/info.json
- Returns mempool size, memory usage and minimum relay fee.
- GET /tx/{tx-hash}
- Returns a transaction by its hash.
Common REST errors
What you are most likely to hit calling this interface, and what to do about it.
- 400
- Bad request. A path or query parameter is malformed. Check the parameter format, and that path values are URL-encoded.
- 404
- Not found. Either the path is wrong, or the resource genuinely does not exist at that height. Confirm the path against the list above. A valid path can still 404 for pruned history on a non-archive node.
- 429
- Rate limited. You have exceeded the free tier request allowance. Back off and retry. REST responses cache well, so caching on your side removes most repeat traffic.
- 500
- Internal server error. The node failed while handling the request. Retry with backoff.
- 503
- Service unavailable. The node is starting, resyncing, or temporarily out of rotation. Retry with backoff; this is normally short-lived.
Indexed Bitcoin Cash Data Insights
Complete on-chain data access, no infrastructure to run yourself. Query wallets, tokens, NFTs, and transaction history with lightning-fast APIs.
Real-time Bitcoin Cash Alerts
Real-time webhooks for on-chain events. Stop polling the network - get instant alerts for transactions, smart contract events, and wallet activities.
Real-time Alerts for Bitcoin Cash
Receive instant webhooks for any event on Bitcoin Cash.
Notification Types on Bitcoin Cash
Discover incoming and outgoing transaction events for Bitcoin Cash addresses.
About Bitcoin Cash
What it is, and guides for building on it.
The Bitcoin Cash RPC documentation provides developers with the necessary resources to interact programmatically with the Bitcoin Cash network. This guide outlines the key API endpoints for querying transaction data, submitting new transactions, and managing wallets. Bitcoin Cash uses larger block sizes to offer faster and cheaper transactions than Bitcoin, making it ideal for peer-to-peer payments. The documentation includes examples and best practices for integrating Bitcoin Cash into decentralized applications, particularly in payments and financial services.
What's new at Tatum on Bitcoin Cash?
Notifications: Robinhood
Robinhood Chain is now live on Tatum’s Blockchain Notifications, with support for all notification types. Receive onc...
RPC Gateway: WebSockets for Arbitrum and BSC
Stop polling. Start streaming. Tatum WebSocket subscriptions push blockchain updates to your app over a persistent co...
Harmony Networks Removal
Tatum is decommissioning its hosted Harmony Mainnet S0, Harmony Testnet S0, and Harmony Devnet S0 RPC services follow...
Frequently Asked Questions
Everything you need to know about Bitcoin Cash RPC endpoints
Quick Answer: What is Bitcoin Cash RPC?
RPC (Remote Procedure Call) is the standard way to interact with the network programmatically - reading on-chain data, submitting transactions, and deploying smart contracts through JSON-RPC calls. The free tier ships 5 requests per minute with no registration required, which covers most learning and testing workflows. Production applications typically move to Tatum Premium for 200 requests per second and enterprise-grade reliability.
What is Bitcoin Cash RPC?
How do I connect to Bitcoin Cash using these RPC endpoints?
What are the rate limits for the free RPC tier?
Is Bitcoin Cash RPC free forever?
What happens if I exceed the free tier rate limit?
Can I use these Bitcoin Cash RPC endpoints with MetaMask?
Are these RPC endpoints secure?
What's the difference between mainnet and testnet RPC endpoints?
How do I troubleshoot RPC connection errors?
Can I use these endpoints in production?
Explore Other Blockchains
Discover RPC endpoints for other popular blockchain networks