// Server-only — syncs newsletter opt-ins to Brevo's Contacts API via the
// double-opt-in endpoint: this only ever *requests* a subscription, it
// does not add the contact to the real list itself — Brevo sends the
// confirmation email (the template at BREVO_DOUBLE_OPTIN_TEMPLATE_ID,
// configured as this list's Double Opt-in template in Brevo's own UI) and
// only adds the contact to BREVO_LIST_ID once they click through. This
// app never sends marketing mail itself, and — as of this switch — never
// even directly grants list membership; it only ever hands Brevo the
// contact + consent-to-be-asked. Everything after that (the confirmation
// email itself, the post-confirmation Welcome Flow automation) is
// configured in Brevo's own UI, not manageable via their public API.
//
// Previously called the plain `POST /v3/contacts` upsert (single
// opt-in — added straight to the list, no confirmation click required).
// Switched 2026-07-25 per explicit request once the confirmation-email
// template existed to point templateId at.
const BREVO_DOUBLE_OPTIN_URL = "https://api.brevo.com/v3/contacts/doubleOptinConfirmation";

export type BrevoSyncResult = { ok: true } | { ok: false; reason: string };

export type NewsletterOptInSource = "checkout" | "newsletter-page" | "newsletter-modal" | "newsletter-hero" | "challenge";

// `source` becomes a Brevo contact attribute so campaigns/segments can
// tell a checkout opt-in apart from the standalone signup forms without
// needing separate lists.
export async function upsertNewsletterContact(
  email: string,
  source: NewsletterOptInSource,
): Promise<BrevoSyncResult> {
  const apiKey = process.env.BREVO_API_KEY;
  const listId = process.env.BREVO_LIST_ID;
  const templateId = process.env.BREVO_DOUBLE_OPTIN_TEMPLATE_ID;
  if (!apiKey || !listId || !templateId) {
    return { ok: false, reason: "BREVO_API_KEY/BREVO_LIST_ID/BREVO_DOUBLE_OPTIN_TEMPLATE_ID nicht konfiguriert." };
  }
  // No dedicated "danke, bestätigt" landing page exists yet — falls back
  // to the homepage rather than blocking double opt-in on that page
  // existing first. Revisit once one exists.
  const redirectionUrl = process.env.BREVO_DOI_REDIRECT_URL || "https://einfach-produktiv.mk360.de/";

  try {
    const res = await fetch(BREVO_DOUBLE_OPTIN_URL, {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
        "api-key": apiKey,
      },
      body: JSON.stringify({
        email,
        includeListIds: [Number(listId)],
        templateId: Number(templateId),
        redirectionUrl,
        attributes: { OPT_IN_SOURCE: source },
      }),
      signal: AbortSignal.timeout(8000),
    });
    // 201 Created is this endpoint's success status (unlike the plain
    // contacts upsert this replaced, which used 204). A contact who's
    // already confirmed-and-subscribed re-submitting the form is not
    // treated as an error either — Brevo resends the confirmation email
    // in that case rather than erroring, which is an acceptable no-op
    // resend from this app's point of view (matches the previous
    // endpoint's "always succeeds for an existing contact too" behavior).
    if (res.ok || res.status === 201) return { ok: true };
    const body = await res.json().catch(() => null);
    return { ok: false, reason: body?.message ?? `Brevo antwortete mit ${res.status}` };
  } catch (err) {
    return { ok: false, reason: err instanceof Error ? err.message : "Brevo ist gerade nicht erreichbar." };
  }
}