Use case

Send Contact Form Notification Emails

When a form submission should notify a team, NoticeAPI can be the outbound email layer. Use REST from your app, or SMTP relay from software that already has mail settings, then inspect logs and delivery events in one place.

SMTP settings for form software
host: smtp.noticeapi.com
port: 465
security: implicit TLS
username: noticeapi
password: ntc_xxxxxxxxxxxxxxxxxxxx
from: Forms <[email protected]>

Works with SMTP settings

Use smtp.noticeapi.com on port 465 for tools that already send through SMTP.

REST alternative

Custom apps can call the send API directly and include structured form details in HTML or text.

Verified sender domains

Production form notifications send from domains you verify with DNS.

Logs for debugging

Each notification appears in NoticeAPI logs and timelines so missed form alerts are easier to trace.

How it works

From test send to production traffic.

1

Pick REST or SMTP

Use REST when you own the code path; use SMTP when a site builder or CMS already exposes mail settings.

2

Verify the sender

Add DNS for the domain you want notification messages to come from.

3

Send a simulator test

Use sandbox and simulator addresses while the form workflow is still in development.

4

Monitor delivery

Use logs, email timelines, and webhooks to catch bounces or configuration mistakes.

Trust

Outbound notifications, clearly scoped

This use case is for sending notification email after a form submission. NoticeAPI does not collect form submissions for you; your app or site owns the form and decides what to send.

Implementation links

Build with the shipped docs.

FAQ

Questions developers ask before switching email.

Can I use this with a CMS contact form?

Yes, if the CMS or plugin can send through SMTP on port 465 with username and password authentication.

Does NoticeAPI store form submissions?

No. Your app or site owns the form data. NoticeAPI sends the notification email you provide.

Should form notifications use broadcasts?

No. Contact form notifications are transactional sends to your team. Broadcasts are for consent-based audience messages.

Start free. Send production after your domain is ready.

Free includes 3,000 production emails per month, a 100/day production cap, and one verified sending domain.