Send
Start with REST or SDK sends, then add templates, batching, scheduling, or paid REST attachments as your app grows.
Transactional sends, broadcasts, automations, and inbound receiving — one account, pooled across projects, ready for your code or an agent.
Start with the job your product needs today. The same projects, keys, domains, and delivery controls stay useful as the product grows.
Start with the job your product has today: send, market, automate, or receive.
Receipts, resets, verifications, and alerts over REST, the Node SDK, or the SMTP relay — with templates, batching, scheduling, and duplicate-send protection on the REST and SDK paths.
UpdateAudiences, broadcasts, and newsletters with one-click unsubscribe and shared suppressions.
AutomateAudience triggers, reusable template steps, timed delays, and stop conditions your app or agent can operate.
RouteReceiving domains, signed email.received webhooks, and retrieval APIs for message bodies and attachments.
These links go deeper on limits, code, and plan notes once you know the job.
Start with REST or SDK sends, then add templates, batching, scheduling, or paid REST attachments as your app grows.
Give support a clear receipt trail: recipient state, stored content, tracking events, suppression state, and signed callbacks.
Send audience-backed product updates and lifecycle messages with contact state, schedules, and automations.
Keep older mailers, inbound workflows, agent keys, and simulator tests in the same account and log timeline.
Use one send path for account, billing, and product flows so you can debug from one timeline.
Search a recipient, inspect the stored body, see the stop reason, and follow the signed event back to your app.
Sender ramps, auto-pause, and suppressions run on the send path — and the simulator lets you rehearse a bounce or complaint before production traffic ever sees it.
Keep audiences, broadcasts, and automations in the same logs, suppressions, domains, and dashboard.
Inbound is API receiving for product workflows, not a human inbox. Verify domains, receive webhook events, and fetch message bodies when your app needs them.
REST APIs, the Node SDK, the SMTP relay, scoped keys, and receiving all run under one workspace and one set of usage controls.
Copy a key, verify your sending domain, and use the API, SDK, SMTP, or an agent to wire the email into your product.