Order email that reaches the inbox.
Confirmations, shipping notices, and delivery updates from a domain you verify yourself. Authentication and suppression handled so the email a shopper is waiting on lands in the inbox.
The order data flows in. The domain is yours.
A send call passes the order id and tracking link into a versioned template. It goes out from your own domain, signed with DKIM and backed by SPF. Keep your existing DMARC policy, or add one separately when you are ready.
POST https://api.samva.dev/v1/messages
{ to: [{ email: "ada@example.com" }],
channel: "email",
email: { templateSlug: "order-shipped",
templateData: {
orderId: "A-1042",
trackingUrl: "https://…"
} } }
← { id: "msg_7q2xk9mvt4znw8rh", status: "pending" }TYPE HOST PURPOSE STATUS
TXT _samva ownership verified
CNAME s1._domainkey DKIM verified
MX send MAIL FROM verified
TXT send SPF verifiedA shopper is waiting on an email that shows up.
Order updates land in spam.
A shopper waiting on a shipping notice checks their inbox and finds nothing, because the sending domain never built the authentication to earn a place there.
Notification templates drift.
A shipping-update email gets edited in one place and not another, and customers start seeing two different layouts for the same event.
A seasonal spike makes cost unpredictable.
Order volume triples for a week and you're left guessing what the bill looks like, or worse, hitting a cap that drops a confirmation.
From verified domain to confirmed delivery.
Verify your own domain, records managed.
Add your domain and publish the DKIM and MAIL FROM records Samva generates. Keep your existing DMARC policy, or add one separately when you are ready.
TYPE HOST PURPOSE STATUS
TXT _samva ownership verified
CNAME s1._domainkey DKIM verified
# samva signs outgoing mail once verifiedOne template, every order.
A versioned template holds the order-shipped email. Pass the order id and tracking link as templateData, and the pinned version renders the same layout every time.
template order-shipped
v3 published pinned
v2 archived
v1 archived
send { templateSlug: "order-shipped", templateData: { orderId: "A-1042" } }
# same template, every orderA delivery event drives the confirmation.
A signed message.delivered event tells your app the notification reached the recipient's provider, so a confirmation flow can trigger off real delivery instead of a guess.
POST /webhooks/samva
{ type: "message.delivered",
timestamp: "2026-07-08T09:42:14Z",
data: { messageId: "msg_7q2xk9mvt4znw8rh" } }
# mark the order confirmed in your appGet the domain right first.
Questions from store engineering.
What happens during a seasonal spike?
Sends past your plan's allowance bill as itemized overage, up to a monthly spend limit you control. A big week costs more, and no hard cap drops a confirmation.
How do I set up DMARC?
DMARC is an optional domain-wide TXT policy that complements SPF and DKIM. Samva does not create or replace it; start separately with `v=DMARC1; p=none; adkim=r; aspf=r` when you are ready to monitor.
Do order confirmations need one-click unsubscribe?
No. Order confirmations and shipping updates are transactional, triggered by something the recipient did, and RFC 8058's one-click unsubscribe requirement is scoped to marketing mail. If you also send promotional campaigns from the same account, those need the unsubscribe headers; your order emails don't.
How do I confirm a delivery for my own flows?
Register a webhook for message.delivered. The event carries the message id and a status of delivered once the recipient's provider confirms it, so your app can trigger a confirmation step off a real signal instead of assuming the send worked.
Get your next order confirmation to the inbox.
Verify your domain, then send the first templated order email.