Overview
What is the Glacier Webhooks?
With Glacier Webhooks, you can monitor real-time events on the Avalanche C-chain and L1s. For example, you can monitor smart contract events, track NFT transfers, and observe wallet-to-wallet transactions.
Key Features:
- Real-time notifications: Receive immediate updates on specified on-chain activities without polling.
- Customizable: Specify the desired event type to listen for, customizing notifications according to individual requirements.
- Secure: Employ shared secrets and signature-based verification to guarantee that notifications originate from a trusted source.
- Broad Coverage: Support for C-chain mainnet, testnet, and L1s within the Avalanche ecosystem, ensuring wide-ranging monitoring capabilities.
Use cases
- NFT Marketplace Transactions: Get alerts for NFT minting, transfers, auctions, bids, sales, and other interactions within NFT marketplaces.
- Wallet Notifications: Receive alerts when an address performs actions such as sending, receiving, swapping, or burning assets.
- DeFi Activities: Receive notifications for various DeFi activities such as liquidity provisioning, yield farming, borrowing, lending, and liquidations.
Supported L1s
Webhooks are currently enabled for the following L1s. Additional L1s will be added in the future:
Mainnet
| L1 | Chain ID |
|---|---|
| Beam | 4337 |
| DFK | 53935 |
| Dexalot | 432204 |
| Shrapnel | 2044 |
| Testnet | Fuji |
Testnet
| L1 | Chain ID |
|---|---|
| Pulsar | 431234 |
| Beam | 13337 |
| Dexalot | 432201 |
| DFK | 335 |
| WAGMI | 11111 |
| Shrapnel | 2038 |
What are Webhooks?
A webhook is a communication mechanism to provide applications with real-time information. It delivers data to other applications as it happens, meaning you get data immediately, unlike typical APIs where you would need to poll for data to get it in “real-time”. This makes webhooks much more efficient for both providers and consumers. Webhooks work by registering a URL to send notifications once certain events occur. You can create receiver endpoints in your server in any programming language and those will have an associated URL (e.g. https://myserver.com/callback). This object contains all the relevant information about what just happened, including the type of event and the data associated with that event.
Webhooks vs. WebSockets:
The difference between webhooks and WebSockets is that webhooks can only facilitate one-way communication between two services. In contrast, WebSockets can facilitate two-way communication between a user and a service, recognizing events and displaying them to the user as they occur.
Event structure
The Event structure always begins with the following parameters:
Parameters:
webhookId: Unique identifier for the webhook in your account.eventType: The event that caused the webhook to be triggered. In the future, there will be multiple types of events, for the time being only the address_activity event is supported. The address_activity event gets triggered whenever the specified addresses participate in a token or AVAX transaction.messageId: Unique identifier per event sent.event: Event payload. It contains details about the transaction, logs, and traces. By default logs and internal transactions are not included, if you want to include them use"includeLogs": true, and"includeInternalTxs": true.
Address Activity webhook
The address activity webhook allows you to track any interaction with an address (any address). Here is an example of this type of event:
Overview
What is the Glacier Webhooks?
With Glacier Webhooks, you can monitor real-time events on the Avalanche C-chain and L1s. For example, you can monitor smart contract events, track NFT transfers, and observe wallet-to-wallet transactions.
Key Features:
- Real-time notifications: Receive immediate updates on specified on-chain activities without polling.
- Customizable: Specify the desired event type to listen for, customizing notifications according to individual requirements.
- Secure: Employ shared secrets and signature-based verification to guarantee that notifications originate from a trusted source.
- Broad Coverage: Support for C-chain mainnet, testnet, and L1s within the Avalanche ecosystem, ensuring wide-ranging monitoring capabilities.
Use cases
- NFT Marketplace Transactions: Get alerts for NFT minting, transfers, auctions, bids, sales, and other interactions within NFT marketplaces.
- Wallet Notifications: Receive alerts when an address performs actions such as sending, receiving, swapping, or burning assets.
- DeFi Activities: Receive notifications for various DeFi activities such as liquidity provisioning, yield farming, borrowing, lending, and liquidations.
Supported L1s
Webhooks are currently enabled for the following L1s. Additional L1s will be added in the future:
Mainnet
| L1 | Chain ID |
|---|---|
| Beam | 4337 |
| DFK | 53935 |
| Dexalot | 432204 |
| Shrapnel | 2044 |
| Testnet | Fuji |
Testnet
| L1 | Chain ID |
|---|---|
| Pulsar | 431234 |
| Beam | 13337 |
| Dexalot | 432201 |
| DFK | 335 |
| WAGMI | 11111 |
| Shrapnel | 2038 |
What are Webhooks?
A webhook is a communication mechanism to provide applications with real-time information. It delivers data to other applications as it happens, meaning you get data immediately, unlike typical APIs where you would need to poll for data to get it in “real-time”. This makes webhooks much more efficient for both providers and consumers. Webhooks work by registering a URL to send notifications once certain events occur. You can create receiver endpoints in your server in any programming language and those will have an associated URL (e.g. https://myserver.com/callback). This object contains all the relevant information about what just happened, including the type of event and the data associated with that event.
Webhooks vs. WebSockets:
The difference between webhooks and WebSockets is that webhooks can only facilitate one-way communication between two services. In contrast, WebSockets can facilitate two-way communication between a user and a service, recognizing events and displaying them to the user as they occur.
Event structure
The Event structure always begins with the following parameters:
Parameters:
webhookId: Unique identifier for the webhook in your account.eventType: The event that caused the webhook to be triggered. In the future, there will be multiple types of events, for the time being only the address_activity event is supported. The address_activity event gets triggered whenever the specified addresses participate in a token or AVAX transaction.messageId: Unique identifier per event sent.event: Event payload. It contains details about the transaction, logs, and traces. By default logs and internal transactions are not included, if you want to include them use"includeLogs": true, and"includeInternalTxs": true.
Address Activity webhook
The address activity webhook allows you to track any interaction with an address (any address). Here is an example of this type of event: