Help Center · Integrations · Setup guide: outbound webhooks

Setup guide: outbound webhooks

Point Boxli at your endpoint and receive signed delivery and engagement events as they happen.

Webhooks are the build-anything integration: Boxli POSTs delivery and engagement events to an endpoint you control, as they happen. Route them into your data warehouse, your own alerting, or any system Boxli does not integrate with natively.

1
Open Settings → Integrations → Webhook
Click Connect on the Webhook card.
2
Enter your endpoint URL
The HTTPS endpoint that should receive events. On save, Boxli generates a Signing Secret and shows it on the card — copy it into your receiving code.
3
Verify signatures on your end
Every request carries an X-Boxli-Signature header: an HMAC-SHA256 of the payload using your Signing Secret. Verify it before trusting a request — it proves the event came from Boxli and was not tampered with.
4
Send a test
Use the Test button on the card to fire a test event at your endpoint and confirm the round trip before real events depend on it.

What you receive: delivery events as boxes move through shipped, delivered, and failed, and engagement events as recipients scan, tap, and watch. Each payload identifies the send and contact, so events join cleanly against your own data.

Webhooks also exist in two other places worth knowing about. Alert rules can call a webhook as their action — so a specific moment, like a deep watch, can hit your endpoint instead of (or alongside) Slack. And campaign workflows have a webhook step, letting a workflow notify your systems at exactly the right point in a sequence.

If the secret is ever exposed, Regenerate Secret on the card issues a new one — update your endpoint to match, since old signatures stop validating immediately.

Related articles

In the app

Do it where the work happens

Every guide here lives in the in-app Help Center too — open Help in the sidebar.

Open Boxli