Skip to main content
A transfer is a Wallet Transfer Request to move an asset from a wallet to a destination address. A transfer request creates an action that moves native tokens or on-chain assets (ERC-20, ERC-721, SPL, etc.) from a specified wallet to a recipient. It requires the transfer payload (kind, destination, amount, and any asset-specific fields), appropriate permissions, and may trigger policies (approvals, screening, fee sponsorship). The API returns a transfer object with status, txHash, fees, and timestamps. Use Transfer when you want a high-level, tracked asset transfer. What endpoint should I use for my transactions?
  • Transfer: call the Transfer Asset endpoint for native tokens, ERC-20/721, SPL, Cardano assets, etc. It creates a wallet transfer request, requires user action signing, supports fee sponsorship, idempotency via externalId, policy approvals, status tracking, and indexing (txHash, dateConfirmed).
  • Broadcast (Sign & Broadcast): use the Broadcast Transaction endpoint when you’ve built a raw/serialized transaction (or need to call arbitrary smart contract functions, mint, deploy contracts). This endpoint signs the transaction with the wallet key and broadcasts it; it also returns request status and txHash. See Broadcast.
  • Sign (Generate Signature): use Generate Signature only when you need an off-chain signature (no broadcast). Note this wallet endpoint is deprecated in favor of the Keys API; it does not submit anything to the chain. See Sign.
⌘I