Blockbook 0.5.0 > 0.6.0 API changes

The Divi (DIVI) Blockbook API at https://divibook.nownodes.io has been upgraded from Blockbook 0.5.0 to 0.6.0. The request and response formats stay the same; the changes below are new limits on heavy requests.

What changed

• Paging limits. page is capped at 1,000,000 and account history paging stops at 100,000 items (page × pageSize). Out-of-range values are clamped instead of being processed.
• XPUB and descriptor limits. gap is capped at 10,000, descriptors may list at most 10 change indexes, and oversized derivation scans are rejected.
• Balance history limit. A balance history request spanning more than 100,000 transactions is rejected; narrow the from/to range.
• details=basic on addresses no longer aggregates mempool transactions: unconfirmed balance fields are omitted and unconfirmedTxs is the raw mempool count.
• Broadcast body limit. POST /sendtx/ accepts bodies up to 8 MiB.
• Socket.IO removed. The legacy Socket.IO interface is no longer available; use the REST API or the Blockbook WebSocket API.

Added methods

No REST methods were added for this chain. The new GET /api/v2/contract/{contract} route works on Ethereum-type networks only and returns an error here.

Modified methods

• GET /api/v2/block/{blockId} — Get a block by height or hash.
• POST /api/v2/sendtx/ — Broadcast a raw transaction using the request body.
• GET /api/v2/address/{address} — Get address/account details.
• GET /api/v2/xpub/{xpub} — Get XPUB or descriptor account details.
• GET /api/v2/utxo/{descriptor} — Get UTXOs for an address, XPUB, or descriptor.
• GET /api/v2/balancehistory/{descriptor} — Get account balance history.
• POST /api/v1/sendtx/ — Legacy broadcast transaction using the request body.

Deprecated methods

No REST methods were removed or deprecated.