Tokenization webhook notifications send an onchain_data.updated event to your Webhooks v2 endpoint whenever a transaction emits an event on a token contract that you deployed or linked in Fireblocks, including transactions that do not start from your workspace.

Why use tokenization webhooks

Standard Fireblocks webhooks notify you about transactions that start from your vault accounts. Token issuers also need to know what happens to their token across all of its holders, such as transfers between wallets outside Fireblocks. Tokenization webhook notifications cover those events, so you can reconcile your records with the blockchain without polling.

Which contracts send events

Token contracts and Access Registries (AllowList and DenyList) that you issued with Fireblocks, such as ERC20F tokens.
Other EVM smart contracts that you deployed or linked in Fireblocks, including bring-your-own tokens, on supported blockchains.

Fireblocks decodes each event with the contract's ABI, so the notification includes readable event parameters.

Set up tokenization webhook notifications

Create a Webhooks v2 webhook, or edit an existing one, that listens for the onchain_data.updated event. In the Console, go to Developer center > Webhooks. Only Owners, Admins, and Non-Signing Admins can configure webhooks.
In the Console, open the token or contract in Tokenization.
Select Manage on-chain data.
Turn on Webhook notifications to include this contract in the tokenization webhook notifications configured for your workspace.

Each contract has its own setting, so you choose which contracts send notifications.

What the event contains

The data object of an onchain_data.updated event describes the transaction and the events it emitted. Key fields include:

contractAddress: The contract that emitted the event.
transactionHash, blockNumber, blockTimestamp, and chainId: Where the transaction is on the blockchain.
from and to: The sender and recipient of the transaction.
status: Whether the transaction succeeded.
decodedLogs: The decoded event parameters, as key and value pairs.

For every field, see the Tokenization events reference in the Developer Portal.

High-volume contracts

A contract that emits a very high volume of events can slow down delivery for everyone. When that happens, Fireblocks pauses indexing and webhook delivery for that contract until the volume drops. The On-chain data dialog shows a warning, and the contract appears as rate limited. Your settings are kept and apply again when delivery resumes.

Supported blockchains

On-chain data tracking is not available on every blockchain. If a contract is on an unsupported blockchain, the On-chain data dialog tells you. For the current list, see the Tokenization events reference.

Past events

Webhook notifications tell you about new events. To retrieve earlier events for a contract, scan its history and query the on-chain data endpoints, as described in the Index any contract guide.