import type { EmailProvider } from './email';
import type { UserWithEmail } from './auth';
interface EmailCallbackParams {
    user: UserWithEmail;
    url: string;
    token: string;
}
/**
 * better-auth's own `/request-password-reset` route already builds `url` as
 * `${baseURL}/reset-password/${verificationToken}?callbackURL=${encodeURIComponent(redirectTo)}`
 * — the token lives in the path, `callbackURL` is already correctly encoded.
 * Use it as-is: appending a second `?token=` here (the previous behavior)
 * produces a value with two `?` characters whenever `redirectTo` itself
 * already carries a query string, which better-auth's own callback-URL
 * validation on the follow-up GET request rejects.
 */
export declare function sendResetPasswordCallback({ user, url, token: _token }: EmailCallbackParams, emailService: EmailProvider): Promise<void>;
/**
 * better-auth's own `/send-verification-email` route already builds `url` as
 * `${baseURL}/verify-email?token=${token}&callbackURL=${callbackURL}` — both
 * params correctly `&`-joined. Use it as-is instead of rebuilding a
 * token-only URL, which silently dropped any `callbackURL` a caller supplied.
 */
export declare function sendVerificationEmailCallback({ user, url, token: _token }: EmailCallbackParams, emailService: EmailProvider): Promise<void>;
export {};
//# sourceMappingURL=auth-email-callbacks.d.ts.map