Broadcast
A broadcast sends a transaction to the blockchain network so that nodes can receive it and include it in the chain. In these docs, broadcast refers to submitting a signed transaction to a node or RPC endpoint so the network can propagate it and eventually confirm it. Examples and API calls that sign an unsigned transaction and broadcast it are available in the examples section.
Use broadcast when you want the wallet to sign a prepared transaction or PSBT with its underlying key and publish it to the blockchain. The endpoint accepts a signed or partially signed PSBT (Bitcoin or Litecoin) or an unsigned transaction payload for many other chains. When applicable, the wallet service signs the transaction and broadcasts it to the network. See the examples for request formats and chain‑specific details.
What endpoint should I use for my transactions?
- Transfer
-
Use the Transfer Asset endpoint for native tokens, ERC‑20/721 assets, SPL tokens, Cardano assets, and similar transfers. This endpoint:
- Creates a wallet transfer request
- Requires user‑action signing
- Supports fee sponsorship
- Supports idempotency through
externalId - Enforces policy approvals
- Provides status tracking and indexing (for example,
txHash,dateConfirmed)
- Broadcast (Sign and Broadcast)
-
Use the Broadcast Transaction endpoint when you have built a raw or serialized transaction, or when you need to send arbitrary smart‑contract calls, mint tokens, or deploy contracts. This endpoint signs the transaction with the wallet key and broadcasts it. It also returns the request status and
txHash. - Sign (Generate Signature)
-
Use Generate Signature only when you need an off‑chain signature and do not want to broadcast anything. This endpoint is deprecated in favor of the Keys API and no longer submits transactions to the chain.