SMTP Relay with Nodemailer and NoticeAPI
If your app already sends with Nodemailer, NoticeAPI can become the SMTP relay without changing your mailer architecture. Use port 465 with implicit TLS, put your ntc_ API key in the password field, and keep the same logs and suppressions as REST sends.
import nodemailer from "nodemailer";
const transport = nodemailer.createTransport({
host: "smtp.noticeapi.com",
port: 465,
secure: true,
auth: {
user: "noticeapi",
pass: process.env.NOTICEAPI_API_KEY,
},
});
await transport.sendMail({
from: "Acme <[email protected]>",
to: "[email protected]",
subject: "Your receipt",
html: "<p>Thanks for your order.</p>",
});Port 465 implicit TLS
Use smtp.noticeapi.com on port 465 with secure true. Do not configure STARTTLS for this endpoint.
API key password
The username is ignored; authenticate with an ntc_ API key as the SMTP password.
Same delivery trail
Relayed messages appear in NoticeAPI logs and email timelines alongside REST and SDK sends.
Same safety layer
Verified domains, quotas, suppressions, and deliverability autopilot still apply to SMTP mail.
From test send to production traffic.
Create an API key
Use any NoticeAPI API key as the SMTP password.
Configure Nodemailer
Set host, port 465, secure true, any username, and the API key password.
Send a sandbox test
Use [email protected] with simulator recipients while checking that your app can connect and queue mail.
Verify production DNS
Production from addresses must use a verified sending domain.
SMTP compatibility without a separate email product
SMTP relay is a compatibility path for transactional app mail. Use Pro or Custom REST sends when you need attachments, and use broadcasts when an audience update needs contact state, scheduling, and stats.
Read the implementation.
Questions before you ship.
Does Nodemailer need STARTTLS?
No. Configure port 465 with secure true for implicit TLS.
Can I send attachments through SMTP?
Not today. SMTP attachments are dropped in v0. Use the REST send API on Pro or Custom for attachments.
Can I use SMTP for newsletters?
Use the broadcasts API for audience sends so unsubscribe links, List-Unsubscribe headers, and subscribed contact state are enforced.
Test it. Then send from a verified domain.
Free includes simulator testing and 3,000 emails per month. Production sending on Free needs activation and a verified domain.