Email Verification

Verification Flow

User signs up

A record is created in the user collection with emailVerified: false. Profile data is saved to the temporary userprofile collection.

Verification email sent

Better Auth generates a token stored in the verification collection and sends an email with a verification link.

User clicks the link

The link hits GET /api/auth/verify-email?token=...&callbackURL=/. Better Auth validates the token and sets emailVerified: true.

Welcome email triggered

The onEmailVerification callback fires, sends an Inngest event to trigger the welcome email, and cleans up the temporary profile data.

User can sign in

With emailVerified: true, the user can now authenticate normally.

In development (NODE_ENV=development), email verification is disabled. Users are auto signed-in after signup and verification URLs are logged to the console instead of emailed.

Configuration

Email verification is configured in lib/better-auth/auth.ts:

emailAndPassword: {
  enabled: true,
  requireEmailVerification: process.env.NODE_ENV === "production",
  autoSignIn: process.env.NODE_ENV === "development",
  sendVerificationEmail: async ({ user, url, token }) => {
    if (process.env.NODE_ENV === "development") {
      console.log("Verification URL:", url);
    } else {
      await sendVerificationEmail({ email: user.email, verificationUrl: url });
    }
  },
},
emailVerification: {
  sendOnSignUp: process.env.NODE_ENV === "production",
  autoSignInAfterVerification: true,
  onEmailVerification: async (user) => {
    // Triggers welcome email via Inngest
  },
}

Important: GET Not POST

The verification endpoint uses GET with query parameters, not POST with a JSON body.

// Correct
const verifyURL = new URL("/api/auth/verify-email", window.location.origin);
verifyURL.searchParams.set("token", token);
verifyURL.searchParams.set("callbackURL", callbackURL);

const response = await fetch(verifyURL.toString(), {
  method: "GET",
  redirect: "manual",
});

// Better Auth redirects on success (307/302)
if (response.status === 307 || response.status === 302 || response.ok) {
  // Verification succeeded
}

Email Template

The verification email uses a styled HTML template defined in lib/nodemailer/templates.ts with:

Gold/yellow CTA button matching the brand
24-hour expiry notice
Mobile-responsive layout
Dark mode support

All URLs in templates use the {{baseUrl}} placeholder, which is replaced at runtime with NEXT_PUBLIC_BASE_URL.

Database

Collection	Role
`user`	`emailVerified` field updated to `true` after verification
`verification`	Stores ephemeral tokens — deleted after use
`userprofile`	Temporary sign-up data — deleted after verification triggers welcome email

It’s normal for the verification collection to appear empty after a user verifies. Tokens are ephemeral and deleted once consumed.

Testing

Development
Production

Run npm run dev and sign up
Copy the verification URL from the terminal logs:

📧 EMAIL VERIFICATION (Development Mode)
To: test@example.com
Verification URL: http://localhost:3000/verify-email?token=...&callbackURL=/

Paste the URL in your browser
You should see “Email Verified!” and be redirected to sign-in

Sign up at your production URL
Check your inbox for the verification email
Verify the email contains a correct URL with ?token= parameter
Click the button — should redirect to sign-in
Sign in with the verified account

Getting Started

Authentication

Deployment

Verification Flow

Configuration

Important: GET Not POST

Email Template

Database

Testing

​Verification Flow

​Configuration

​Important: GET Not POST

​Email Template

​Database

​Testing

Verification Flow

Configuration

Important: GET Not POST

Email Template

Database

Testing