Configure real-time alerts for transaction events and handle error notifications through Slack. Stay updated with critical information.
Field | Description | Type |
---|---|---|
event | Indicates the type of event, e.g., transaction.applied . | String |
data | Contains the request payload, detailing the relevant information. | Object |
Event name | Description |
---|---|
ledger.created | When a ledger is created. |
Event name | Description |
---|---|
balance.created | When a balance is created. |
Event name | Description |
---|---|
balance.monitor | When a balance monitor is triggered due its conditions being met. |
Event name | Description |
---|---|
transaction.applied | When a transaction is applied or committed. |
transaction.inflight | When a transaction is inflight |
transaction.void | When an inflight transaction is voided. |
transaction.scheduled | When a transaction is successfully scheduled. |
transaction.rejected | When a transaction is rejected |
Event name | Description |
---|---|
bulk_transaction.applied | When all items in a bulk transactions have been applied. |
bulk_transaction.inflight | When all items in a bulk transactions are successfully inflight. |
bulk_transaction.failed | When a bulk transaction fails. |
Event name | Description |
---|---|
identity.created | When an identity is created. |
blnk.json
configuration file. This file allows you to specify the webhook URLs that Blnk sends notifications to — both for your application and Slack.
blnk.json
file, please create a new json
file — it contains essential settings for running your Blnk server.Next, copy & paste the configuration JSON into it.notification
object as follows:
slack
:
webhook_url
: The webhook URL provided by your Slack workspace.webhook
:
url
: Your application’s webhook URL where Blnk sends transaction event notifications to.headers
: Optional headers that you may need to include in the notification request to authenticate the message. This can include authentication tokens or content type specifications.