QuickAlerts enables you to leverage real-time blockchain data and advanced alerting to power your apps, make DeFi trading decisions based on the specific data that matters to you, add real-time blockchain event driven logic into your workflows, and more.
Cost
Each QuickAlerts notification sent to your webhook URL uses 4 API credits.
Access
There are two ways to access QuickAlerts - within the QuickNode Developer Portal, and through the QuickAlerts REST API.
Plan Limits
The number of QuickAlerts notifications that can be active at any given time is based on your QuickNode Plan:
| Discover | Build | Scale | |
|---|---|---|---|
| Limit | 1 notification | 10 notifications | 20 notifications |
Enterprise Access
Need a higher limit? We also offer an Enterprise plan. Contact us to learn more.
Supported Networks
The QuickAlerts and QuickAlerts API is available on these chains and networks:
| Chain | Mainnet | Testnets | Note |
|---|---|---|---|
| Ethereum | ✅ | Goerli, Sepolia | |
| Polygon | ✅ | Mumbai | |
| Polygon zkEVM | ✅ | Testnet | |
| Arbitrum | ✅ | Goerli | |
| Arbitrum Nova | ✅ | ||
| Avalanche C-Chain | ✅ | Fuji | |
| Base | ✅ | Goerli | |
| Bitcoin | ✅ | REST API only | |
| BNB Smart Chain | ✅ | Testnet | |
| Celo | ✅ | ||
| Doge | ✅ | REST API only | |
| Fantom | ✅ | ||
| Gnosis | ✅ | ||
| Optimism | ✅ | Goerli | |
| TRON (beta) | ✅ |
REST API
To access the QuickAlerts REST API, you will first need to create an API key. Learn More
QuickAlerts Expressions
QuickAlerts expressions can target any combination of data from a block, transaction, and/or log using comparators and operators. Learn more about data targeting and modifiers, operators, and comparators.
Example 1: Transaction Sent Notification
If you want to receive a notification whenever a transaction was sent to or from a specified wallet, you could use an expression like the one below:
(tx_from == '0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B') || (tx_to == '0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B')
tx_from represents the address the transaction originated, tx_to represents the destination of the transaction, and || is the operator meaning OR.
Example 2: NFT Transfer Notification
If you want to receive a notification whenever a Loopy Donuts NFT is transferred, you would use an expression like the following that targets the transaction logs:
(tx_logs_address == '0x2106c00ac7da0a3430ae667879139e832307aeaa') && (tx_logs_topic0 == '0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef') && (tx_logs_topic3_int > 0)
tx_logs_address represents the contract address for Loopy Donuts, tx_logs_topic0 is the topic hash that represents a Transfer() event on the contract, and tx_logs_topic3_int is an integer greater than 0, which represents the tokenID that is being transferred.
QuickAlerts Destinations
We currently support webhook URL destinations for QuickAlerts notifications, with additional destinations, like Slack, email, SMS, Discord, Pagerduty, and more, coming soon. You can let us know what kind of destination you are interested by sharing feedback.
Webhook Alert Payload
When your QuickAlerts expression finds a match against streaming blockchain data, we send a payload to your destination, instantly. Learn more about the available Payload Types.