Initiate a transaction

Required for transactions from MPC wallets. "acceleration" speeds up transactions with a certain nonce by adjusting the gas setting. "accountSet" is for XRP AccountSet transactions. "consolidate" combines multiple UTXO inputs into fewer outputs. "enabletoken" is for SOL. "fanout" splits UTXO inputs into many smaller outputs (UTXO coins only). "stakingLock" and "stakingUnlock" are for Stacks delegations. "transfer" is for native-asset transfers. "trustline" is for Stellar trustline transactions. Possible types include: [acceleration, accountSet, consolidate, enabletoken, fanout, stakingLock, stakingUnlock, transfer, transfertoken, trustline]

For AVAX, possible types include: addValidator, export, and import.

For XRP, possible types include: payment and accountSet. The default is payment.

For STX, type is required.

(BTC only) The number of blocks required to confirm a transaction. You can use numBlocks to estimate the fee rate by targeting confirmation within a given number of blocks. If both feeRate and numBlocks are absent, the transaction defaults to 2 blocks for confirmation.

Note: The maxFeeRate limits the fee rate generated by numBlocks.

Custom fee rate (in base units) per kilobyte (or virtual kilobyte). For example, satoshis per kvByte.

If the feeRate is less than the minimum required network fee, then the minimum fee applies. For example, 1000 sat/kvByte, a flat 1000 microAlgos, or a flat 10 drops of xrp. For XRP, the actual fee is usually 4.5 times the open ledger fee.

Note: The feeRate overrides the maxFeeRate and minFeeRate.

(BTC only) The maximum fee rate (in base units) per kilobyte (or virtual kilobyte). For example, satoshis per kvByte. The maxFeeRate limits the fee rate generated by both feeMultiplier and numBlocks.

Note: The feeRate overrides the maxFeeRate.

The unspent selection for the transaction will only consider unspents with at least this many confirmations to be used as inputs. Does not apply to change outputs unless used in combination with enforceMinConfirmsForChange.

When set to true, will enforce minConfirms for change outputs.

Custom gas price to be used for sending the transaction. Only for ETH and ERC20 tokens.

Custom gas limit to be used for sending the transaction. Only for ETH and ERC20 tokens.

Specifies the minimum count of good-sized unspents to maintain in the wallet. Change splitting ceases when the wallet has targetWalletUnspents good-sized unspents.

Note: Wallets that continuously send a high count of transactions will automatically split large change amounts into multiple good-sized change outputs while they have fewer than targetWalletUnspents good-sized unspents in their unspent pool. Breaking up large unspents helps to reduce the amount of unconfirmed funds in flight in future transactions, and helps to avoid long chains of unconfirmed transactions. This is especially useful for newly funded wallets or recently refilled send-only wallets.

Ignore unspents smaller than this amount of base units (e.g. satoshis). For doge, only string is allowed.

Ignore unspents larger than this amount of base units (e.g. satoshis). For doge, only string is allowed.

A sequenceId is a unique and arbitrary wallet identifier applied to transfers and transactions at creation. It is optional but highly recommended. With a sequenceId you can easily reference transfers and transactions—for example, to safely retry sending. Because the system only confirms one send request per sequenceId (and fails all subsequent attempts), you can retry sending without the risk of double spending. The sequenceId is only visible to users on the wallet and is not shared publicly.

(DOT only) A nonce ID is a number used to protect private communications by preventing replay attacks. This is an advanced option where users can manually input a new nonce value in order to correct or fill in a missing nonce ID value.

Set true to disable automatic change splitting.

Also see: targetWalletUnspents

Specifies a custom destination address for the transaction's change output(s)

[UTXO only] Format of the returned transaction hex serialization. legacy for serialized transaction in custom bitcoinjs-lib format. psbt for BIP174 serialized transaction

(DASH only) Specifies whether or not to use Dash's "InstantSend" feature when sending a transaction.

An optional memo for the transaction.

(AVAXC and AVAXP only) Destination chain for an AVAX import/export transaction. One of [P, C].

(AVAXC and AVAXP only) Source chain for an AVAX import/export transaction. One of [P, C].

DEPRECATED - use changeAddressType. The type of address to create for change. One of p2sh, p2shP2wsh, p2wsh, or p2tr.

Unix timestamp in seconds.nanoseconds format, denoting the start of the validity window. Only for HBAR transactions.

(ALGO/TEZOS only) Consolidation ID of this consolidation transaction.

(XRP only) Absolute max ledger the transaction should be accepted in, whereafter it will be rejected

(XRP only) Relative ledger height (in relation to the current ledger) that the transaction should be accepted in, whereafter it will be rejected

The desired effective fee rate of the accelerated transaction in base units per kilobyte (e.g. satoshi/kB), the unconfirmed transactions it depends on, and the newly created Child-Pays-For-Parent transaction. Must be higher than the current effective fee rate of the target transaction.

It is used to mark an UTXO transaction eligible for Replace-By-Fee (RBF) later.

Limits the amount of satoshis that can be used for fees in a Child-Pays-For-Parent (CPFP) transaction. CPFP transactions accelerate the targeted transaction and all of the unconfirmed transactions the targeted transaction depends on. maxFee is required for all CPFP transactions as it allows users to set a safety net that will halt CPFP attempts that exceed the expected cost.

Optional unspent selection strategy to use. One of RANDOM, FIFO or BNB.

Optional block this transaction is valid from

Optional block this transaction is valid until

Optional parameter that takes a hexadecimal value to set messagekey for an XRP accountSet transaction. Recipients field should be empty when messageKey is set.

A cryptocurrency or token ticker symbol.

The subtype of the wallet (e.g., custodialHot)

The safe the pending approval is scoped to

The organization name

The BitGo organization

The creation date of the pending approval

The date when the approval was granted

The date when the approval was last updated (any update, not just processing)

The key curve of the coin attached to this pending approval

What kind of entity the Pending Approval is tied to

Label for the wallet

Transaction request ID

Version of the pending approval

ID for the policy evaluation

Flag to use legacy policy engine

ID for the video call

The last date the approval was processing