Transactional email API — POST to one endpoint, no SMTP relay
Serverless runtimes can't talk to a traditional SMTP relay without a third-party bridge. Most teams bolt on SendGrid or Resend to fill that gap, which means a separate billing relationship, a separate dashboard, and a per-email fee. Flowmails removes the bolt-on: you POST to one endpoint (or use the Flowmails SDK from any runtime), and the message goes out through Cloudflare Email Sending — via a thin sender worker we deploy in your own account — or through Resend, whichever you picked for that domain. There is no SMTP relay, no per-email markup from Flowmails, and no shared sending IP from a SaaS. Transactional senders typically ship the first email in under an hour: connect the provider, verify the domain, mint an API key, hit the SDK.
What hurts today
The transactional email api pain points
Serverless runtimes can't natively SMTP — most teams bolt on SendGrid / Resend
Per-email pricing compounds fast at scale (10K+ transactional emails / month)
Hosted ESPs add a separate dashboard, separate billing, and a shared sending IP
How Flowmails answers
What you get instead
A single `POST` to the send endpoint from any HTTPS-capable runtime
Outbound goes through Cloudflare Email Sending or Resend — no SMTP relay, no per-email markup from us
Your domain sends from its own provider account, so DKIM / SPF / DMARC align automatically
FAQ
Common questions from transactional email api
Other personas