Available in version 0.8.4 and later.
Payload contract
Each delivery is an HTTPPOST with a JSON body in this shape:
transaction.applied
| Field | Description | Type |
|---|---|---|
event | Event name, for example transaction.applied. See Supported events. | String |
data | Payload for the event—resource fields, error details, or reconciliation results. | Object |
Delivery semantics
Blnk delivers webhooks at least once. Your endpoint may receive the same event more than once, often with an identical payload andX-Blnk-Signature.
Make handlers idempotent so a duplicate delivery does not trigger the same side effect twice, for example, sending two emails or crediting a balance twice. Dedupe on a stable key such as the event name plus the resource identifier in data, e.g. transaction_id.
If your global webhook endpoint returns a non-
2xx response, Blnk does not retry the delivery. For configurable retries, use transaction hooks instead.Configuration
Implement your endpoint
- Accept
POSTrequests with a JSON body matching the payload contract. - Optionally verify signatures per Webhook security.
- Return
2xxonly after you have safely recorded or processed the event.
Handle supported events
Use the
event field to identify what happened, then route the payload in data to the right handler.See Supported events for every event name and when it fires.Related docs
Supported events
Event names and descriptions.
Webhooks overview
Global vs transaction hooks and security.
Notification configuration
Set your global webhook URL