webhook-overview
Supported Event
EventType is the value that specifies the event to track when configuring a Webhook. The data you receive varies depending on the EventType. The supported EventTypes are as follows.
Event Type | Description |
|---|---|
Monitors the activity of accounts included in a user-specified address array. This event sends a notification whenever those accounts appear as the sender (from) or receiver (to) of a transaction — that is, when a transaction, token transfer (ERC20), or NFT transfer (ERC721, ERC1155) occurs. This service allows users to track the activity of multiple addresses in real time, enabling effective monitoring of asset movements and transactions. | |
Delivers the transaction receipt as a notification when a transaction sent from a specific address has been successfully mined and finalized by the blockchain network. Notifications are sent both when the transaction succeeds and when it fails. Users can track the final status of their sent transactions in real time and confirm whether they succeeded or failed. | |
Sends a notification when a transaction from a specific address is processed successfully. This event fires when the transaction is fully confirmed by the blockchain network and deemed valid. Users can confirm that their transaction executed as expected and that the desired operation completed successfully. | |
Sends a notification when a transaction from a specific address fails. This event fires when the transaction is rejected by the blockchain network or fails to complete due to an error during execution. Users can quickly identify the cause of the transaction failure and take the necessary action. Failures can result from various technical issues such as insufficient gas or unmet contract conditions, and this event helps with more effective transaction management and error tracking on the blockchain. | |
Sends a notification when a token (ERC20) transfer or NFT (ERC721, ERC1155) transfer occurs. Users can specify a contract address to monitor token movements occurring within that contract. Additionally, for NFTs following the ERC721 and ERC1155 standards, it is possible to set a specific token ID as a condition and track only transfers for that token ID. | |
Sends a notification when the balance of a specified account falls below a threshold set by the user. This event plays an important role in financial management and asset protection. Users can use this feature to take preventive action before their account balance drops below the minimum threshold, and to transfer additional funds or take other financial measures in a timely manner when needed. | |
Sends a notification based on the interval of blocks generated on the network. Users can set a desired block interval (e.g., every block, every N blocks) to receive block data at that frequency. This event provides data after a specified number of blocks have been confirmed, delivering more stable and finalized data. | |
Sends a notification when addresses on a predefined block list transfer tokens to a target address. This event type is primarily used to monitor the activity of addresses on a pre-defined block list. For example, you can receive an immediate alert when a blacklisted address attempts to transfer funds to a specific account. This makes it a useful tool for detecting illegal or suspicious fund movements in advance. | |
Sends a notification when addresses on an allow list transfer tokens to a target address. The allow list contains trusted addresses, and fund movements from those addresses are considered safe or expected activity. This event type is used to track the activity of allowed addresses and to confirm fund transfers from addresses included in the allow list. | |
Sends a notification when a transaction containing a specified smart contract event log is created. Users can specify one or more event signatures as filter conditions. For example, configuring the system to monitor the ERC20 standard token transfer event | |
This feature sends a notification each time an event matching the specified conditions occurs, when the user pre-configures the API with a specific event type (eventType) and the account that triggered the event (eventAccountAddress). When a user wants to track a specific event, they can include the relevant event type and associated account in the API configuration. The configured API detects events in real time and sends notifications, enabling quick awareness of important activity occurring on the network. | |
This feature returns all details of the transaction containing the specified event type when the user configures the API with a specific event type (eventType) and the account that triggered it (eventAccountAddress). When an event occurs, all details of the corresponding transaction — including the full transaction history, sender, receiver, amount, called function, and related data — are available, making it useful for system monitoring. |