Skip to content
Faivelo Docs

Transactional email

Transactional email is the mail your application sends — receipts, password resets, magic links, shipping updates, alerts. It’s one-to-one, triggered by something a user did, and it needs to arrive now.

Faivelo’s transactional email gives you:

  • A send API — POST /api/v1/emails sends from any address on one of your verified domains. No mailbox needs to exist for the sender: receipts@yourdomain.com works the moment the domain is verified.
  • Designed templates — build the email once in the visual template editor, then trigger it from code with an alias and variables. See Templates.
  • Delivery tracking — every send has a status (sent → delivered, bounced, complained, or failed) you can poll, plus webhooks that push those events to your server as they happen.
  • Automatic suppression — addresses that previously hard-bounced or complained are dropped before sending, so a stale address in your database can’t damage your domain’s reputation.
  • Safe retries — send an Idempotency-Key header and a retried request returns the original result instead of emailing your customer twice.

Who can use it

Transactional email is included on every paid plan: Starter sends 500 a month, Growth 10,000, Pro 100,000 and Business 250,000 — at 10/30/60/120 recipients a minute respectively (see rate limits). Transactional volume is a separate budget from campaigns, so a newsletter can never eat your password resets. Delivery webhooks are included from Pro. Every signed-in account can browse the Templates section and explore the editor. See Billing & plans.

Transactional vs. campaigns

TransactionalCampaigns
Triggered byYour code, one recipient at a timeYou, to a whole list
ExamplesReceipts, resets, alertsNewsletters, announcements, outreach
Sent viaAPI (POST /api/v1/emails)Dashboard campaign wizard
Unsubscribe footerNot added (it’s not marketing)Added automatically
Counts againstYour monthly sending limitYour monthly sending limit

Both kinds of sending draw from the same monthly pool and the same account-level sending limits.

Getting started

  1. Verify a domain (you’ve probably done this already).
  2. Create an API key with the mail:send scope — see AI agents & API keys.
  3. Send your first email — see Sending via the API.
  4. Optional: design a template and add a webhook for delivery events.