Email API
Email API for transactional and marketing email you can prove
When a customer says the reset, receipt, or invite never arrived, NoticeAPI gives your team evidence. Send with REST, Node, or SMTP, inspect the recipient timeline, and push signed webhook outcomes back into your app.
curl -X POST https://www.noticeapi.com/api/v1/email/send \
-H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx" \
-H "Idempotency-Key: receipt-8412" \
-H "Content-Type: application/json" \
-d '{
"from": "Acme <[email protected]>",
"to": "[email protected]",
"subject": "Your receipt",
"html": "<p>Thanks for your purchase.</p>"
}'Send from the path you have
Call REST with JSON, install the zero-dependency Node SDK, or relay existing app mail through SMTP on port 465.
Recipient timelines on every send
Accepted, delivered, bounced, complained, and opened events stay attached to the message your app created.
Bad addresses stop early
Hard bounces, complaints, manual blocks, and opt-outs stop future sends before another provider call.
Simulator outcomes without real traffic
Trigger delivered, bounced, complained, and suppressed paths before production email or quota is involved.
Routing map
Pick the path that fits the job.
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 featureFull 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.
How it works
Test the path before customers depend on it.
Create an account API key
Keys start with ntc_ and authenticate REST, SDK, and SMTP traffic for the workspace.
Start with simulator recipients
[email protected] works with simulator addresses so delivery, bounce, complaint, and webhook paths can be tested before DNS is ready.
Verify your production domain
Add SPF, DKIM, and sender records for your domain. Free real sending also requires operator activation before production mail leaves NoticeAPI.
Turn outcomes into app state
Poll email status or subscribe to signed webhooks so delivery outcomes can update support, billing, or account workflows.
Trust
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.
Implementation links
Build with the shipped docs.
FAQ
Questions developers ask before switching email.
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 when you are ready to send real email; Free real sending also needs operator activation.
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.
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.