Section Overview
StackShift Mail
Send product email through StackShift Mail with verified sender domains, templates, OTP, events, webhooks, bounces, reputation controls, scheduled delivery, batch sending, inbound capture, and analytics.
StackShift Mail overview
A verified map of the current StackShift Mail surface: outbound send, sender domains, bounces, suppressions, templates, OTP, events, webhooks, reputation, scheduled mail, batch mail, inbound mail, attachments, and analytics.
Goal
Understand exactly what StackShift Mail does today and which API surface owns each workflow.
Expected result
You can choose the correct StackShift Mail API for each email workflow and avoid relying on assumptions that are not implemented.
Send email
Send a single outbound email with the official SDK or REST API, then inspect the message, attempts, logs, and timeline.
Goal
Queue a message safely and understand the exact response and lifecycle fields returned by StackShift Mail.
Expected result
The API returns a message id, status, and idempotencyStatus. The message is then visible in the message APIs and dashboard.
Sender domains and DNS
Create and verify outbound sender domains, inspect SPF, DKIM, DMARC, and return-path record status, and know what the domain status fields mean.
Goal
Move a domain from pending to verified before using it as a production sender.
Expected result
The sender domain has status verified and individual SPF, DKIM, DMARC, and return-path checks are not missing or failed.
Templates and OTP
Create versioned templates, preview and test them, send from a template, and use the built-in one-time-code challenge flow.
Goal
Use reusable email templates and OTP challenges without storing plaintext OTP codes in your application.
Expected result
Template sends are rendered server-side, missing variables fail before queueing, and OTP challenges record status and attempt counts.
Events, webhooks, and timelines
List mail events, inspect per-message timelines, subscribe webhooks, rotate secrets, retry deliveries, and verify webhook signatures.
Goal
Build reliable downstream automation from StackShift Mail events without trusting unsigned payloads.
Expected result
Your application processes mail lifecycle events once, verifies signatures, and can recover failed webhook deliveries.
Bounces, suppressions, and reputation
Handle hard and soft bounces, workspace-scoped suppressions, sending limits, warmup stage, domain reputation, and reputation events.
Goal
Operate Mail volume without repeatedly sending to addresses or domains that should be blocked or throttled.
Expected result
High-risk recipients are suppressed, hard bounces stop repeat sends, and operators can see current usage limits and reputation posture.
Scheduled, batch, inbound, attachments, and analytics
Use the Mail APIs for scheduled delivery, batch sending, batch-template sending, inbound domain capture, asset-backed attachments, and aggregate analytics.
Goal
Use the advanced Mail APIs for workflows that need delayed delivery, fan-out, inbound capture, attachments, or reporting.
Expected result
Mail workflows that need delay, fan-out, inbound capture, or reporting can use first-class APIs instead of ad hoc application jobs.