Discover Events and find out how it enables real-time data processing.
In a traditional API, customers request data from the blockchain using the API. This process involves continuous polling where customers request new blocks, transactions, and related information. The system retrieves data on demand, creating a continuous query process cycle.
Event streaming flips the interaction model by delivering blockchain events directly to customers. Currently, the delivery is limited to webhooks. Customers will have to register a webhook in order to receive blockchain events.
Blockchain events are delivered in near real-time as they happen on the chain. This enables an event-driven architecture where customers receive only the data they're interested in and only when relevant. Customers can control which events will be sent by event streaming. It works on a conditional basis that is reflected in the form of rules and variables.
Supported Protocols
| Protocol | Network |
|---|---|
| BTC | Mainnet Testnet |
| BCH | Mainnet |
| DOGE | Mainnet |
| DOT | Mainnet Westend |
| ETH | Mainnet Holesky |
| LTC | Mainnet |
| POL (formerly known as MATIC) | Mainnet Amoy |
Event Types
Event Streaming has two conditions to receive events:
| Events | Conditions | Supported Event Types |
|---|---|---|
| Based on the Event Type | Receive events when a blockchain event of a specific type occurs. | unified_block unified_reorg |
| Based on Address | Receive events when a blockchain event is related to a specific address. | unified_confirmed_tx unified_confirmed_balance unified_confirmed_tx_trace unified_confirmed_tx_log |
Info:
Learn how to integrate with Events in the Integration guide.
👋 Need Help?
Contact us through email or our support page for any issues, bugs, or assistance you may need.