Hardware Wallet

Get access to multiple blockchain protocols, coins, tokens and layers without the hassle of setting up a single node. Our suite combines all the tools and features a hardware wallet provider needs.
Securely broadcast signed transactions, access accurate data on balances, and get notifications for new events on the transaction.

100+ REST APIs
35+ Networks
99.99% Uptime
Start on the free plan Let's discuss your project

Some of the features you can use

HD wallet (xPub, yPub, zPub) data

Using the API endpoints in Blockchain Data you can sync HD wallets, obtain HD wallet details, list HD wallet transactions, list HD Wallet UTXOs and more.

Get callback notifications

Blockchain Events allow you to set callback notifications (webhooks) whenever there are any deposits or withdrawals to or from your addresses that you would like to be notified about.

Broadcast locally signed transaction

With Blockchain Tools you can securely broadcast locally signed transactions using a single endpoint, without the need of having self hosted nodes.

Obtain data from multiple blockchains

Get details on confirmed balance, total coins received and spent, as well as a list of all UTXOs and use them to prepare transactions. Derive all possible addresses, get all previous transactions and calculate balances.

The benefits of using Crypto APIs

Developed to save time. Designed to be robust.

Save on development time

Leverage the power of a proven blockchain infrastructure trusted by industry leaders. Integrate once, go to market in days.

Reduce maintenance costs

Our flexible pricing plans offer the best cost to performance ratio. Get access to full product suite and features. Upgrade or downgrade anytime.

Enterprise-grade security

We apply encryption to REST, encryption to memory, and encryption in transit on all sensitive data. We are fully ISO 27001 certified.

All-in-one dashboard

One dashboard for all of your crypto operations. Get API keys, generate addresses, setup webhooks, monitor failed requests, callbacks and more.

How to connect a hardware wallet

1

Read the xPub from the device

The device exports a public key; that is all the API needs to derive addresses.

2

Show balances and history

Read positions and full activity without the device being connected.

3

Build the transaction

Prepare an unsigned transaction the device can display and verify.

4

Sign on the device

The user approves on hardware; you broadcast the signed result.

You might also be interested in

AI Compatibility
Contracts
Verify Address
Transaction Simulator
Dedicated Nodes

Frequently Asked Questions

HD Wallets

Which blockchains does the Crypto APIs HD Wallets Management (xPub sync) API support?

The HD Wallet (xPub/yPub/zPub) sync API supports the EVM chains (such as Ethereum, Ethereum Classic, BNB Smart Chain, Tron), the UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), and XRP. You import an extended public key and Crypto APIs derives and syncs its addresses and transactions for you.

Does the HD Wallets Management API support Solana?

No. HD wallet (xPub/yPub/zPub) sync is not available for Solana. HD wallet coverage is limited to the EVM chains Ethereum, Ethereum Classic, BNB Smart Chain and Tron, the six UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash) and XRP. Solana is supported by other Crypto APIs products such as transactions data and blockchain events, but not by the HD wallet endpoints.

What can I do with a synced xPub through the HD Wallets API?

Once you sync an extended public key you can list all your synced HD wallets, pull the wallet's aggregated assets and balances, retrieve wallet details, and list the wallet's transactions across all derived addresses through a single integration. The sync monitors every derived address for you, so you do not have to track individual addresses manually. Syncing and deleting an xPub each carry a subscription cost, and monitored addresses incur a daily monitoring tax.

Can I derive addresses from an xPub without calling the API or exposing keys?

Yes. Crypto APIs provides address-derivation utilities in the blockchain tools family that generate child addresses from an extended public key for EVM chains, the UTXO chains and XRP. Because HD wallets use extended public keys, derivation and wallet syncing never require your private keys. This lets you generate deposit addresses and reconcile them against a synced wallet.

Is there a free tier, and how is HD wallet usage billed?

Every API request consumes credits, with the exact amount returned in the x-credits-consumed response header and the cost varying by endpoint and blockchain. HD wallet asset and transaction reads on UTXO chains are among the heavier calls (roughly 520-530 baseline credits), and a synced xPub also adds a per-subscription cost plus daily monitoring taxes per derived address. After your monthly credit allocation is exhausted, usage continues automatically under pay-as-you-go billing. The marketing page does not state a specific free-tier allowance.

Does the Prepare Transactions API support Solana or Bitcoin?

No. The Prepare Transactions endpoint is EVM-only, covering Ethereum and other EVM-based blockchains. There is no prepare route for Solana, Bitcoin, or other UTXO/non-EVM chains on this product.

Can I prepare ERC-20 token and NFT transfers, or only native coin transfers?

Yes, both. The Prepare Transactions API supports native EVM coin transfers as well as fungible token (ERC-20) and non-fungible token (NFT) transfers from any address. It builds the unsigned transaction payload ready for you to sign locally.

How do I go from a prepared transaction to a confirmed on-chain transaction?

Prepare the unsigned EVM transaction with Prepare Transactions, sign it, then submit it with the Broadcast Signed Transaction endpoint. You can also estimate gas costs beforehand using the EVM Blockchain Fees endpoint.

Can I estimate gas fees for an EVM transaction before sending it?

Yes. CryptoAPIs provides an EVM Blockchain Fees endpoint to retrieve current fee estimates so you can set gas parameters before signing and broadcasting. This pairs directly with the Prepare Transactions workflow.

Can I test what an EVM transaction will do before broadcasting it?

Yes. CryptoAPIs offers an EVM transaction simulation endpoint that lets you preview the outcome of a transaction before it is signed and broadcast. This helps you catch failures or unexpected results without spending gas on-chain.

What is the CryptoAPIs Broadcast Transactions API and how does it work?

It lets you push a transaction you have already signed locally to the blockchain network through a single specialized endpoint. You keep your private keys on your side, sign the raw transaction offline, and CryptoAPIs relays the signed payload to a node for you. This means CryptoAPIs never handles your keys while still giving you node access for broadcasting.

Which blockchains does the Broadcast Transactions API support?

Broadcasting is available across 35+ networks. This covers EVM chains (Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, Avalanche C-Chain, Tron, Arbitrum, Base, and Optimism), UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash), plus XRP, Solana, and Kaspa.

Does the Broadcast Transactions API support Solana and Bitcoin?

Yes. Solana is supported for broadcasting locally signed transactions, as are Bitcoin and the other UTXO chains (Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash). XRP and Kaspa are also covered, alongside the EVM chains.

Can I broadcast transactions on testnets as well as mainnet?

Yes. Broadcasting works on both mainnets and testnets across the networks CryptoAPIs supports. For example EVM chains offer testnets such as Sepolia, Amoy, Fuji, Nile and Mordor, and UTXO chains such as Bitcoin, Litecoin and Dogecoin offer their standard testnets. Kaspa is currently mainnet only.

Does broadcasting a transaction with CryptoAPIs mean they hold my private keys?

No. The model is non-custodial for signing: you sign the transaction locally with your own keys and only send the already-signed transaction to the broadcast endpoint. CryptoAPIs relays that signed payload to a node and never sees or stores your private keys.