Alerts
Alerts detects deposits, withdrawals, token transfers, and logs on addresses. It offers three methods: Webhook (push), where Nodit sends events to a registered URL; WebSocket subscription (push), where your system keeps a connection open and receives events sent by the server; and filter polling (pull), where your system queries for changes directly. By default, Webhook sends a message after the block containing the transaction is finalized. If you set isInstant to true, it sends the event as soon as it is detected, regardless of block finality.
Polling each customer address periodically increases call volume in proportion to the number of addresses and delays updates by the polling interval. With Alerts, you receive events without polling, and Address Set lets you manage a large number of addresses with a single Webhook.
Use Cases
- Service OpsDetect customer deposits
Register customer deposit addresses in an Address Set and receive deposit events through Webhook for processing. Updates arrive with less delay and fewer calls than periodic polling.
- Service OpsManage deposit addresses in bulk
Add newly created deposit addresses to an Address Set and monitor them with a single Webhook. You do not need to create additional Webhooks as addresses grow, which reduces operational effort.
- InfrastructureDetect events in network-segregated environments
In environments that cannot accept inbound connections, use filter polling to fetch changes since the last query. You can detect logs and new blocks without opening inbound connections.
Available APIs
Webhook — Receive Events (push)
WebSocket Subscriptions (push)
Filter Polling (pull)
- RPC
eth_getLogsRetrieves logs that match conditions66 CU - RPC
eth_newFilter · eth_newBlockFilterRegisters a log filter and a new block filter18 CU - RPC
eth_getFilterChangesRetrieves changes since the last poll18 CU - RPC
eth_getFilterLogsRetrieves all logs matching the filter conditions69 CU - RPC
eth_uninstallFilterRemoves a registered filter10 CU