# 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.

<CodeGroup>
```bash blnk.env wrap
BLNK_SLACK_WEBHOOK_URL=
BLNK_WEBHOOK_URL=
BLNK_WEBHOOK_HEADERS={"Authorization":"Bearer <token>","Content-Type":"application/json"}
```

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

<ParamField name="BLNK_SLACK_WEBHOOK_URL">
Slack incoming webhook URL used for team alerts.
</ParamField>
<ParamField name="BLNK_WEBHOOK_URL">
HTTPS endpoint that receives Blnk event notifications.
</ParamField>
<ParamField name="BLNK_WEBHOOK_HEADERS" default="{}">
Extra HTTP headers sent with webhook requests (for example authentication).
</ParamField>

<Note>
If using `.env`, set `BLNK_WEBHOOK_HEADERS` to a JSON-encoded object. For `blnk.json`, set `notification.webhook.headers` to a JSON object.
</Note>

### `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](https://api.slack.com/messaging/webhooks).

<Warning>
Treat Slack webhook URLs like secrets. Anyone with the URL can post to your channel, so store them in a secret manager or environment variables, not in version control.
</Warning>

### `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](/webhooks/overview#webhook-security) for signature verification.

<RelatedTopics
  items={[
    { title: "Webhooks overview", href: "/webhooks/overview" },
    { title: "Global webhooks", href: "/webhooks/global-webhooks" },
    { title: "Data stores", href: "/operating/configuration/data-stores" },
  ]}
/>