Oct 10, 2026
Partner mail: your product's email, sent from the partner's domain
Send your product's email through one endpoint, and each white-label partner's customers get it from that partner's own address. We handle the keys and the DNS checks.
New
POST /api/mail/send with a mail:send key. Pass a partner id or the customer's account id and the message goes out from that partner's verified sender, DKIM-signed for their domain. With no partner, or one that hasn't finished setup, it goes out from your own sender.
Email sender setup for partners: enter a name, an address and a reply-to, and we generate the DKIM key and show the DKIM, SPF, and DMARC records to publish. The private key is encrypted and never shown to anyone.
DNS is checked when you press Verify and again on a schedule: daily for verified senders, hourly for the rest. A verified sender is only marked failed after three missed checks in a row.
Idempotency keys in the body or an Idempotency-Key header, kept for at least 7 days. A 4xx is always final and a 5xx or 429 is always safe to retry, so you know when to fall back to your own mailer.
Receipts at GET /api/mail/messages/{id}, plus mail.sent and mail.failed webhooks. Message bodies are never stored, and erasing a contact removes their address from every receipt.
A Mail senders tab in the admin shows every partner's sender and DNS status. Partners set theirs up under Settings, Domains & email.
Two MCP tools for coding agents: get_partner_mail_identity, which tells you who a send would come from and why, and send_test_mail.
Partners who already uploaded their own DKIM key can verify it on the same card, and it then works the same way.