REST, Node SDK, or SMTP relay
Send JSON over REST, call the typed Node SDK, or point an existing SMTP mailer at smtp.noticeapi.com:465.
Send receipts, campaigns, and automations from one email API
Pick REST, the Node SDK, or SMTP. Every send — transactional, broadcast, or automated — lands on one delivery record your app and your support team can read.
- REST, Node SDK, or SMTP relay
- Send JSON over REST, call the typed Node SDK, or point an existing SMTP mailer at smtp.noticeapi.com:465.
- Recipient timelines on every send
- Accepted, delivered, bounced, complained, and suppressed events stay attached to the exact message your app sent.
- Bad addresses stop early
- Hard bounces, complaints, manual blocks, and unsubscribes go to suppressions, so the next send to that address is stopped before it leaves.
Built for the whole job.
Recipient timelines on every send
Accepted, delivered, bounced, complained, and suppressed events stay attached to the exact message your app sent.
Bad addresses stop early
Hard bounces, complaints, manual blocks, and unsubscribes go to suppressions, so the next send to that address is stopped before it leaves.
Simulator outcomes without real traffic
Trigger delivered, bounced, complained, and suppressed paths before production email or quota is involved.
Four ways to send, one place to watch them.
REST, the Node SDK, SMTP relay, and broadcasts each keep their own job while sharing the logs and webhooks that make delivery inspectable.
Browse every featureREST
Full payload control
Use direct JSON requests for Pro/Custom attachments, idempotency keys, custom headers, templates, and per-send tracking overrides.
SDKTyped Node calls
Install noticeapi when you want a small TypeScript wrapper around the REST contract.
SMTPDrop-in relay
Keep existing mailer settings for transactional mail while still using NoticeAPI logs and suppressions.
BroadcastsProduct updates from code
Use audiences and broadcasts for newsletters, product updates, and lifecycle sends; unsubscribe handling stays built in.
Test the path before customers depend on it.
- 1
Create an account API key
Keys start with ntc_ and authenticate REST, SDK, and SMTP traffic for the workspace.
- 2
Start with simulator recipients
[email protected] works with simulator addresses so delivery, bounce, complaint, and webhook paths can be tested before DNS is ready.
- 3
Verify your production domain
Add SPF, DKIM, and sender records for your domain. Free real sending also requires a card on file before production mail leaves NoticeAPI.
- 4
Turn outcomes into app state
Poll email status or subscribe to signed webhooks so delivery outcomes can update support, billing, or account workflows.
One email path, visible from send to outcome.
Transactional sends, broadcasts, and automations share recipient timelines, webhooks, suppressions, sender controls, and plan limits. Broadcast and lifecycle flows add unsubscribe and List-Unsubscribe behavior where the message type needs it.
Read the implementation.
Questions before you ship.
Can I send product updates too?
Yes. NoticeAPI includes audiences and broadcasts for product updates, newsletters, and lifecycle messages. Broadcasts include unsubscribe handling and share your plan quota.
Do I need DNS before testing?
No. Start with [email protected] and simulator recipients. Add a verified production domain and a card on file when you are ready to send real email.
Can support see what happened to a message?
Yes. Every send has an id, stored message details for the retention window, recipient events, and optional signed webhooks so support can see whether the message delivered, bounced, complained, or was suppressed.
What happens after a hard bounce?
The recipient is suppressed automatically. Future sends to that address fail with recipient_suppressed until you remove the suppression intentionally.
Test it. Then send for real.
Simulator outcomes are free. Move to a verified domain when the path is ready.