Already sending over SMTP? Reroute it, don't rewrite it.

Keep the mailer. Change the relay. Point the framework, CMS, plugin, or legacy app you already run at smtp.noticeapi.com:465 over implicit TLS with an ntc_ key, and its logs, suppressions, quotas, and delivery events land in NoticeAPI.

Create account Read SMTP docs
  1. 1
    Find the existing mail settingsOpen the framework, CMS, plugin, or app configuration that already sends transactional mail.
  2. 2
    Set host, port, TLS, and passwordUse smtp.noticeapi.com, port 465, implicit TLS, any username, and an ntc_ API key as the password.
  3. 3
    Send from a verified domainVerify the sending domain so production mail leaves with your own SPF and DKIM.
  4. 4
    Route audience mail elsewhereUse broadcasts or automations when audience state, unsubscribe handling, and List-Unsubscribe headers matter.

Wire in the relay without new send code.

  1. 1

    Find the existing mail settings

    Open the framework, CMS, plugin, or app configuration that already sends transactional mail.

  2. 2

    Set host, port, TLS, and password

    Use smtp.noticeapi.com, port 465, implicit TLS, any username, and an ntc_ API key as the password.

  3. 3

    Send from a verified domain

    Verify the sending domain so production mail leaves with your own SPF and DKIM.

  4. 4

    Route audience mail elsewhere

    Use broadcasts or automations when audience state, unsubscribe handling, and List-Unsubscribe headers matter.

Three ways in. SMTP is the one you don't rewrite.

SMTP carries a single message from code you already have. Reach for REST or broadcasts when you need payload control or an audience.

SMTP

Existing mailer settings

Use smtp.noticeapi.com:465 when a framework, CMS, plugin, or legacy app already exposes SMTP fields.

REST

Payload control

Use the send API when you need attachment payloads, exact JSON control, or repeat-safe idempotency keys.

Broadcasts

Audience sends

Use broadcasts or automations when audience membership, unsubscribe state, and one-click headers matter.

The controls around the path.

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.

The relay runs the same guardrails as REST.

Every relayed message flows through the same sender checks, suppressions, quotas, delivery events, logs, and deliverability autopilot that REST sends do.

Read the implementation.

SMTP docsConnection settings and framework examples.Errors and limitsRecipient, quota, and content limits for sends.SimulatorTest delivery outcomes before production traffic.REST send APIUse REST for attachments and full payload control.

Questions before you ship.

Does SMTP support attachments?

Attachments go through the REST send API, not the SMTP relay. Send those messages with a POST to /api/v1/email/send.

Can I use SMTP for broadcasts?

SMTP relays one message at a time. For marketing sends, use the broadcasts API so audience state, unsubscribe links, and one-click List-Unsubscribe are handled for you.

Will SMTP sends show in the dashboard?

Yes. Relayed messages become normal NoticeAPI sends, with the same logs and delivery timelines as REST.

Test it. Then send for real.

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

Create your account Compare plans