Verify email - Kerne

A verification email can carry a 6-digit code, a link, or both - decided by the tenant’s own configuration, not by this call. There’s also one legacy single-token method, kept for compatibility.

// Send a verification email - throttled client-side, 60s cooldown
await kerne.auth.sendVerificationEmail();

// Verify with the 6-digit code
const { success, needsTokenRefresh } = await kerne.auth.verifyEmailWithCode('483920');

// Or verify with the link's token (public route, no session needed)
await kerne.auth.verifyEmailWithLink(tokenFromLink);

// Check current status
const { emailVerified, needsVerification, email } = await kerne.auth.getVerificationStatus();

sendVerificationEmail() still takes a 'code' | 'link' first argument for backward compatibility, but it’s never sent to the server - passing it has no effect.

needsTokenRefresh: true means the access token’s email_verified claim is now stale - call refreshToken() to get one that reflects the new status.

Legacy single-token verify

await kerne.auth.verifyEmail(tokenFromEmail);

Prefer the code/link flow above for new integrations - this is the older, simpler variant kept for compatibility.