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 70 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:

	Free	Starter	Growth	Business
Notification Limit	1	2	10	20

Enterprise Access

Need a higher limit? We also offer an Enterprise plan. Contact us to learn more.

Supported Networks

The QuickAlerts and QuickAlerts API are available on these chains and networks:

Chain	Mainnet	Testnets	Note
Ethereum	✅	Holesky, Sepolia
Polygon	✅	Amoy
Polygon zkEVM	✅	Cardona
Arbitrum	✅	Sepolia
Arbitrum Nova	✅
Avalanche C-Chain	✅	Fuji
B3	✅	Sepolia
Base	✅	Sepolia
Bera	Coming soon	bArtio
Bitcoin	✅		REST API Only
Blast	✅	Sepolia
BNB Smart Chain	✅	Testnet
Camp	Coming soon	Sepolia
Celo	✅
Cyber	✅	Sepolia
Doge	✅		REST API Only
Fantom	✅
Fraxtal	✅
Gnosis	✅
Hedera	✅	Testnet
Immutable	✅	Testnet
Kaia	✅	Kairos
Linea	✅
Mantle	✅	Sepolia
Morph	Coming Soon	Holesky
Optimism	✅	Sepolia
Race	✅	Sepolia
Redstone	✅
Scroll	✅	Testnet
Sei	✅	Atlantic
Story	Coming soon	Testnet
TRON	✅
Xai	✅	Testnet
zkSync Era	✅	Sepolia
Zora	✅

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:

Expression

Deploy

1
tx_from == '0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B'
2
||
3
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:

Expression

Deploy

1
tx_logs_address == '0x2106c00ac7da0a3430ae667879139e832307aeaa'
2
&&
3
tx_logs_topic0 == '0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef'
4
&&
5
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.

Looking for more QuickAlerts examples?

Check out our Expression Library for pre-written expressions that you can use to power your apps and workflows.

QuickAlerts Destinations

We currently support webhook URL destinations for QuickAlerts notifications, with additional destinations up for consideration based upon customer demand.

In the meantime, we have guides available demonstrating how to send QuickAlerts notifications to Discord, Telegram, SMS, Email, and Twitter.

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.

We ❤️ Feedback!

If you have any feedback or questions about this documentation, let us know. We'd love to hear from you!