Skip to main content
This page covers all transaction events that can trigger webhook notifications, and their associated data objects for the Webhooks v2 service.

Transaction event types

To receive a specific event, include its eventType in the webhook’s notification object.

Transaction alert events

Transaction alert events notify you when Fireblocks detects conditions that may require intervention, such as transactions that have stalled due to fee-related issues. Use these events to build automated monitoring and remediation workflows.

transaction.alert.stuck

Triggered when one or more transactions from a vault account and base asset are stuck in the CONFIRMING status on EVM blockchains, indicating potential fee-related issues that may block subsequent transactions.

Example payload

Data objects

TransactionDetails

TransactionOperation

AmountInfo

transaction_status_updated webhooks contain only up to 17 digits past the decimal place when reporting balances.

FeeInfo

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

RoleFeeInfo

TON. What a transfer cost one wallet of your workspace, in TON, as decimal strings with nine decimals (like networkFee).

TON fee fields

For TON transfers, feeInfo.sender and feeInfo.recipient tell you what the transfer cost each wallet of your workspace that took part in it. They are omitted for other blockchains. The per-wallet detail behind them is in blockchainInfo.feeBreakdowns. For how fees work on TON, with worked examples, see TON Transfer Fees. networkFee describes the transfer as a whole. feesDeducted is always the cost to one wallet, so the two can differ. For example, a recipient only pays the fees of its own incoming transaction. What feesDeducted contains What you receive in each case Examples Sender of a Jetton transfer to an external wallet. The wallet attached 0.1 TON, got 0.082922856 TON back as excess, and paid its own fees:
0.017722684 = own fees 0.000579472 (0.000487381 transaction fees plus 0.000092091 forwarding fees) + attached 0.1 − excess returned 0.082922856 + fee of receiving the excess 0.000066068. Native TON transfer between two of your vault accounts:
Recipient of a native TON transfer from an external wallet:
Recipient of a Jetton transfer with a forward amount of 0.000000001 TON:
Recipient of a Jetton transfer with no forward amount (the wallet paid nothing):
  • feeInfo.sender and feeInfo.recipient appear only in the top-level feeInfo. They are not repeated inside blockchainInfo.
  • A Jetton sender’s feesDeducted is calculated from its own two transactions (the transfer and the returned excess), so other activity on a busy wallet in between does not change it.
  • If a wallet’s figure cannot be established from on-chain data, its object is left out, and the other wallet’s is still reported. A wallet that paid nothing is reported as zero, never left out.

SourceTransferPeerPathResponse

For more details, see transaction sources and destinations.

DestinationTransferPeerPathResponse

DestinationsResponse

TransactionExtraParameters

SystemMessageInfo

TransactionAlertPayload

The data object returned with transaction.alert.stuck events.

RecommendedAction

StuckTransactionDetails

StuckAccountDetails