Drop-in SMTP relay
Auth0's custom SMTP fields point straight at NoticeAPI's implicit-TLS relay on port 465.
Auth0 decides what account email to send, but by default you can't see whether it landed. Point your tenant's custom SMTP provider at NoticeAPI and every verification, reset, and MFA message sends from your verified domain, into the same logs, suppressions, and signed webhooks as the rest of your mail.
SMTP host: smtp.noticeapi.com SMTP port: 465 TLS/SSL: enabled Username: noticeapi Password: ntc_xxxxxxxxxxxxxxxxxxxx From: Accounts <[email protected]>
Add your sending domain in NoticeAPI and publish its SPF and DKIM records.
Generate an API key (ntc_ prefix) and use it as the SMTP password.
In Auth0, choose custom SMTP and set host smtp.noticeapi.com, port 465, TLS on, and your From address.
Trigger a verification, reset, and MFA email, then watch each one resolve in the logs.
Auth0's custom SMTP fields point straight at NoticeAPI's implicit-TLS relay on port 465.
Verification, reset, and MFA mail sends from a domain you prove with SPF and DKIM.
Each Auth0 message lands in NoticeAPI logs, so support can read accepted, delivered, bounced, and suppressed for any account.
Signed webhooks push each outcome into your support desk or account systems as it happens.
Auth0 decides what account email to send and to whom. NoticeAPI is the delivery path for it, not a replacement: it does not manage your users, login policies, or mailboxes.
No. Auth0 still decides what account email to send and renders it. NoticeAPI is the SMTP delivery path underneath, plus the logs and events on top.
Yes. Auth0's SMTP sends enter the NoticeAPI send path, so each one shows up in the logs and recipient timeline with its delivery state.
No. This path is for transactional identity email. For subscribed-audience sends, use NoticeAPI broadcasts and audiences.
Simulator outcomes are free. Move to a verified domain when the path is ready.