API and webhooks
Your systems should know when somebody leaves.
An unsubscribe changes who you are allowed to contact everywhere, not just here. That is the case webhooks exist for, and it is worth wiring up on day one.
Twelve events
Subscribed and unsubscribed. Delivered, bounced, marked as spam, failed. Opened and clicked. Campaign started, finished, paused, cancelled. Each one signed, retried, and logged with the request and the response.
- HMAC signature with a timestamp, so a captured request cannot be replayed
- Retries with backoff for about half an hour
- A delivery log you can read when something looks wrong
Keys that match what they are for
Publishable keys for the browser, limited to taking a signup. Secret keys for your server. Test keys that validate everything and send nothing. Each one can be scoped to a single brand.
If your endpoint stops answering, we tell you.
Repeated failures disable it and email whoever manages webhooks. Campaigns keep sending and every event is still recorded, so your reports stay complete while you fix it.
Try ZevCampaign for 14 days
No card to start. Pick a plan before the trial ends and nothing pauses; your contacts, campaigns and reports carry straight on.
[object Object]