Transaction Objects

InputsSelection

Parameter	Type	Description
inputsToSpend	Array of Inputs	Inputs that should be used in the transaction
inputsToExclude	Array of Inputs	Inputs that shouldn’t be used in the transaction

Input

Parameter	Type	Description
txHash	string	txHash
index	string	vOut of the txHash

DestinationTransferPeerPath

Parameter	Type	Description
type	string	[ VAULT_ACCOUNT, EXCHANGE_ACCOUNT, INTERNAL_WALLET, EXTERNAL_WALLET, UNMANAGED_WALLET, ONE_TIME_ADDRESS, NETWORK_CONNECTION, FIAT_ACCOUNT ]
id	string	The peer ID (not needed for ONE_TIME_ADDRESS)
oneTimeAddress	OneTimeAddress	Destination address

OneTimeAddress

Parameter	Type	Description
address	string	Transfer destination address
tag	string	Used as destination tag for XRP;`memo for ATOM, EOS, HBAR, LUNA, LUNC, XDB, XEM;`memo_text`for XLM;`notes` for ALGO; Bank Transfer Description for fiat providers.

BlockInfo

Parameter	Type	Description
blockHeight	string	The height (number) of the block the transaction was mined in
blockHash	string	The hash of the block the transaction was mined in

RewardsInfo

Parameter	Type	Description
srcRewards	string	The ALGO rewards acknowledged by the source account of the transaction
destRewards	string	The ALGO rewards acknowledged by the destination account of the transaction

BlockchainInfo

Blockchain	Parameter	Type	Description
HBAR
	hbarTxHash	string	HBAR transaction hash
EVM
	evmTransferType	enum	Type of transfer: NATIVE for native transfer. TOKEN for token transfers that are reflected via the transaction’s logs. INTERNAL for internal transfers that are reflected via the transaction’s traces.
TON
	messageContent	string	Contains the payload of the internal message (see TON internal message docs). This field represents the smart contract input or data sent to the wallet. Unlike structured blockchains (e.g. EVM, Solana, Stellar), TON allows arbitrary message bodies. Fireblocks exposes this raw data so you can apply custom parsing logic for non-standard formats if needed.
	tonTransferType	enum	Type of transfer: NATIVE for native transfer. JETTON for Jetton transfer.
	hashes	TonHashes	Additional hashes of ton transfers
	isFeeExcess	boolean	Early Access. `true` only on the transaction that records the excess TON a Jetton transfer returned to one of your wallets other than the sender. That transaction is a plain native transfer to the wallet, and its top-level `feeInfo` has `recipient` only, like any other incoming transfer. Omitted otherwise.
	feeBreakdowns	array of TonFeeBreakdown	Early Access. The fees of each wallet of your workspace in the transfer, one entry per wallet. Available when the feature is enabled for your workspace.
CANTON
	transactionType	enum	Types of transactions: - OFFER - Transfer initiated. Sender has created a transfer offer awaiting the recipient’s action. This is the first step in a 2-step transfer flow. - ACCEPT - Transfer completed. The recipient has accepted the pending transfer offer. Funds have been transferred successfully. - REJECT - Transfer failed. Recipient has rejected the pending transfer offer. No funds were transferred. - WITHDRAW - Transfer cancelled. Sender has withdrawn/cancelled their pending transfer offer before recipient took action. No funds were transferred. - PRE_APPROVAL - Transfer completed instantly. Recipient had pre-approved incoming transfers, enabling a 1-step transfer flow (e.g., transfers from external sources like Kraken).
	traceableId	string	`UpdateId` of the original transfer offer or auto-approved transaction. The hash that could be used to locate the transaction in Canton explorers.
	hashes	CantonHashes	Additional hashes of Canton transfers.
DOT
	substrateExtrinsicId	string	The extrinsic ID of the transaction.
SUI
	gasUsed	GasUsed	Detailed breakdown of the costs incurred. The total gas cost and gas rebate can be calculated from these values.
TRON
	energyUsed	integer	The amount of energy consumed by the transaction. Energy pays for the processing cost of executing smart contracts, such as TRC-20 token transfers. Native TRX transfers don’t consume energy.
	bandwidthUsed	integer	The amount of bandwidth points consumed by the transaction. One bandwidth point equals one byte of transaction data, and every transaction type on the TRON network consumes bandwidth.

For ACCEPT, REJECT, and WITHDRAW transaction types, the offerUpdateId links back to the original OFFER transaction, enabling full transaction lifecycle tracking.

TonHashes

Parameter	Type	Description
externalIncoming	string	Hash of the external incoming message
tonTransfer	string	Hash of the ton transfer
jettonTransfer	string	Hash of the jetton transfer

TonFeeBreakdown

Early Access. One entry per wallet of your workspace in a TON transfer. Each entry describes one wallet and its own on-chain transaction. The summary of what the transfer cost each wallet (feeInfo.sender and feeInfo.recipient) is in the transaction’s top-level feeInfo; feeBreakdowns carries the detail behind it. For how fees work on TON, with worked examples, see TON Transfer Fees.

Parameter	Type	Description
role	string	`SENDER` or `RECIPIENT`: the role of the wallet in the transfer.
address	object	The wallet, as `raw` and `userFriendly` addresses.
txHash	string	The hash of the wallet’s own transaction. Omitted for a Jetton recipient that has no transaction of its own (see below).
feeBreakdown.totalOutMsgsForwardFees	string	The sum of the forwarding fees of the messages the wallet’s transaction sent.
feeBreakdown.chainReported	object	The fee components the blockchain reports for that transaction: `totalFees`, `storageFees`, `gasFees`, `actionFees`, `forwardFees` and, when applicable, `importFee`, `bounceFees`, `actionFine`. `totalFees` is the sum of `storageFees`, `importFee`, `gasFees`, `actionFees` and `bounceFees`.
feeBreakdown.fundingSpent	string	Jetton sender only: the TON the wallet attached to fund the token wallets and did not get back. When the excess comes back to the sender, this also includes the fee of receiving it.

Units. Everything inside feeBreakdowns is an integer string in nanoTON (1 TON = 1,000,000,000 nanoTON). The top-level feeInfo is in TON. How it ties to feeInfo. For each entry, totalFees + totalOutMsgsForwardFees + fundingSpent (fundingSpent is 0 when absent), converted from nanoTON to TON, equals the feesDeducted of the matching role in feeInfo: feeInfo.sender for the SENDER entry, feeInfo.recipient for the RECIPIENT entry. Which entries you get

Case	Entries
Your wallet sends to an external wallet	One: your wallet, `role: "SENDER"`.
An external wallet sends to your wallet	One: your wallet, `role: "RECIPIENT"`.
Between two wallets of your own workspace, or a transfer to the same wallet	One transaction with two entries, `SENDER` and `RECIPIENT`. Tell them apart by `role`. The top-level `feeInfo` has both `sender` and `recipient`.
Jetton transfer without a forward amount, and the recipient is your wallet	The recipient entry has no `txHash` and every figure is `"0"`: the recipient wallet has no transaction of its own and paid nothing.
Excess TON returned to one of your other wallets	When enabled for your workspace, that wallet gets its own transaction with one `RECIPIENT` entry and `isFeeExcess: true`.

Only wallets of the notified workspace appear. A counterparty outside your workspace is never listed. Example: Jetton transfer sent from your wallet. The wallet attached 0.1 TON and the excess came back to it (addresses and hashes shortened):

"blockchainInfo": {
  "tonTransferType": "JETTON",
  "hashes": {
    "externalIncoming": "68a3…433e",
    "jettonTransfer": "3fc0…1d33"
  },
  "messageContent": "te6cckEBAgEATwABZHNi0JwAAAAA…",
  "feeBreakdowns": [
    {
      "role": "SENDER",
      "address": {
        "raw": "0:8837…7d5a",
        "userFriendly": "0QCIN4Fp…WpAq"
      },
      "txHash": "b464…009a",
      "feeBreakdown": {
        "totalOutMsgsForwardFees": "92091",
        "chainReported": {
          "totalFees": "487381",
          "storageFees": "3",
          "gasFees": "220534",
          "actionFees": "46043",
          "forwardFees": "138134",
          "importFee": "220801"
        },
        "fundingSpent": "17143212"
      }
    }
  ]
}

The matching top-level feeInfo.sender is {"feesDeducted": "0.017722684"}: 487381 + 92091 + 17143212 = 17,722,684 nanoTON. Example: transfer between two of your vault accounts. One transaction. The top-level feeInfo is the sender’s, and both wallets are in the breakdown:

"blockchainInfo": {
  "tonTransferType": "NATIVE",
  "hashes": {
    "externalIncoming": "446f…d6fc",
    "tonTransfer": "587f…26a1"
  },
  "feeBreakdowns": [
    {
      "role": "SENDER",
      "address": { "raw": "0:8837…7d5a", "userFriendly": "0QCIN4Fp…WpAq" },
      "txHash": "16f1…cb50",
      "feeBreakdown": {
        "totalOutMsgsForwardFees": "57424",
        "chainReported": {
          "totalFees": "425437", "storageFees": "7925", "gasFees": "220534",
          "actionFees": "28710", "forwardFees": "86134", "importFee": "168268"
        }
      }
    },
    {
      "role": "RECIPIENT",
      "address": { "raw": "0:b45d…6be0", "userFriendly": "0QC0XWFD…MEN" },
      "txHash": "587f…26a1",
      "feeBreakdown": {
        "totalOutMsgsForwardFees": "0",
        "chainReported": {
          "totalFees": "45682", "storageFees": "7214", "gasFees": "38468",
          "actionFees": "0", "forwardFees": "0"
        }
      }
    }
  ]
}

Top-level feeInfo: "sender": {"feesDeducted": "0.000482861"} (425437 + 57424 nanoTON) and "recipient": {"feesDeducted": "0.000045682"} (45682 nanoTON).

When a transfer carries a very long message, feeBreakdowns, messageContent or both may be left out. tonTransferType, the hashes, isFeeExcess and the top-level feeInfo are always included.

CantonHashes

Parameter	Type	Description
offerUpdateId	string	`UpdateId` of the original transfer offer transaction. Present in transaction types such as OFFER, ACCEPT, REJECT, and WITHDRAW.
acceptUpdateId	string	`UpdateId` of the accept action transaction. Present in transaction types like ACCEPT.
rejectUpdateId	string	`UpdateId` of the reject action transaction. Present in transaction types like REJECT.
withdrawUpdateId	string	`UpdateId` of the withdraw action transaction. Present in transaction types like WITHDRAW.
preApprovalUpdateId	string	`UpdateId` of the pre-approval transfer transaction. Present in transaction types like PRE_APPROVAL.

GasUsed

Parameter	Type	Description
storageCost	string	Gas units consumed for data storage.
storageRebate	string	Gas units refunded due to storage cleanup.
computationCost	string	Gas units consumed for computation.
nonRefundableStorageFee	string	A portion of the storage fee that is non-refundable.

feeInfo

The paidByRelay, relayType, relayId, and relayName fields apply to gasless transactions. See EVM Gasless (Universal Gasless).

Parameter	Type	Description
networkFee	string	The fee paid to the network
serviceFee	string	The total fee deducted by the exchange from the actual requested amount (serviceFee = amount - netAmount)
gasPrice	string	The amount of gas required by/paid to the network to process the transaction
paidByRelay	boolean	`true` or `false`; indicates whether the relay paid the fee
relayType	string	Indicates whether the relay is the same tenant (`LOCAL`) or another tenant (`THIRD_PARTY`)
relayId	string	The Vault account ID of the relay
relayName	string	The name of the tenant hosting the third-party relay
sender	object	TON (Early Access). What the transfer cost the sending wallet, when it belongs to your workspace: `feesDeducted` and, for a Jetton recipient only, `valueCredited`, in TON with nine decimals. See RoleFeeInfo.
recipient	object	TON (Early Access). What the transfer cost the receiving wallet, when it belongs to your workspace. Same fields as `sender`.

NetworkRecord

Parameter	Type	Description
source	SourceTransferPeerPathResponse	Source of the transaction
destination	DestinationTransferPeerPathResponse	Destination of the transaction
txHash	string	Blockchain hash of the transaction
networkFee	number	The fee paid to the network
assetId	string	Transaction asset
netAmount	number	The net amount of the transaction, after fee deduction
status	NetworkStatus object	Status of the blockchain transaction
type	string	Type of the operation
destinationAddress	string	Destination address
sourceAddress	string	For account-based assets only, the source address of the transaction

NetworkStatus

Parameter	Type	Description
networkStatus	enum	`DROPPED` - The transaction was dropped by the network (Typically due to a low fee, or if the mempool is full). \n`BROADCASTING` - Broadcasting to the blockchain. \n`CONFIRMING` - Pending confirmations. \n`FAILED` - The transaction has failed to complete on the blockchain. \n`CONFIRMED` - Confirmed on the blockchain.

TransactionRequestDestination

Parameter	Type	Description
amount	string	The amount to be sent to this destination
destination	DestinationTransferPeerPath	The specific destination

DropTransactionRequest

Parameter	Type	Description
txId	string	The ID of the transaction being dropped.
feeLevel	string	The fee level for the replacement of non-ETH transactions.
gasPrice	string	The network fee level for the replacement of ETH transactions.

DropTransactionResponse

Parameter	Type	Description
success	boolean	True if the transaction dropped or the replacement succeeded.
transactions	array	Dropped Transaction replacement Transaction ID(s).

SetConfirmationsThresholdResponse

Parameter	Type	Description
success	boolean
transactions	array of strings	txIds of the transactions

NodeControls

Parameter	Type	Description
type	string (enum)	Transaction routing type. \nEnum Values: \n \n- NODE_ROUTER\n- MEVFor routing transactions to a custom node set - NODE_ROUTER \n For MEV protection routing set - MEV
tag	string	Used for NODE_ROUTER type only. The pre-configured tag of the node to route the transaction to

Index

Parameter	Type	Description
Index	integer	(Optional) Fireblocks’ internal identifier for a specific transfer within a transaction. - For UTXO-based assets, this field corresponds to the UTOX’s vOut index. - For other blockchains, like EVM, Tron, Solana, etc., this field is derived from the sequential position of the event within the transaction’s transfer list. The field is not returned when the transaction includes multiple destinations.

logIndex

Parameter	Type	Description
logIndex	integer	Applicable to EVM blockchains only. Represents the EVM log index that indicates the order of the log within the block. This information can be verified directly on the blockchain.

blockchainIndex

Parameter	Type	Description
blockchainIndex	string	Blockchain-native transfer identifier showing the transfer’s exact position within the block data (e.g. log entry, trace path, or nested array index). - EVM token transfers: Uses logIndex. - EVM internal transfers: Uses traceAddress (e.g., [0,1,2] → “0_1_2”). - Solana: Refers to the nested instruction position in the instruction array.

nonce

Parameter	Type	Description
nonce	string	Blockchain nonce for the transaction (EVM only)

Introduction

Errors & Statuses

API Endpoints

Data Objects

InputsSelection

Input

DestinationTransferPeerPath

OneTimeAddress

BlockInfo

RewardsInfo

BlockchainInfo

TonHashes

TonFeeBreakdown

CantonHashes

GasUsed

feeInfo

NetworkRecord

NetworkStatus

TransactionRequestDestination

DropTransactionRequest

DropTransactionResponse

SetConfirmationsThresholdResponse

NodeControls

Index

logIndex

blockchainIndex

nonce

​InputsSelection

​Input

​DestinationTransferPeerPath

​OneTimeAddress

​BlockInfo

​RewardsInfo

​BlockchainInfo

​TonHashes

​TonFeeBreakdown

​CantonHashes

​GasUsed

​feeInfo

​NetworkRecord

​NetworkStatus

​TransactionRequestDestination

​DropTransactionRequest

​DropTransactionResponse

​SetConfirmationsThresholdResponse

​NodeControls

​Index

​logIndex

​blockchainIndex

​nonce

InputsSelection

Input

DestinationTransferPeerPath

OneTimeAddress

BlockInfo

RewardsInfo

BlockchainInfo

TonHashes

TonFeeBreakdown

CantonHashes

GasUsed

feeInfo

NetworkRecord

NetworkStatus

TransactionRequestDestination

DropTransactionRequest

DropTransactionResponse

SetConfirmationsThresholdResponse

NodeControls

Index

logIndex

blockchainIndex

nonce