Skip to main content
Blnk Watch is currently in beta. Send us a message
Alert webhooks let you send risk alerts to your own endpoints when one or more rules trigger for a transaction. You configure webhook URLs and options with environment variables; Watch sends a POST request with the consolidated verdict, score, and evaluation data whenever the alert criteria are met.

How alert webhooks work

Enable alert webhooks by setting the webhook URL and turning delivery on in your .env file:
.env
Watch sends an alert webhook only when all of these conditions are met:
  1. At least one rule triggered for the transaction during evaluation.
  2. Alert webhooks are enabled - ALERT_WEBHOOK_ENABLED is not set to false.
  3. Alert criteria are met - either:
    • The consolidated risk score is greater than or equal to ALERT_WEBHOOK_RISK_THRESHOLD (default is 0.5), or
    • The consolidated verdict is block or review.
If no webhook URLs are set, Watch skips delivery and does not retry.

Delivery behavior

Watch sends a POST request with Content-Type: application/json and the payload structure below. If you set ALERT_WEBHOOK_API_KEY, Watch includes Authorization: Bearer <value> on each request. Your endpoint should return a 2xx status code to indicate success.

Webhook payload structure

Here’s the alert payload sent when a transaction triggers one or more rules:
The evaluation_data object contains:

Security considerations

  • Use HTTPS for all webhook URLs in production.
  • Set ALERT_WEBHOOK_API_KEY and validate the Authorization: Bearer <token> header in your endpoint to ensure requests are from Watch.
  • Do not log or store the API key in plain text.

Need help?

We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool. To ask questions or discuss issues, please contact us or join our Discord community.