How do I get delivery webhooks for auth emails?

If you’re using an auth/email service, delivery webhooks for auth emails are only available if the provider exposes them for transactional/auth messages.

In general, the setup looks like this:

1. Enable webhooks in your email provider

   • Go to your provider’s dashboard.
   • Find webhooks / event notifications.
   • Subscribe to events like:
     • delivered
     • bounce
     • deferred
     • opened / clicked (if supported)
     • complained

2. Make sure auth emails are sent through that provider

   • OTPs, magic links, password resets, etc. must be sent via the same sending infrastructure that emits delivery events.
   • Some auth systems send emails through their own internal service and do not expose delivery webhooks directly.

3. Set your webhook endpoint

   • Create an HTTPS endpoint on your app.
   • Verify webhook signatures if the provider supports them.
   • Return a 2xx quickly.

4. Test with a known auth email

   • Send a password reset or login link.
   • Confirm the provider emits the event.

If you mean a specific service, the exact answer depends on it:

• Auth0: delivery webhooks are not generally provided for built-in auth emails; you typically customize email templates and use an external SMTP/email provider with its own event webhooks.
• Supabase: auth emails are sent via the configured SMTP provider; delivery tracking comes from that provider’s webhooks, not Supabase Auth itself.
• Firebase Auth: no direct delivery webhooks for auth emails.
• Clerk: email delivery events depend on their email sending setup/provider and webhook support.

If you tell me which auth service you’re using, I can give you the exact steps.