Configure Nodemailer SMTP Transport for High Deliverability

Your app already sends with Nodemailer, and rebuilding that path is the last thing you want to do. Change three transport fields (the host, port 465 with implicit TLS, and an ntc_ key in the password) and every message routes through NoticeAPI. Those sends land in the same logs, suppressions, and delivery events as your REST and SDK calls.

Get an API key Read the SMTP docs
Shortest working path
Nodemailer transport
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 <billing@acme.com>",
  to: "customer@example.com",
  subject: "Your receipt",
  html: "<p>Thanks for your order.</p>",
});

Connect it, test it, then move traffic.

  1. Create an API key

    Any NoticeAPI API key doubles as the SMTP password.

  2. Configure Nodemailer

    Set the host, port 465, secure true, any username, and the API key as the password.

  3. Send a sandbox test

    Set the sender to demo@sandbox.noticeapi.com and target a simulator inbox such as delivered@simulator.noticeapi.com; mail landing in the queue confirms your app is connecting.

  4. Verify production DNS

    Production senders must use a domain you have verified for sending.

What remains visible after integration.

Port 465, implicit TLS

Connect to smtp.noticeapi.com on port 465 with secure true. This endpoint does not use STARTTLS.

The key is your password

The username is ignored. Authenticate with an ntc_ API key in the SMTP password field.

One delivery record

Relayed messages land in the same logs and recipient timelines as your REST and SDK sends.

Guardrails still apply

Verified domains, quotas, suppressions, and deliverability autopilot cover SMTP mail too.

Where the relay fits your stack

The SMTP relay carries transactional app mail through your existing Nodemailer setup. Reach for REST on a paid plan when a message needs attachments, and for broadcasts when an audience send needs contact state, scheduling, and stats.

Read the implementation.

SMTP relayWhat the relay is and how sends flow through NoticeAPI.SMTP docsConnection settings and framework examples.SimulatorTest delivery outcomes before production DNS is ready.REST send APISwitch to REST when you need attachments and full payload control.

Questions before you ship.

Does Nodemailer need STARTTLS?

No. Set port 465 with secure true; the connection is TLS from the first byte, so STARTTLS never comes into play.

Can I send attachments through SMTP?

SMTP attachments are not supported. Send those messages through the REST API on a paid plan, which supports attachments.

Can I use SMTP for newsletters?

Yes. Use NoticeAPI broadcasts for newsletters instead of raw SMTP. Broadcasts keep subscribed-contact state, unsubscribe handling, scheduling, and recipient stats together.

Test in the simulator, then send from a verified domain.

Simulator outcomes are free. Move to a verified domain when the path is ready.

Create your account Compare plans