All updates
Changelog
Webhooks, send pacing, and the whole app on a phone
The API gained its other half. Your code could already call day3; webhooks let day3 call you when an address bounces or a message lands, so your own records stop drifting. Underneath, outbound mail is now paced to the provider's send rate instead of bursting into a throttle, pages load in one round trip instead of two, and the app works on a phone.
What shipped
- Outbound webhooks for six events: email.sent, email.delivered, email.bounced, email.complained, email.failed and suppression.created, covering campaign and transactional mail alike.
- Every webhook request is signed, retries run for around seven hours, and a failing endpoint is never silently disabled.
- Sending is paced to the provider's live send rate, so a large campaign no longer trips a throttle it caused itself and then waits ten minutes.
- Pages load their data on the server, so moving around the app costs one round trip instead of two.
- The whole app works on a phone: an off-canvas sidebar, stacked forms, tables that scroll in place, and real touch targets.
- Standing warnings above the campaign builder can be collapsed to one line, and a missing business address can be added right there.
- The MCP install snippet is one line and works in bash, zsh, CMD and PowerShell.