@wix/agent-skills 1.8.0 → 1.10.0

package/skills/wix-manage/references/bookings/create-course-service.md

@@ -0,0 +1,237 @@
+---
+name: "Create Course Service"
+description: "Create a course booking service — e.g. 'create a 6-week photography workshop', 'set up a training program', 'add a bootcamp course for $300', 'create a teacher training course'. Handles group capacity, full-course pricing, and fixed series defaults via bulkCreateServices API. Staff assignment is not used for courses."
+---
+
+# Create Course Service from Prompt
+
+## When to Use
+
+- User wants to create a multi-session course: "create a training program", "set up a 6-week workshop", "add a bootcamp course", "create a teacher training course"
+- The service type is COURSE — a fixed series with pre-defined start and end dates
+- Customers must book the entire course (all sessions), unlike CLASS where they can pick individual sessions
+- For general service creation where the type is ambiguous, see [Create Booking Service from Prompt](./create-booking-service-from-prompt.md)
+
+## Prerequisites
+
+- **Wix Bookings app installed** (App ID: `13d21c63-b5ec-5912-8397-c3a5ddb27a97`). Use [List Installed Apps](../app-installation/list-installed-apps.md) to verify, and [Install Wix Apps](../app-installation/install-wix-apps.md) to install if missing.
+- For full API field definitions, validation rules, and troubleshooting, see [Create and Update Booking Services](./create-and-update-booking-services.md)
+
+---
+
+## Step 1: Gather Business Context
+
+Run these queries to collect site data for informed defaults.
+
+### 1a. Query Service Categories
+
+```bash
+curl -X POST 'https://www.wixapis.com/bookings/v2/categories/query' \
+  -H 'Authorization: <AUTH>' \
+  -H 'Content-Type: application/json' \
+  -d '{ "query": {} }'
+```
+
+### 1b. Get Site Currency
+
+```bash
+curl -X GET 'https://www.wixapis.com/site-properties/v4/properties' \
+  -H 'Authorization: <AUTH>'
+```
+
+Extract `properties.paymentCurrency`. Fall back to `USD` if unavailable.
+
+### 1c. Query Existing Services (Duplicate Check)
+
+```bash
+curl -X POST 'https://www.wixapis.com/bookings/v2/services/query' \
+  -H 'Authorization: <AUTH>' \
+  -H 'Content-Type: application/json' \
+  -d '{ "query": { "paging": { "limit": 100 } } }'
+```
+
+Warn the user if a service with a similar name already exists.
+
+> **Note:** Staff queries are optional for COURSE services since `staffMemberIds` is ignored by the API. However, querying staff can still be useful for context (e.g., mentioning the instructor in the description).
+
+---
+
+## Step 2: Apply Course Defaults
+
+For any fields the user did not explicitly specify:
+
+| Field | Default | Notes |
+|---|---|---|
+| Capacity | 10 | `defaultCapacity` — required for COURSE |
+| Online booking | Enabled | `onlineBooking.enabled: true` |
+
+### Pricing (if not specified)
+
+- Use the site's currency from Step 1b
+- If user specifies a price → `rateType: "FIXED"` (for the entire course)
+- If user says "free" → `rateType: "NO_FEE"`, `options.inPerson: true`, `options.online: false`
+- If no price mentioned → infer from context (workshops ~$100-300, training programs ~$200-500, bootcamps ~$150-400) or default to free
+- **Course pricing is for the full course**, not per session — remind the user of this in the summary
+
+### Capacity (if not specified)
+
+- Default: 10 participants
+- If user mentions group size → use their number
+- Typical ranges: intensive 5-10, standard 10-20, lecture-style 20-50
+
+### Category
+
+- If categories exist → assign the most relevant one (e.g., "Training", "Workshops")
+- If no categories exist → create one:
+```bash
+curl -X POST 'https://www.wixapis.com/bookings/v2/categories' \
+  -H 'Authorization: <AUTH>' \
+  -H 'Content-Type: application/json' \
+  -d '{ "category": { "name": "General" } }'
+```
+
+### Service Name & Description
+
+- Use the user's wording for the service name
+- Generate a brief, professional description (1-2 sentences) mentioning it's a multi-session course
+- If the user specified the number of sessions or duration, include that in the description
+
+---
+
+## Step 3: Create the Course Service
+
+**CRITICAL: COURSE services do NOT use `staffMemberIds` or `sessionDurations`.** These fields are ignored. Use `defaultCapacity` instead.
+
+**Paid course:**
+
+```bash
+curl -X POST 'https://www.wixapis.com/bookings/v2/bulk/services/create' \
+  -H 'Authorization: <AUTH>' \
+  -H 'Content-Type: application/json' \
+  -d '{
+    "services": [{
+      "name": "<SERVICE_NAME>",
+      "description": "<GENERATED_DESCRIPTION>",
+      "type": "COURSE",
+
+      "onlineBooking": { "enabled": true },
+      "defaultCapacity": <CAPACITY>,
+      "payment": {
+        "rateType": "FIXED",
+        "options": { "online": true, "inPerson": false },
+        "fixed": {
+          "price": { "value": "<PRICE>", "currency": "<CURRENCY>" }
+        }
+      },
+      "category": {
+        "id": "<CATEGORY_ID>"
+      }
+    }]
+  }'
+```
+
+**Free course:**
+
+```bash
+curl -X POST 'https://www.wixapis.com/bookings/v2/bulk/services/create' \
+  -H 'Authorization: <AUTH>' \
+  -H 'Content-Type: application/json' \
+  -d '{
+    "services": [{
+      "name": "<SERVICE_NAME>",
+      "description": "<GENERATED_DESCRIPTION>",
+      "type": "COURSE",
+
+      "onlineBooking": { "enabled": true },
+      "defaultCapacity": <CAPACITY>,
+      "payment": {
+        "rateType": "NO_FEE",
+        "options": { "online": false, "inPerson": true }
+      },
+      "category": {
+        "id": "<CATEGORY_ID>"
+      }
+    }]
+  }'
+```
+
+### COURSE-Specific Reminders
+
+- Do **NOT** include `staffMemberIds` — it is ignored for COURSE services
+- Do **NOT** include `schedule.availabilityConstraints.sessionDurations` — not used for COURSE
+- `defaultCapacity` is **required** — sets max participants for the entire course
+- Customers must book the **entire course** (all sessions), not individual sessions
+- After creation, course sessions must be scheduled separately via `bulkCreateEvents` using the returned `service.schedule.id` (see [Create and Update Booking Services](./create-and-update-booking-services.md))
+
+Save the `serviceId` from the response: `results[0].item.service.id`
+
+---
+
+## Step 4: Summary Message
+
+Provide a summary including:
+
+1. **What was created** — service name, total course price, capacity
+2. **Assumptions made** — list defaults used (e.g., "I set the capacity to 10 participants since you didn't specify")
+3. **Pricing clarification** — note that the price is for the entire course, not per session
+4. **Schedule note** — remind the user that course sessions (dates and times) still need to be set up
+5. **Next steps** — "Click Save to finalize, then set up the course schedule"
+6. **Offer to adjust** — "Want me to change the price, capacity, or description?"
+
+**Example:**
+
+> I created **"Yoga Teacher Training"**:
+>
+> - **Type**: Course (customers book the full program)
+> - **Price**: $300 for the full course
+> - **Capacity**: 10 participants
+> - **Category**: Training
+>
+> I assumed a capacity of 10 since you didn't specify. The price of $300 covers the entire course — customers pay once for all sessions. You can review and adjust the details in the service form.
+>
+> **Next step:** You'll need to set up the course schedule (specific session dates and times) in the service form.
+
+---
+
+## Error Handling
+
+| Error | Cause | Action |
+|---|---|---|
+| 428 "App not installed" | Bookings not installed | Install using [Install Wix Apps](../app-installation/install-wix-apps.md) |
+| 400 "INVALID_PAYMENT_OPTIONS" | Payment misconfigured | Free: `inPerson: true`, `online: false`. Paid: price > 0 |
+| 403 | Permission denied | Inform user they lack permission |
+
+---
+
+## Payment Validation Quick Reference
+
+| rateType | `options.online` | `options.inPerson` | Valid? |
+|----------|------------------|-------------------|--------|
+| FIXED    | true             | false             | ✓      |
+| FIXED    | false            | true              | ✓      |
+| FIXED    | true             | true              | ✓      |
+| NO_FEE   | false            | true              | ✓      |
+| NO_FEE   | true             | false             | ✗      |
+| Any      | false            | false             | ✗      |
+
+---
+
+## What This Skill Does NOT Cover
+
+- **Course schedule setup** — individual session events (dates/times) must be configured separately via Calendar Events API. See [Create and Update Booking Services](./create-and-update-booking-services.md) Step 3.
+- **Pricing plans** — memberships or installment payments are separate. See [Create and Update Pricing Plans](../pricing-plans/create-and-update-pricing-plans.md)
+- **Instructor assignment** — `staffMemberIds` is ignored for COURSE. Staff association is managed through calendar events.
+- **Service images** — requires Media Manager API (see [create-and-update-booking-services.md](./create-and-update-booking-services.md))
+
+---
+
+## API Documentation Reference
+
+- [Bulk Create Services](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/bulk-create-services)
+- [Query Services](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/query-services)
+- [Query Categories](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/categories-v2/query-categories)
+- [Create Category](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/categories-v2/create-category)
+- [Bulk Create Events](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/bulk-create-event)
+- [Site Properties](https://dev.wix.com/docs/api-reference/business-management/site-management/site-properties/properties/read)
+- [About Service Types](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/about-service-types)
+- [About Service Payments](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/about-service-payments)

package/skills/wix-manage/references/cms/cms-data-items-crud.md

@@ -10,7 +10,7 @@ This recipe covers basic Create, Read, Update, Delete (CRUD) operations for Wix
 
 ## Prerequisites
 
-1. Wix CMS enabled on the site
+1. Wix CMS enabled on the site (appDefId: `e593b0bd-b783-45b8-97c2-873d42aacaf4`)
 2. Collections already created (see [CMS Schema Management](cms-schema-management.md))
 3. API access with CMS permissions
 
@@ -439,6 +439,7 @@ curl -X DELETE \
 | `WDE0007` | Bulk update: wrong ID field name | Use `id` not `_id` at element level |
 | `WDE0080` | Validation failed (multiple causes) | Bulk update: don't include `_id` in `data`; Bulk patch: use `patches` array not `dataItems` |
 | `WDE0303` | Can't set multi-reference field via data operations | Use reference endpoints: `insert-references`, `replace-references` |
+| `WDE0110` | Wix CMS (Wix Data) application is not installed | Install application with appDefId: `e593b0bd-b783-45b8-97c2-873d42aacaf4` |
 
 ---
 

package/skills/wix-manage/references/cms/cms-schema-management.md

@@ -10,7 +10,7 @@ This recipe covers managing the structure (schema) of Wix CMS collections using
 
 ## Prerequisites
 
-1. Wix CMS enabled on the site
+1. Wix CMS application installed on the site (appDefId: `e593b0bd-b783-45b8-97c2-873d42aacaf4`)
 2. API access with CMS permissions (Manage Data Collections scope)
 
 ## Required APIs

package/skills/wix-manage/references/stores/create-product-from-image.md

@@ -183,6 +183,30 @@ Examine the images for visible product attributes that should become variant opt
 - If multiple images show the **same product from different angles**, treat them as additional product media — NOT as separate variants.
 - If only one image is provided and a distinctive color is visible, suggest that single color as a choice and ask the user if the product comes in other colors.
 
+### 4h. Subscription Eligibility Detection (silent — no user interaction)
+
+Based on the product name, description, and image analysis, determine whether this product is **subscription-eligible**. A product qualifies if it is a consumable that gets depleted at a predictable rate — something customers buy repeatedly on a regular schedule.
+
+**Eligible categories (examples):**
+- Food & beverage: coffee beans/pods, tea, protein powder, meal kits
+- Supplements & health: vitamins, probiotics, protein supplements
+- Pet: pet food, flea/tick treatments, cat litter
+- Personal care: skincare routine products, razor blades/cartridges, deodorant, shampoo/conditioner
+- Household: cleaning supplies, paper towels, toilet paper, laundry detergent
+- Baby: diapers, formula, wipes
+- Media: print/digital newspapers, magazines
+- Candles (daily-use scented candles with high burn frequency)
+
+**NOT eligible (do not suggest):**
+- Furniture, art, décor (one-time purchase)
+- Electronics, tools, appliances
+- Standard clothing, apparel, shoes (not subscription-typical)
+- Jewelry, watches
+- Books (single title), games, toys
+- Any unique or collectible item
+
+Store the result internally as `subscription_eligible: true/false`. If `true`, also note a brief reason (e.g., `"coffee beans — daily consumable"`). No user interaction at this step.
+
 ---
 
 ## V3 STEP 4: Present Review Card to User (INTERACTIVE)
@@ -207,6 +231,7 @@ Present a structured review card using the markdown format below. This provides
 | Images | [count] uploaded |
 | SEO | [first 60 chars of meta description]… |
 | Tone | [Matched from existing site products / Neutral e-commerce] |
+| Subscription | [e.g. Monthly · 10% off] or [Not applicable] |
 
 **Info Sections**
 - **[Title 1]:** [one-line summary]
@@ -221,7 +246,7 @@ After the card, present the action options:
 
 > 1. **Refine** — tell me what to change (e.g., "make the description shorter", "the price should be lower")
 > 2. **Regenerate** — I'll start the analysis over, optionally with additional context from you
-> 3. **Approve** — proceed to options and product creation
+> 3. **Approve** — lock in these details and continue to the next steps
 
 If the user provided a text note that **contradicts** what's visible in the image (e.g., image shows blue but note says "available in red"), ask the user to clarify before proceeding.
 
@@ -229,6 +254,68 @@ If the user provided a text note that **contradicts** what's visible in the imag
 
 ---
 
+## V3 STEP 4.5: Suggest Subscription (INTERACTIVE, conditional)
+
+> **Run this step ONLY if `subscription_eligible: true` was set in V3 STEP 3 section 4h.** Otherwise skip directly to V3 STEP 5.
+
+Present a short, non-pushy suggestion card:
+
+---
+
+**This product looks like a great candidate for a subscription plan.**
+Customers who subscribe to *[product name]* get auto-refills on a schedule they choose — boosting repeat revenue for you.
+
+Would you like to add a subscription option?
+- **Yes** — set it up now (takes ~30 seconds)
+- **No** — create as a one-time purchase only
+
+---
+
+If the user says **No**, proceed directly to V3 STEP 5.
+
+If the user says **Yes**, ask the following 4 questions (can be presented together as a single form):
+
+**Q1 — Billing frequency**
+> "How often should subscribers be charged and receive this product?"
+
+| Choice | `frequency` | `interval` |
+|--------|------------|-----------|
+| Every week | `WEEK` | `1` |
+| Every 2 weeks | `WEEK` | `2` |
+| Every month *(Recommended)* | `MONTH` | `1` |
+| Every 2 months | `MONTH` | `2` |
+| Every 3 months | `MONTH` | `3` |
+| Every 6 months | `MONTH` | `6` |
+| Every year | `YEAR` | `1` |
+
+**Q2 — Duration**
+> "How long should the subscription run?"
+
+- **Ongoing** — renews automatically until the customer cancels (omit `billingCycles`)
+- **Fixed** — ends after N cycles (ask: "How many cycles?") → set `billingCycles: N`
+
+**Q3 — Subscriber discount (optional incentive)**
+> "Would you like to offer a discount to customers who subscribe?"
+
+- No discount (omit `discount` block)
+- **10% off** *(Recommended)* → `type: "PERCENTAGE", amount: 10`
+- Custom percentage → ask for value → `type: "PERCENTAGE", amount: [value]`
+- Fixed amount off → ask for value → `type: "AMOUNT", amount: [value]`
+
+**Q4 — Allow one-time purchase alongside subscription**
+> "Can customers also buy this product as a one-time purchase (without subscribing)?"
+
+- **Yes — sell both ways** *(Recommended)* → `allowOneTimePurchases: true`
+- No — subscription only → `allowOneTimePurchases: false`
+
+After collecting the user's answers, show a brief confirmation line before moving on:
+
+> Subscription plan configured: [e.g. Monthly · Ongoing · 10% off · One-time purchases also allowed]
+
+Store the collected subscription data for use in V3 STEP 6.
+
+---
+
 ## V3 STEP 5: Suggest Options and Ask User (INTERACTIVE)
 
 **Present the detected options from V3 STEP 4g and ask the user if they want to add product options.**
@@ -255,10 +342,74 @@ If no options were detected:
 
 ## V3 STEP 6: Create the Product
 
+Before making the API call, ask the user one final time:
+
+> Everything is ready. Shall I create the product now?
+> - **Yes, create it** — I'll submit the product to your store now.
+> - **No, go back** — return to a previous step to make changes.
+
+**Wait for confirmation.** Only proceed with the API call if the user says Yes.
+
+---
+
 **API Endpoint:** `POST https://www.wixapis.com/stores/v3/products`
 
 Build the request body with all confirmed fields. The write must be **atomic** — either all fields save or none do.
 
+**If a subscription was configured in V3 STEP 4.5**, include a `subscriptionDetails` block in the product body (see rules below). Otherwise omit it entirely.
+
+**`subscriptionDetails` rules:**
+- `title`: auto-generate from frequency (e.g. `"Monthly Subscription"`, `"Weekly Subscription"`, `"Quarterly Subscription"`)
+- `description`: if a discount was set, write a short sentence referencing it (e.g. `"Subscribe and save 10% on every order."`). Omit if no discount.
+- `visible`: always `true`
+- `frequency` + `interval`: from user's Q1 answer
+- `billingCycles`: include only for fixed-duration subscriptions (from Q2). Omit for ongoing.
+- `discount`: include only if a discount was chosen (from Q3). Omit the entire block if no discount.
+- `allowOneTimePurchases`: from user's Q4 answer
+
+**Example `subscriptionDetails` block (monthly, ongoing, 10% off, one-time also allowed):**
+
+```json
+"subscriptionDetails": {
+    "subscriptions": [
+        {
+            "title": "Monthly Subscription",
+            "description": "Subscribe and save 10% on every order.",
+            "visible": true,
+            "frequency": "MONTH",
+            "interval": 1,
+            "discount": {
+                "type": "PERCENTAGE",
+                "amount": 10
+            }
+        }
+    ],
+    "allowOneTimePurchases": true
+}
+```
+
+**Example with fixed duration and flat amount discount (every 2 months, 6 cycles, $5 off, subscription only):**
+
+```json
+"subscriptionDetails": {
+    "subscriptions": [
+        {
+            "title": "Bi-Monthly Subscription",
+            "description": "Subscribe and save $5 on every order.",
+            "visible": true,
+            "frequency": "MONTH",
+            "interval": 2,
+            "billingCycles": 6,
+            "discount": {
+                "type": "AMOUNT",
+                "amount": 5
+            }
+        }
+    ],
+    "allowOneTimePurchases": false
+}
+```
+
 ---
 
 ### Path A: Simple Product (No Options)
@@ -650,8 +801,9 @@ Before reporting success to the user, verify ALL of the following:
 - [ ] V3 STEP 2 completed: User provided 1-3 images, all uploaded to Media Manager with wixstatic.com URLs.
 - [ ] V3 STEP 3 completed: Images analyzed from user's message, all product fields generated based on what's visible in the image(s).
 - [ ] V3 STEP 4 completed: User reviewed and approved the generated details.
+- [ ] V3 STEP 4.5 completed (if applicable): Subscription eligibility was evaluated. If eligible, user was asked and their choice (Yes/No) was applied before proceeding to STEP 5.
 - [ ] V3 STEP 5 completed: User confirmed, modified, or skipped product options.
-- [ ] V3 STEP 6 completed: Product was created via API and you received a product ID.
+- [ ] V3 STEP 6 completed: User confirmed "create now", product was created via API and you received a product ID.
 
 ---
 

package/skills/wix-headless/references/astro/templates/bookings/ManageBooking.tsx

@@ -1,84 +0,0 @@
-import { useState } from "react";
-import { createClient, OAuthStrategy } from "@wix/sdk";
-import { bookings } from "@wix/bookings";
-import { WIX_CLIENT_ID } from "astro:env/client";
-
-// ManageBooking.tsx — client:only="react" island for /manage-booking.
-// The server (manage-booking.astro) already minted an anonymous action token
-// (app-elevated) and passed it in. The cancel call is a NO-AUTH anonymous method,
-// so the visitor client runs it directly with the token. Reschedule-in-place
-// needs a verified class V2Slot shape, so we offer cancel-and-rebook instead.
-
-interface Props {
-  token: string | null;
-  revision: string;
-  serviceName: string;
-  startDate: string | null;
-  status: string | null;
-  canCancel: boolean;
-  showSummary?: boolean; // false when embedded under a page that already shows the service/date
-}
-
-const wixClient = createClient({
-  modules: { bookings },
-  auth: OAuthStrategy({ clientId: WIX_CLIENT_ID }),
-});
-
-const fmt = (iso: string | null) => {
-  if (!iso) return null;
-  const d = new Date(iso);
-  return Number.isNaN(d.getTime())
-    ? null
-    : d.toLocaleString([], { weekday: "long", month: "long", day: "numeric", hour: "2-digit", minute: "2-digit" });
-};
-
-export default function ManageBooking({ token, revision, serviceName, startDate, status, canCancel, showSummary }: Props) {
-  const [state, setState] = useState<"idle" | "canceling" | "canceled" | "error">(
-    status === "CANCELED" ? "canceled" : "idle",
-  );
-  const when = fmt(startDate);
-
-  const handleCancel = async () => {
-    if (!token) return;
-    setState("canceling");
-    try {
-      await wixClient.bookings.bookingsCancelBookingAnonymously(token, revision);
-      setState("canceled");
-    } catch (err) {
-      console.error("[manage-booking] cancel failed:", err);
-      setState("error");
-    }
-  };
-
-  if (state === "canceled") {
-    return (
-      <div className="manage-booking">
-        <p className="manage-booking-status">
-          Your booking for <strong>{serviceName}</strong>{when ? <> on <strong>{when}</strong></> : null} is canceled.
-        </p>
-        <a href="/services" className="booking-submit" style={{ display: "inline-block" }}>Book another service</a>
-      </div>
-    );
-  }
-
-  return (
-    <div className="manage-booking">
-      {showSummary !== false && (
-        <p className="manage-booking-summary">
-          <strong>{serviceName}</strong>{when ? <> · {when}</> : null}
-        </p>
-      )}
-      {state === "error" && <p className="booking-error">Something went wrong canceling your booking. Please try again.</p>}
-      {canCancel ? (
-        <button type="button" className="booking-submit" onClick={handleCancel} disabled={state === "canceling"}>
-          {state === "canceling" ? "Canceling…" : "Cancel this booking"}
-        </button>
-      ) : (
-        <p className="manage-booking-note">This booking can no longer be canceled online.</p>
-      )}
-      <p className="manage-booking-note">
-        Need a different time? Cancel above, then <a href="/services" className="manage-booking-link">book another time</a>.
-      </p>
-    </div>
-  );
-}

package/skills/wix-headless/references/astro/templates/bookings/api/confirm-booking.ts

@@ -1,34 +0,0 @@
-import type { APIRoute } from "astro";
-import { auth } from "@wix/essentials";
-import { bookings } from "@wix/bookings";
-
-// POST /api/confirm-booking { bookingId, revision }
-//
-// createBooking() leaves the booking CREATED — which does NOT occupy a seat, so
-// the class/appointment stays bookable and OVERBOOKS (remainingCapacity never
-// drops). confirmBooking() promotes it to CONFIRMED (holds the seat); with
-// flowControlSettings.checkAvailabilityValidation it REJECTS the confirm if the
-// session filled up since the slot was picked — the real overbooking guard.
-// confirmBooking requires Manage Bookings, so elevate (app identity) here;
-// confirmBooking is a real SDK method, so auth.elevate(...) works directly.
-
-const json = (ok: boolean, status: number, extra: Record<string, unknown> = {}) =>
-  new Response(JSON.stringify({ ok, ...extra }), { status, headers: { "Content-Type": "application/json" } });
-
-export const POST: APIRoute = async ({ request }) => {
-  let body: any;
-  try { body = await request.json(); } catch { return json(false, 400, { error: "Invalid request body." }); }
-  const { bookingId, revision } = body ?? {};
-  if (!bookingId || !revision) return json(false, 400, { error: "Missing bookingId or revision." });
-
-  try {
-    const res = await auth.elevate(bookings.confirmBooking)(bookingId, String(revision), {
-      paymentStatus: "NOT_PAID", // pay-on-site reservation
-      flowControlSettings: { checkAvailabilityValidation: true },
-    });
-    return json(true, 200, { status: res.booking?.status });
-  } catch (err) {
-    console.error("[api/confirm-booking] failed:", err);
-    return json(false, 409, { error: "unavailable" }); // most likely: session just filled up
-  }
-};

package/skills/wix-headless/references/astro/templates/bookings/api/waitlist.ts

@@ -1,74 +0,0 @@
-import type { APIRoute } from "astro";
-import { auth, httpClient } from "@wix/essentials";
-
-// POST /api/waitlist { sessionId, totalParticipants, contactDetails:{firstName,lastName,email,phone} }
-//
-// Native Wix Bookings waitlist. There is NO v2/v3 waitlist API — createBooking
-// can't waitlist; the only join is the legacy v1 Register To Waitlist
-// (POST /bookings/v1/waitlist/register), which needs Manage Bookings + a Wix
-// contactId. So this runs server-side, elevated to app identity. CLASS only.
-//
-// `sessionId` is the v1-encoded session id (the `waitingResource`); the browser
-// gets it from the SESSION_CAPACITY_EXCEEDED error createBooking returns for a
-// full session ("…on session <id>").
-//
-// IMPORTANT: auth.elevate() only grants permissions for a real SDK function. The
-// waitlist + Contacts calls are raw REST (no SDK wrapper), so elevate the
-// authenticated fetch ITSELF — NOT a closure that calls it (a closure runs
-// un-elevated/visitor and 403s).
-
-const json = (ok: boolean, status: number, extra: Record<string, unknown> = {}) =>
-  new Response(JSON.stringify({ ok, ...extra }), { status, headers: { "Content-Type": "application/json" } });
-
-export const POST: APIRoute = async ({ request }) => {
-  let body: any;
-  try { body = await request.json(); } catch { return json(false, 400, { error: "Invalid request body." }); }
-  const { sessionId, totalParticipants = 1, contactDetails } = body ?? {};
-  const email: string | undefined = contactDetails?.email;
-  if (!sessionId || !email) return json(false, 400, { error: "Missing sessionId or email." });
-
-  const ef = auth.elevate(httpClient.fetchWithAuth as typeof fetch) as typeof fetch;
-  const api = (url: string, payload: unknown) =>
-    ef(url, { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify(payload) });
-
-  try {
-    // 1. Resolve a contactId (reuse by email; create if absent).
-    let contactId: string | undefined;
-    const q = await api("https://www.wixapis.com/contacts/v4/contacts/query", {
-      query: { filter: { "info.emails.email": email } },
-    });
-    contactId = ((await q.json().catch(() => ({}))) as any).contacts?.[0]?.id;
-    if (!contactId) {
-      const c = await api("https://www.wixapis.com/contacts/v4/contacts", {
-        info: {
-          name: { first: contactDetails.firstName, last: contactDetails.lastName || undefined },
-          emails: { items: [{ email, primary: true }] },
-          ...(contactDetails.phone ? { phones: { items: [{ phone: contactDetails.phone, primary: true }] } } : {}),
-        },
-      });
-      contactId = ((await c.json().catch(() => ({}))) as any).contact?.id;
-    }
-    if (!contactId) throw new Error("could not resolve contactId");
-
-    // 2. Register on the native waitlist.
-    const reg = await api("https://www.wixapis.com/bookings/v1/waitlist/register", {
-      waitingResource: sessionId,
-      formInfo: {
-        paymentSelection: [{ rateLabel: "general", numberOfParticipants: totalParticipants }],
-        contactDetails: {
-          contactId,
-          firstName: contactDetails.firstName,
-          lastName: contactDetails.lastName || undefined,
-          email,
-          phone: contactDetails.phone || undefined,
-        },
-      },
-    });
-    const rj: any = await reg.json().catch(() => ({}));
-    if (!reg.ok || !rj.registrationId) throw new Error(`register ${reg.status}: ${JSON.stringify(rj).slice(0, 200)}`);
-    return json(true, 200, { registrationId: rj.registrationId });
-  } catch (err) {
-    console.error("[api/waitlist] failed:", err);
-    return json(false, 502, { error: "Waitlist registration failed." });
-  }
-};