Send Supabase Auth Emails with NoticeAPI SMTP

Supabase Auth can send branded transactional email through an SMTP provider. NoticeAPI gives that setup an SMTP relay on port 465, API-key auth, verified sender domains, logs, suppressions, and the same delivery visibility as REST sends.

Create account Read SMTP docs

Supabase SMTP settings

Host: smtp.noticeapi.com
Port: 465
Secure: true
Username: noticeapi
Password: ntc_xxxxxxxxxxxxxxxxxxxx
Sender email: [email protected]
Sender name: Acme

SMTP relay settings

Use smtp.noticeapi.com on port 465 with implicit TLS and your ntc_ key as the password.

Verified sender domain

Production auth email sends from domains you verify with NoticeAPI DNS records.

Auth email visibility

Verification, magic link, and password reset sends appear in logs and delivery timelines.

Delivery outcomes

Signed webhooks can send bounce and delivery results back into your own operational workflow.

From test send to production traffic.

Verify a sending domain

Add and verify the domain you want Supabase Auth email to come from.

Create an API key

Use a NoticeAPI key as the SMTP password in Supabase settings.

Configure SMTP

Set host, port 465, secure mode, sender name, sender email, and credentials.

Send an auth test

Trigger a verification, reset, or magic link email and inspect the NoticeAPI log trail.

Supabase Auth email is transactional

Auth email is for verification, login, and account recovery. Sending product updates to Supabase users still requires audience broadcasts and unsubscribe handling.

Read the implementation.

SMTP docsConnection settings, implicit TLS, and authentication.Domain docsVerify sender DNS before production auth email.Magic link emailsSend passwordless login links with delivery visibility.Simulator testingTest NoticeAPI behavior before production traffic.

Questions before you ship.

Does NoticeAPI manage Supabase users?

No. Supabase owns authentication and user state. NoticeAPI relays the email and records delivery outcomes.

Which SMTP port should I use?

Use port 465 with implicit TLS and your NoticeAPI API key as the password.

Can I use the same account for broadcasts?

Yes, but broadcasts should use NoticeAPI audiences and unsubscribe handling, not the Supabase Auth SMTP path.

Test it. Then send from a verified domain.

Free includes simulator testing and 3,000 emails per month. Production sending on Free needs activation and a verified domain.

Create your account Compare plans