Crypto Exchange

Yes. Solana is a supported chain for Blockchain Events on both mainnet and devnet, alongside XRP and Kaspa. You can subscribe to events and receive callbacks for Solana activity through the same unified subscription flow used for the EVM and UTXO chains.

You can subscribe to confirmed coin (native) transactions, unconfirmed coin transactions, internal transactions, and token transactions for an address, as well as newly mined blocks. Confirmed coin, internal, and token transaction events also offer an each-confirmation variant that fires on every confirmation. For UTXO chains, callbacks report direction (incoming or outgoing) based on input/output address matching.

Events are delivered as HTTPS POST callbacks (webhooks) to a URL you register. The callback URL must use HTTPS and match a domain you verify in the Dashboard beforehand. You can optionally set a callback secret key so each request carries an HMAC-SHA256 x-signature header you can verify, and every callback includes an idempotencyKey so you can safely deduplicate.

CryptoAPIs retries failed callbacks with exponential backoff. Each callback allows a 5-second response timeout, and up to 5 retries follow roughly a 5, 10, 20, 40, and 80-minute schedule. If all retries fail, every subscription sharing that event type and callback URL is marked disabled, so you should monitor delivery and re-activate subscriptions as needed.

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.

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.

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.

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.

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.

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.

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.