For the complete documentation index, see llms.txt. This page is also available as Markdown.

Zcash Blockbook (WebSocket) API

GetBlock provides fast and reliable access to Zcash nodes via the Blockbook WebSocket API. Connect to the Zcash network without running your own infrastructure.

The Blockbook indexer WebSocket interface for Zcash: request/response queries (status, account info, transparent UTXOs, transactions, broadcast) plus subscriptions to new blocks and address activity over a persistent connection.

Blockbook (REST) and Blockbook (WebSocket) are provisioned as separate interfaces with their own endpoint URLs. Enabling one does not enable the other.

Base URL

wss://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>

Message Envelope

Every request carries an id chosen by the client, a method, and a params object. The server echoes the same id on the matching response, so replies can be correlated on a multiplexed connection.

{
    "id": "getblock.io",
    "method": "getInfo",
    "params": {}
}

A failed request returns an error object in place of the result:

{
    "id": "getblock.io",
    "data": {
        "error": {
            "message": "Invalid address"
        }
    }
}

Subscription notifications reuse the id from the subscription request rather than a fixed value. Give each subscription on a connection its own id so pushes can be routed by id without inspecting the payload.

Methods

Method
Description

Indexer status and the backend's consensus branch IDs

Transparent address balance and transaction history

Unspent transparent outputs for an address or xpub

Normalized transaction by txid

Broadcast a signed, serialized transaction

Subscribe to new blocks as they are connected

Subscribe to activity on a set of addresses

Not available on Zcash

Method
Behaviour
Use instead

estimateFee

Returns -32601: Method not found. Zebra implements neither estimatesmartfee nor estimatefee, so the indexer has nothing to call

The ZIP-317 conventional fee: 5,000 zatoshis per logical action, with a minimum of two actions

Zcash specifics

  • Amounts are in zatoshis, at 1e-8 ZEC.

  • Fees follow ZIP-317, not a fee market, and there is no fee estimator on any interface.

  • 75-second blocks, so block notifications arrive about eight times as often as on Bitcoin.

  • Consensus branch IDs are reported by getInfo under backend.consensus; transactions must be signed for the branch in force.

  • Transaction expiry. Zcash transactions carry an expiryheight and cannot be mined after it, so a stuck transaction must be rebuilt rather than rebroadcast.

  • Transaction versions 5 and 6 are both current; version 6 accompanies the NU6 upgrades.

Support

Last updated

Was this helpful?