Transactional email
The message a product action requires.
Send verification, password resets, receipts, security alerts, and direct notifications through REST, Node, or SMTP.
- Verification
- Password reset
- Receipt
- Security alert
One email API for the whole SaaS lifecycle.
Send account email immediately. Run opted-in onboarding, lifecycle messages, and product updates through audiences, broadcasts, and automations. Every result is available in project logs and can return through signed webhooks.
Customer lifecycleOne project
user.createdVerify the accountTransactional APIdeliveredinvoice.paidSend the receiptTransactional APIacceptedcontact joins audienceStart onboardingAutomationstep 1 sentrelease readyShare the product updateBroadcastscheduledPro workspace$10 / month
Email meter25,000 / month
Active contacts10,000 included
Automation runs10,000 included
Two customer-email jobs
Keep the purpose clear. Share the infrastructure.
Transactional email follows a product action. Marketing and lifecycle email follows subscribed audience state. Both can use the same project, verified domains, templates, logs, and webhooks.
Marketing email
The update a subscribed customer asked to receive.
Run onboarding, product updates, changelogs, and newsletters through audiences, broadcasts, and lifecycle automations.
- Onboarding
- Product update
- Changelog
- Newsletter
Shared inside the projectVerified domainsTemplatesSuppressionsRecipient logsSigned webhooks
Real production paths
Three routes. No campaign maze.
Start each job from the state it actually uses. NoticeAPI keeps the operation narrow and the recipient result inspectable.
Immediate sendYour app handles a product eventCall REST, Node, or SMTPRead the recipient timelineLifecycle automationA subscribed contact enters an audienceRun one to five stored template stepsStop on unsubscribe or suppressionAudience broadcastChoose the subscribed audiencePreview, schedule, or sendInspect per-recipient results
Broadcasts and automations check subscription, unsubscribe, and project suppression state before sending.
When a customer asks
Show what happened after send.
The request, stored message, provider outcome, and signed event give support and product teams a useful answer without digging through worker logs.
Recipient timelineeml_7F2A
- AcceptedRequest stored and queued for delivery
now - DeliveredRecipient server accepted the message
+1s
email.deliveredSigned webhook · application returned 200
One operational record
The app and the operator read the same outcome.
Store the email ID beside the product action, fetch it when support needs context, or let the webhook update your application automatically.
Read email retrieval docsOperate the path
Open the exact layer you need.
Recipient timelinesRetrieve the stored email and its provider and recipient events.Signed webhooksPush delivery outcomes back into the product that initiated the send.Simulator outcomesExercise delivered, bounced, complained, and suppressed paths before production.Delivery controlsSuppress bad addresses, enforce sender state, and pause risky traffic.
First customer email
Put the email lifecycle back inside your product.
Start with one transactional send, then add the opted-in audience path when the product needs it.