Integrations/Resend
b
Your sender reputation, your domain, your key
BroadcastMail uses your Resend API key to send. We never touch your deliverability, your domain, or your sender identity.
Overview
Most email tools send on shared infrastructure under their own domain. Your emails say "via" their domain in the header, and your deliverability depends on how other customers behave on the same IP pool.
BroadcastMail doesn't work that way. You bring your own Resend key. Emails go out from your domain, under your sender identity, through Resend's infrastructure. We're just the interface.
Message headerswhat recipients see
fromLaki <hello@yourdomain.com>signedyourdomain.comvianone
What BroadcastMail does with your key
01 Authenticates with Resend using your API key at send time
02 Sends each campaign email through your Resend account
03 Receives delivery webhooks (delivered, opened, bounced, complained) and shows them in your dashboard
04 Never stores email content after sending
What you need
A Resend account (free tier works for testing)
An API key from your Resend dashboard
A verified sending domain (your own, not resend.dev)
What it enables
Mail from your own domain, no "via" or "on behalf of"
Delivery tracking per campaign: received, opened, bounced
Hard bounces added to your suppression list automatically
One-click unsubscribe handled for you
Why bring your own key?
01
Reputation is an asset
It takes months to build and can be damaged by other senders on shared infrastructure. Owning your key means owning your reputation.
02
No lock-in
If you stop using BroadcastMail, your Resend account, domain reputation, and sending history go with you.
Webhooks received
deliveredopenedbouncedcomplained