Use the mintBlue console's Event Listener feature to actively filter and monitor transactions on the network.
Event listeners allow you to listen for events matching a certain filter on the mintBlue console. These events can be internal events happening within mintBlue or transactions happening in real time on the Bitcoin network.
An event listener contains two main elements: triggers and actions.
- Triggers define the specific events that the listener should listen for
- Actions define what should happen when an event matching the trigger is detected.
Triggers can be of several different types, including:
- BITCOM: triggers when a BITCOM (Bitcoin Application Protocols) event occurs.
- PEPPOL: triggers when a PEPPOL (Pan-European Public Procurement Online) event occurs.
- PAYMENT_FROM: triggers when a payment is received from a specific address.
- PAYMENT_TO: triggers when a payment is sent to a specific address.
- BITQUERY: triggers when a transaction matches a specified Bitquery.
- mintblue.transaction.inserted: triggers when a transaction is inserted into a specified project on your account.
- mintblue.transaction.created: triggers when a transaction is created on your account.
Read technical details about Triggers
Actions define what should happen when an event matching the trigger is detected. Actions can be of several different types, including:
- insert_into_project: inserts the transaction into a specified project.
- webhook: sends a webhook call to a specified URL.
When a webhook is called, the body of the request will contain information about the subscription and event that triggered the call, as well as the full raw transaction (if specified in the URL query parameters)
Read technical details about Actions