Signed payloads
HMAC signatures let your app reject forged or modified event requests.
Subscribe to delivery events with HMAC signatures, delivery attempts, retry visibility, secret rotation, and replay controls that connect each event back to the original message.
Webhooks close the loop between Sendix delivery and your product database — signed, inspectable, and recoverable.
Choose the delivery, engagement, and inbound events your app needs.
Every payload carries an HMAC signature tied back to the original message id.
Reject forged or modified requests before trusting the payload.
Inspect attempts and replay events as a deliberate operator action.
Each block keeps your application state and Sendix delivery state provably in sync.
HMAC signatures let your app reject forged or modified event requests.
Attempts, response codes, and timing stay visible for each endpoint.
Delivery, bounce, complaint, open, click, and inbound events share one envelope.
Replay controls are designed as operator actions, not hidden background magic.
Use HMAC signatures and rotating secrets to reject forged requests, then update product state with confidence.
Read the guideconst valid = sendix.webhooks.verify({
payload,
signature: req.headers['x-sendix-signature'],
secret: SENDIX_WEBHOOK_SECRET,
});Signed events, retry visibility, and replay controls come with the same account you already send from.
Short notes for developers connecting Sendix events into product state.
Yes. Sendix webhook payloads are designed around HMAC signature verification.
Yes. Replay controls are part of the webhook operations surface.
Yes. Events are tied to message lifecycle, not only to one sending method.
25,000 emails free every month. No credit card required. Upgrade only when you outgrow the free tier — and we will let you know when that time comes.
Managed SaaS platform · Native SMTP engine · SOC 2 in progress