MailJunky for Logto
Send your Logto authentication emails through MailJunky. Verification codes, magic links, and password resets get delivered from your own verified domain, with the deliverability tooling and real-time analytics those emails demand.
Auth email is deliverability-critical
A marketing email in spam is a missed opportunity. A verification code in spam is a user who can't sign in. Logto handles the identity logic; MailJunky makes sure the email arrives.
Verification codes
Sign-up and sign-in one-time codes that have to land in the inbox, instantly.
Magic links
Passwordless sign-in links delivered from your own verified domain.
Password resets
Account recovery emails your users actually receive and trust.
Three steps to live
Verify a domain, create an API key, and add the MailJunky connector in Logto.
Verify your sending domain
In your MailJunky dashboard, add the domain you want auth emails to come from and add the DNS records we generate. MailJunky won't send from a domain until it's verified — exactly what you want for auth mail.
Open dashboardCreate an API key
In your dashboard, create a live API key with permission to send email. Logto uses it as a Bearer token when calling MailJunky's email API.
API keysAdd the connector in Logto
In the Logto Console, add the MailJunky email connector and paste your API key, From email, optional From name, and templates. Send a test, and Logto's verification, magic-link, and password-reset flows deliver through MailJunky.
About LogtoWhat to enter in Logto
Add the MailJunky email connector in the Logto Console and fill in these values from your MailJunky dashboard.
| Setting | Value |
|---|---|
| apiKey | Your MailJunky API key (mj_live_… or mj_test_…), used as a Bearer token against MailJunky's email API. |
| fromEmail | A verified sender address in MailJunky, e.g. [email protected]. |
| fromName | Optional display name for the From header, e.g. Your App. |
| templates | JSON array mapping each Logto flow (Register, SignIn, ForgotPassword, Generic, …) to a subject and body. Supports Handlebars placeholders like {{ code }} and {{ link }}. |
Your From email must be a verified sender in MailJunky — that's what keeps your auth mail aligned and deliverable. At minimum, define templates for Register, SignIn, ForgotPassword, and Generic (Logto falls back to Generic).
More than a mail relay
Keep Logto's identity features and templates. Get MailJunky's verified-domain sending, reputation isolation, and event tracking underneath them.
Verified custom domains
MailJunky only sends from domains you've verified with DKIM, SPF, and a dedicated return-path. Your codes arrive signed and aligned from your own domain.
Reputation isolation
Auth traffic is tracked per domain and kept separate from any marketing you send, so a campaign can never drag down the reputation your login flow depends on.
Real-time analytics
Delivery, open, click, and bounce data on every verification code and reset link. When a user says "I never got the code", you can see exactly what happened.
Verified senders only
MailJunky only sends from domains you've verified, and your From address must be a verified sender — so your auth mail stays aligned and hard to spoof.
Built for transactional
The same deliverability infrastructure behind MailJunky's email API, now behind Logto's auth email — no extra service to run.
Native connector
Logto ships a built-in MailJunky email connector. Paste your API key, From address, and templates, and you're live — no SMTP box to run.
Deliver your Logto emails from your own domain
Verify a domain, create an API key, and add the MailJunky connector in Logto. It takes a few minutes.