Operating

Webhook Configuration

Configure Slack webhooks and outgoing HTTP webhooks for Blnk alerts and events.

This page covers the settings that control how Blnk sends outbound notifications to Slack and to your own HTTP endpoints.

Webhook settings

Use the notification object to configure Slack incoming webhooks and a generic application webhook. You can set either integration alone, or both at the same time.

BLNK_SLACK_WEBHOOK_URL=
BLNK_WEBHOOK_URL=
BLNK_WEBHOOK_HEADERS={"Authorization":"Bearer <token>","Content-Type":"application/json"}

{
  "notification": {
    "slack": {
      "webhook_url": ""
    },
    "webhook": {
      "url": "",
      "headers": {
        "Authorization": "Bearer <token>",
        "Content-Type": "application/json"
      }
    }
  }
}

BLNK_SLACK_WEBHOOK_URL

When set, Blnk can post messages to the Slack channel associated with the incoming webhook.

To create a webhook URL, follow Slack’s guide: Sending messages using incoming webhooks.

BLNK_WEBHOOK_URL

When set, Blnk delivers notifications to your application at this URL. Use this when you want to trigger workflows, sync internal services, or custom alerting outside of your ledger.

BLNK_WEBHOOK_HEADERS

Optional extra HTTP headers Blnk sends with each global webhook request. Use this for authentication tokens, custom Content-Type values, or other gateway requirements.

These headers are separate from Blnk’s signing headers (X-Blnk-Signature and X-Blnk-Timestamp). See Webhook security for signature verification.