SMTP relay
SMTP Relay for app mail
Keep the mailer. Change the relay. Point a framework, CMS, plugin, or legacy app at smtp.noticeapi.com:465 with implicit TLS and an ntc_ key; logs, suppressions, quotas, and delivery events stay in NoticeAPI.
import nodemailer from "nodemailer";
const transport = nodemailer.createTransport({
host: "smtp.noticeapi.com",
port: 465,
secure: true,
auth: {
user: "noticeapi",
pass: process.env.NOTICEAPI_KEY,
},
});
await transport.sendMail({
from: "Acme <[email protected]>",
to: "[email protected]",
subject: "Your receipt",
html: "<p>Thanks.</p>",
});Port 465, implicit TLS
Use smtp.noticeapi.com on port 465 with implicit TLS. Do not configure STARTTLS or port 587 for this relay.
API key as password
The username is ignored; put an ntc_ API key in the password field and rotate it like any account key.
Verified senders only
The From domain must be verified, and quota, account-health, and suppression checks still run before handoff.
Logs after relay
Each relayed message gets a NoticeAPI record, delivery timeline, and webhook-visible delivery outcomes.
Routing guide
Use SMTP when rewriting the sender is the wrong job.
The relay keeps existing mail settings useful without blurring product boundaries. Pick the surface that matches the work.
Existing mailer settings
Use smtp.noticeapi.com:465 when a framework, CMS, plugin, or legacy app already exposes SMTP fields.
RESTPayload control
Use the send API when you need attachment payloads, exact JSON control, or repeat-safe idempotency keys.
BroadcastsAudience sends
Use broadcasts or automations when audience membership, unsubscribe state, and one-click headers matter.
How it works
Change the relay, not the app.
Find the existing mail settings
Open the framework, CMS, plugin, or app configuration that already sends transactional mail.
Set host, port, TLS, and password
Use smtp.noticeapi.com, port 465, implicit TLS, any username, and an ntc_ API key as the password.
Send from a verified domain
Production relay traffic still requires a verified sending domain before real mail leaves NoticeAPI.
Route audience mail elsewhere
Use broadcasts or automations when audience state, unsubscribe handling, and List-Unsubscribe headers matter.
Trust
A compatibility path, not a reputation shortcut.
Relayed messages still flow through NoticeAPI sender checks, suppressions, quotas, delivery events, logs, and the deliverability autopilot.
Implementation links
Build with the shipped docs.
FAQ
Questions developers ask before switching email.
Does SMTP support attachments?
Not in the SMTP sidecar today. Use the REST send API for attachment payloads.
Can I use SMTP for broadcasts?
Use the broadcasts API for marketing sends so unsubscribe links, audience state, and List-Unsubscribe headers are handled correctly.
Will SMTP sends show in the dashboard?
Yes. Relayed messages become normal NoticeAPI sends with logs and delivery timelines.
Start in the sandbox, then send from a verified domain.
Free includes simulator testing and 3,000 emails per month. Real sending on Free needs operator activation plus a verified domain; Pro adds more volume, domains, contacts, automation runs, REST attachments, and visible usage billing.