Transfer

A Transfer request includes a payload that defines the asset type, destination address, amount, and any asset-specific fields. The request is subject to permissions and may trigger policies such as approvals, screening, or fee sponsorship. The API returns a Transfer object that includes status information, txHash, fees, and timestamps.Use a Transfer when you need a high-level, tracked asset movement that integrates with policies, approvals, and audit visibility.

Transfer Asset

Use the Transfer Asset endpoint when you want IBM Digital Asset Haven to construct and handle the transaction for a standard asset transfer. This endpoint supports:

• Native tokens and common asset standards such as ERC‑20, ERC‑721, SPL, and Cardano assets.
• Policy enforcement and approval workflows.
• Fee sponsorship.
• Idempotency through the externalId field.
• Status tracking and indexing, including txHash and dateConfirmed.

This endpoint requires user action signing and produces a Wallet Transfer Request.

Broadcast Transaction (Sign and Broadcast)

Use the Broadcast Transaction endpoint when you have already created a serialized or raw transaction. This is appropriate when:

• You need to call arbitrary smart contract functions.
• You are minting assets, deploying contracts, or performing advanced transactions.
• You want to control transaction assembly, gas parameters, or nonce management.

This endpoint signs the transaction with the Wallet key and broadcasts it to the network. It also returns request status information and the resulting txHash.

Generate Signature (Deprecated Wallet Endpoint)

Use Generate Signature only when you need an off-chain signature that will not be broadcast. This endpoint is deprecated in favor of the Keys API. It returns a signature but does not submit anything to the blockchain.See Sign and the Keys API documentation for current best practices.