@wix/agent-skills 1.18.2 → 1.19.1

package/skills/wix-manage/references/bookings/bookings-staff-setup.md

@@ -68,7 +68,8 @@ The most common mistake is confusing which ID to use in which API call, leading
 
 * **Two-Step Requirement**: Custom working hours requires both `assignWorkingHoursSchedule` AND creating `WORKING_HOURS` events. Only doing the first step results in staff with no actual working hours.
 * **Foundation Dependencies**: Staff operations require Wix Bookings app installation and proper business schedule configuration. "Business schedule not found" errors indicate missing foundation setup.
-* **Event Field Requirements**: When creating `WORKING_HOURS` events, several fields that appear optional in documentation are actually required: `externalScheduleId`, `adjustedStart`, `adjustedEnd`, `resources` array, and `appId`.
+* **Bulk Request Envelope**: `bulkCreateEvents` requires each event to be wrapped in an `event` object — `{"events": [{"event": {...}}], "returnEntity": true}`. Sending a flat `{"events": [{...}]}` fails with 400 `event must not be empty`. Pass `returnEntity: true` to get the created events back; otherwise the response contains only `itemMetadata`.
+* **Minimal Event Fields**: A `WORKING_HOURS` event needs only `type`, `scheduleId`, `start.localDate`, `end.localDate`, and (for recurring hours) `recurrenceRule`. The server derives `externalScheduleId` (set to the staff member's resource ID automatically), `adjustedStart`/`adjustedEnd`, and `appId`; `resources` may stay empty on a working-hours schedule.
 * **Revision Numbers**: Event updates ALWAYS require the current revision number. Fetch current event details before any update operation.
 * **Time Format Precision**: All date/time fields must use precise ISO 8601 format (`YYYY-MM-DDTHH:mm:ss`) without timezone indicators.
 * **Separate Events for Each Day**: Each working day requires a separate event with single-day recurrence rules. You cannot specify multiple days in one event's `recurrenceRule.days` array.
@@ -113,9 +114,7 @@ Before creating staff members, ensure the foundation is properly configured:
 
 **Install Wix Bookings App** (if needed): Use the App Installer API with Wix Bookings app ID: `13d21c63-b5ec-5912-8397-c3a5ddb27a97`.
 
-**Configure Business Schedule**: Set up site properties with business operating hours using the Site Properties API.
-
-**Create Calendar Schedule and Working Hours**: Create a calendar schedule for Wix Bookings integration and populate it with business `WORKING_HOURS` events.
+**Configure Business Schedule**: Default business hours live as `WORKING_HOURS` calendar events on the business schedule — set them up per the [Configure Default Business Hours](../calendar/configure-default-business-hours.md) recipe. Do **not** use the Site Properties API for this: its business-schedule fields are separate general site info and do not drive Bookings availability.
 
 ### 2. Verify Current Business Hours (CRITICAL)
 
@@ -156,11 +155,10 @@ Create staff members using the Staff API (`POST https://www.wixapis.com/bookings
 
 **⚠️ INHERITANCE MOMENT**: The moment this API call completes, the staff member inherits the current business hours. There's no "undo" for this inheritance.
 
-**Save Critical IDs from Response**:
-- `staffMember.id` for updates and schedule assignment
-- `staffMember.resourceId` for services and event resources
-- `staffMember.resource.eventsSchedule.id` for working hours events
-- `staffMember.resource.usesDefaultWorkingHours` (should be `true` initially)
+**Save Critical IDs**:
+- `staffMember.id` (in the create response) for updates and schedule assignment
+- `staffMember.resourceId` (in the create response) for services and event resources
+- `staffMember.resource.eventsSchedule.id` for working hours events — **NOT in the create response**. The create response contains only id/name/resourceId; fetch the staff member again with `?fields=RESOURCE_DETAILS` to get `resource.eventsSchedule.id` (and `resource.usesDefaultWorkingHours`, initially `true`). Reading `resource.eventsSchedule.id` off the create response yields `undefined` and downstream `scheduleId must not be empty` errors.
 
 ### 5. Set Up Custom Working Hours (Two-Step Process)
 
@@ -168,21 +166,44 @@ Create staff members using the Staff API (`POST https://www.wixapis.com/bookings
 
 **Step 5A: Assign Custom Working Hours Schedule**
 
-Get staff member details (`GET https://www.wixapis.com/bookings/v1/staff-members/<STAFF_MEMBER_ID>?fields=RESOURCE_DETAILS`) to extract the events schedule ID. Call `assignWorkingHoursSchedule` (`POST https://www.wixapis.com/bookings/v1/staff-members/<STAFF_MEMBER_ID>/assign-working-hours-schedule`) using the staff member ID and their events schedule ID. This detaches the staff member from business default hours.
+Get staff member details (`GET https://www.wixapis.com/bookings/v1/staff-members/<STAFF_MEMBER_ID>?fields=RESOURCE_DETAILS`) to extract the events schedule ID. Then call `assignWorkingHoursSchedule` (`POST https://www.wixapis.com/bookings/v1/staff-members/<STAFF_MEMBER_ID>/assign-working-hours-schedule`):
+
+```json
+{ "scheduleId": "<EVENTS_SCHEDULE_ID>" }
+```
+
+The request field is `scheduleId` (other names, e.g. `eventsScheduleId`, fail with 400 `scheduleId must not be empty`). This detaches the staff member from business default hours.
 
 Verify the response shows `"usesDefaultWorkingHours": false`.
 
+> **On failure, resume — don't restart.** If this call (or a later step) fails, the staff member from Step 4 already exists. Fix the failing call and continue with the same staff member ID; re-running the whole flow creates a duplicate staff member.
+
 **Step 5B: Create WORKING_HOURS Events**
 
-Use the Events API (`POST https://www.wixapis.com/calendar/v3/bulk/events/create`) to create working hours events for each working day. Each event must include:
-- `scheduleId`: Staff member's events schedule ID
-- `externalScheduleId`: Staff member's resource ID
-- `type`: `"WORKING_HOURS"`
-- `resources` array: Staff member's resource ID
-- `appId`: Wix Bookings app ID
-- Proper recurrence rules with single-day specification
+Use the Events API (`POST https://www.wixapis.com/calendar/v3/bulk/events/create`) to create one recurring event per working day. Note the request envelope: each event is wrapped in an `event` object.
 
-Create separate events for each day of the week the staff member works.
+```json
+{
+  "events": [
+    {
+      "event": {
+        "type": "WORKING_HOURS",
+        "scheduleId": "<STAFF_EVENTS_SCHEDULE_ID>",
+        "start": { "localDate": "2026-09-07T09:00:00" },
+        "end": { "localDate": "2026-09-07T15:00:00" },
+        "recurrenceRule": { "frequency": "WEEKLY", "interval": 1, "days": ["MONDAY"] }
+      }
+    }
+  ],
+  "returnEntity": true
+}
+```
+
+- `scheduleId` is the staff member's **events schedule ID** (`resource.eventsSchedule.id`).
+- `externalScheduleId`, `adjustedStart`/`adjustedEnd`, and `appId` are derived by the server — you do not need to send them (`externalScheduleId` comes back set to the staff member's resource ID).
+- `recurrenceRule.frequency` must be `WEEKLY` (the only supported value); `interval` is 1–4.
+- `recurrenceRule.days` takes exactly one **full uppercase** day name from `MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY` — abbreviations like `MON` fail validation. One day per event, so create a separate event for each working day.
+- `start`/`end` must be today or in the future for recurring events.
 
 ### 6. Verify Setup
 
@@ -193,10 +214,9 @@ Query the staff member to confirm:
 
 ### IMPORTANT NOTES
 
-* **ID Relationship Critical**: Use staff member ID for assignment, events schedule ID for event `scheduleId`, and resource ID for `externalScheduleId` and `resources` array
+* **ID Relationship Critical**: Use the staff member ID for assignment and the events schedule ID for event `scheduleId`; the resource ID appears in server-derived fields (`externalScheduleId`) and in `resources` arrays when attaching this staff member to CLASS/COURSE session events
 * **Foundation First**: Complete foundation setup before staff operations to avoid "Business schedule not found" errors
 * **Complete Two-Step Process**: Both schedule assignment AND event creation are mandatory for custom working hours
-* **Event Field Requirements**: Include all required fields even if they appear optional in basic documentation
 * **Revision Management**: Always fetch current revision numbers before updating events
 * **Date Format Strict**: Use precise ISO 8601 format without timezone indicators
 * **Inheritance is Permanent**: Once inherited, business hours changes don't affect existing staff
@@ -218,7 +238,10 @@ Completed assignment but missing event creation. Create `WORKING_HOURS` events u
 - **Solution**: Standardize by configuring custom hours for all staff, or recreate staff after fixing business hours
 
 **"Invalid scheduleId" or "Resource not found" Errors**:
-Using wrong ID type in API calls. Verify you're using events schedule ID for `scheduleId`, resource ID for `externalScheduleId` and `resources` array, and staff member ID for updates.
+Using wrong ID type in API calls. Verify you're using the events schedule ID for `scheduleId` and the staff member ID for updates.
+
+**400 "event must not be empty" on bulkCreateEvents**:
+The request body is missing the per-event wrapper. Each entry in `events` must be `{"event": {...}}`, not the event fields directly.
 
 **Event Update Fails with Revision Error**:
 Get current event details first and include the revision number in update requests.
@@ -227,7 +250,7 @@ Get current event details first and include the revision number in update reques
 Use current or future dates for recurring event start dates.
 
 **Events Not Linked to Staff Member**:
-Ensure `resources` array contains staff member's resource ID and `externalScheduleId` is properly set.
+Verify the event was created on the staff member's own events schedule (`resource.eventsSchedule.id`) — the schedule is what links working-hours events to the staff member. The returned event's `externalScheduleId` should equal the staff member's resource ID (server-derived).
 
 ### Working with Existing Staff
 

package/skills/wix-manage/references/bookings/multi-resource-service-creation.md

@@ -18,8 +18,9 @@ Below are the recommended steps to successfully create Wix Bookings services tha
 Before creating multi-resource services, ensure the following requirements are met:
 
 1. **Wix Bookings** - Core app must be installed and configured
-2. **Premium Plan** - Advanced resource management typically requires premium features
-3. **Business Location** - At least one business location must be configured
+2. **Business Location** - At least one business location must be configured
+
+> Resource type, resource, and resource-bound service creation succeed via the API without any premium-related error. If a plan-gating error does occur, it surfaces explicitly (e.g. a 403) — don't preemptively block on plan checks.
 
 ### App Installation Process
 
@@ -112,6 +113,12 @@ Before creating anything, plan your resource type structure. Each type should re
 
 Create resource types using `createResourceType` API (`POST https://www.wixapis.com/bookings/v2/resources/resource-types`) ([REST](https://dev.wix.com/docs/api-reference/business-solutions/bookings/resources/resource-types-v2/create-resource-type)):
 
+```json
+{ "resourceType": { "name": "Treatment Room" } }
+```
+
+The response returns `resourceType.id` — save it for resource creation and the service's `serviceResources`.
+
 **Key Requirements:**
 - `name` must be unique across the site
 - Keep `name` descriptive but concise (appears in booking interface)
@@ -121,9 +128,23 @@ Create resource types using `createResourceType` API (`POST https://www.wixapis.
 
 ### 3. Create Individual Resources
 
-For each resource type, create the individual resource instances using `createResource` API (`POST https://www.wixapis.com/bookings/v2/resources`) ([REST](https://dev.wix.com/docs/api-reference/business-solutions/bookings/resources/resources-v2/create-resource)):
+Create the resource instances of each type. For more than one (the usual case — e.g. Room A and Room B), use `bulkCreateResources` (`POST https://www.wixapis.com/bookings/v2/bulk/resources/create`) ([REST](https://dev.wix.com/docs/api-reference/business-solutions/bookings/resources/resources-v2/bulk-create-resources)); for a single one, `createResource` (`POST https://www.wixapis.com/bookings/v2/resources`) takes `{ "resource": { "name": ..., "typeId": ... } }`.
+
+```json
+{
+  "resources": [
+    { "name": "Room A", "typeId": "<RESOURCE_TYPE_ID>" },
+    { "name": "Room B", "typeId": "<RESOURCE_TYPE_ID>" }
+  ],
+  "returnEntity": true
+}
+```
+
+Read each created resource's ID from `results[i].item.id` (with `returnEntity: true`) or `results[i].itemMetadata.id` (without it). **The resource is directly under `item` — there is no `item.resource.id`** (reading it throws `Cannot read properties of undefined`). Match items to your request by `itemMetadata.originalIndex`, and check `bulkActionMetadata.totalFailures` before proceeding.
 
-**Gap Not in Docs**: The docs don't clearly explain that `availableInAllLocations: true` is the simplest approach and that specific location configuration is complex and often unnecessary.
+**⚠️ Payload shape**: the type reference is the flat `typeId` field (same on single and bulk). Sending a nested object (`"type": {"id": ...}`) fails with 400 `Unexpected value for StringValue`. A resource without `typeId` is created but is not bookable.
+
+If you omit `locationOptions`, the resource defaults to `availableInAllLocations: true` — the simplest and usually correct configuration; specific location setup is complex and often unnecessary.
 
 **Advanced Configuration (Gap):**
 - Custom working hours override business location hours (this behavior isn't clearly documented)
@@ -133,17 +154,42 @@ For each resource type, create the individual resource instances using `createRe
 
 ### 4. Create Multi-Resource Service (Optional Connection)
 
-Create the service that optionally connects to multiple resource types using `bulkCreateServices` API ([REST](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/bulk-create-services)):
+Create the service that optionally connects to multiple resource types using `bulkCreateServices` API (`POST https://www.wixapis.com/bookings/v2/bulk/services/create`) ([REST](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/bulk-create-services)). Note the endpoint path is `/bulk/services/create` (not `/services/bulk/create`, which 404s).
+
+**Pick the service type, and mind the resource-specific required fields:**
+
+- A **1-on-1, time-slot** service (e.g. a massage, a room rental by the hour) is an `APPOINTMENT`. When such a service is driven by a **resource instead of a staff member**, `primaryResourceType` (a flat resource-type GUID) is **required** — omitting it fails with 400 `primary_resource_type is required for appointment services without staff members`. APPOINTMENT also needs `schedule.availabilityConstraints.sessionDurations`.
+- A **group** service (fixed capacity per session) is a `CLASS` (drop-in) or `COURSE` (whole series); these use `defaultCapacity` and do not require `primaryResourceType`.
+
+Appointment example (one room per booking, no staff):
 
-**Service Resource Configuration:**
 ```json
-"serviceResources": [
-  {"resourceType": {"id": "room-type-id"}},
-  {"resourceType": {"id": "equipment-type-id"}},
-  {"resourceType": {"id": "instructor-type-id"}}
-]
+{
+  "services": [{
+    "name": "Massage",
+    "type": "APPOINTMENT",
+    "onlineBooking": { "enabled": true },
+    "serviceResources": [
+      { "resourceType": { "id": "<ROOM_TYPE_ID>" } }
+    ],
+    "primaryResourceType": "<ROOM_TYPE_ID>",
+    "schedule": { "availabilityConstraints": { "sessionDurations": [60] } },
+    "payment": {
+      "rateType": "FIXED",
+      "options": { "online": true, "inPerson": false },
+      "fixed": { "price": { "value": "80" } }
+    }
+  }],
+  "returnEntity": true
+}
 ```
 
+For a group service, use `"type": "CLASS"` with `"defaultCapacity": <n>` instead of `primaryResourceType`/`sessionDurations`. Both types take `payment.options` (at least one of `online`/`inPerson` true) — required even for the resource-bound case.
+
+Save the service ID from the response: `results[0].item.id` (with `returnEntity: true`), or `results[0].itemMetadata.id` (without it). **There is no `results[0].item.service.id`** — reading that path throws `Cannot read properties of undefined`.
+
+**⚠️ Verify from the response, not from assumptions**: without `returnEntity: true` the bulk response contains only `results[0].itemMetadata` (id + success flag) — there is no `item`. With the flag, the created service is at `results[0].item` (e.g. `item.id`, `item.serviceResources`). Check `bulkActionMetadata.totalFailures` and each `itemMetadata.success` before reporting the service as created.
+
 **Key Principle**: This creates a **loose connection** where the service requests resource allocation during booking, but resources remain independent entities with their own lifecycle and management.
 
 **Pricing Strategy**: Multi-resource services typically command premium pricing due to coordination complexity.
@@ -171,6 +217,18 @@ The docs don't explain how multi-resource allocation actually works during booki
 - Check that `typeId` exactly matches the resource type `id`
 - Ensure you're not using resource type `name` when `id` is required
 
+**400 "Unexpected value for StringValue" on createResource or on service `primaryResourceType`:**
+- A resource-type reference was sent as a nested object where a flat GUID string is expected. `createResource` uses `"typeId": "<guid>"`; the service field is `"primaryResourceType": "<guid>"` (both flat, not `{"id": ...}`). Note this differs from `serviceResources[].resourceType.id`, which *is* nested.
+
+**400 "primary_resource_type is required for appointment services without staff members":**
+- An `APPOINTMENT` service bound to a resource (no `staffMemberIds`) needs `primaryResourceType` set to the driving resource-type GUID. Either add it, or model the service as a `CLASS`/`COURSE` if a group service fits.
+
+**404 on bulk creation:**
+- The path segments are `bulk/<entity>/create`: `POST /bookings/v2/bulk/services/create`, `POST /bookings/v2/bulk/resources/create`. `/bookings/v2/services/bulk/create` (and the resources equivalent) do not exist.
+
+**`Cannot read properties of undefined` after a bulk create (resources or services):**
+- Every bulk response nests the entity directly under `results[i].item` — use `item.id`, never `item.resource.id` or `item.service.id`. Without `returnEntity: true` there is no `item` at all, only `itemMetadata.id`.
+
 **"Resource type name already exists" Error (409):**
 - Resource type names must be unique across the site
 - Query existing resource types to avoid duplicates
@@ -211,7 +269,7 @@ The docs don't explain how multi-resource allocation actually works during booki
 - Consider how names appear in booking confirmations and staff interfaces
 
 **Availability Strategy:**
-- Default to 24/7 availability unless business rules require restrictions
+- Don't add `workingHoursSchedules` to non-staff resources unless business rules require it — without them the resource simply follows business location hours, which is usually what you want
 - Use working hours sparingly - they add complexity without always adding value
 - Test availability scenarios thoroughly before going live
 

package/skills/wix-manage/references/calendar/configure-default-business-hours.md

@@ -26,7 +26,7 @@ Wix Bookings default business hours define the base availability for your bookin
 
 ### 🚨 CRITICAL: Default Hours Upon Installation
 
-**IMPORTANT**: When Wix Bookings is first installed on a site, it automatically creates DEFAULT business hours (typically 9 AM - 5 PM, Monday through Friday). You CANNOT simply create new hours without handling these existing default hours first.
+**IMPORTANT**: When Wix Bookings is first installed on a site, it automatically creates DEFAULT business hours — one recurring event per default working day. The exact days and times vary by site and template: a bare install creates Monday–Friday 10 AM–6 PM (per [About Business Schedules](https://dev.wix.com/docs/api-reference/business-management/calendar/about-business-schedules)), but template-created sites can differ (e.g. include Saturday). You CANNOT simply create new hours without handling these existing default hours first.
 
 **You MUST either:**
 1. **Update the existing default hours** to your desired schedule, OR
@@ -49,9 +49,9 @@ Wix Bookings default business hours define the base availability for your bookin
 
 ### Key Discovery: Universal Business Schedule External ID
 
-**VERIFIED**: The business schedule external ID `"4e0579a5-491e-4e70-a872-d097eed6e520"` is **universal across all Wix sites**.
+**VERIFIED**: The business schedule external ID `"4e0579a5-491e-4e70-a872-d097eed6e520"` is **universal across all Wix sites** — documented in [About Business Schedules](https://dev.wix.com/docs/api-reference/business-management/calendar/about-business-schedules) ("The business schedule always uses the `externalId` value `4e0579a5-491e-4e70-a872-d097eed6e520`").
 
-This has been tested and confirmed on multiple different Wix sites:
+This has also been tested and confirmed on multiple different Wix sites:
 - All sites have a business schedule with this exact external ID
 - The schedule name is consistently `"business"`
 - While the internal schedule `id` varies per site, the `externalId` is constant
@@ -63,7 +63,8 @@ This has been tested and confirmed on multiple different Wix sites:
 * **Default Hours Always Exist**: Every Wix Bookings installation creates default hours automatically
 * **Event Scheduling Flexibility**: Businesses can create multiple time slots per day or complex schedules as needed - there are no restrictions on number of events per day
 * **MASTER vs INSTANCE Events**: Based on observed behavior, MASTER events appear to generate INSTANCE events automatically, but always verify current event state when working with recurring events
-* **Query Patterns**: Use `"recurrenceType": ["MASTER"]` to focus on the primary recurring event definitions
+* **Query Patterns**: Use `"recurrenceType": ["MASTER"]` to focus on the primary recurring event definitions. ⚠️ It is a **top-level** request field, a sibling of `query` — placing it inside `query.filter` is **silently ignored** (the call succeeds and returns INSTANCE events), so a wrong placement produces confusing results rather than an error
+* **The universal external ID is a lookup key, not a schedule ID**: use `4e0579a5-491e-4e70-a872-d097eed6e520` only in the `externalId` filter of `querySchedules`. Passing it as an event's `scheduleId` fails with 404 `Schedule with 4e0579a5-... ID not found` (and as a `resources[].id`, with a similar `Resource ... not found`) — events take the schedule's real `id` returned by that query
 * **Revision Numbers**: Calendar events require current revision numbers for updates - always get fresh revision before bulk operations
 
 ---
@@ -104,7 +105,27 @@ Query pattern:
 
 **Important**: Always query for MASTER events specifically to see actual recurring schedules.
 
-**Expected Result**: You will typically find 5 existing MASTER events (Monday through Friday, 9 AM - 5 PM) from the default Bookings installation.
+**Expected Result**: One MASTER event per default working day. Don't assume which days: a bare Bookings install has Monday–Friday, but template-created sites can carry a different set (e.g. Monday–Saturday), and times vary by site — this query is what tells you what's actually there. The response fields this flow reads (trimmed — real responses carry more):
+
+```json
+{
+  "events": [
+    {
+      "id": "9f1e2d3c4b5a69788766554433221100aabbccddeeff00112233445566778899",
+      "scheduleId": "f3b9c2d1-7a4e-4b8c-9d2f-6e1a5c8b0d47",
+      "type": "WORKING_HOURS",
+      "recurrenceType": "MASTER",
+      "recurrenceRule": { "frequency": "WEEKLY", "interval": 1, "days": ["MONDAY"] },
+      "start": { "localDate": "2026-08-31T10:00:00", "timeZone": "America/New_York" },
+      "end": { "localDate": "2026-08-31T18:00:00", "timeZone": "America/New_York" },
+      "revision": "1"
+    }
+  ]
+}
+```
+
+- Update and cancel calls target `events[].id`; updates also need that event's current `revision`.
+- `recurrenceRule.days` tells you which weekday each event covers; `start`/`end` `localDate` carry the current hours in the schedule's `timeZone`.
 
 ### 3. Choose Your Strategy: Update OR Replace
 
@@ -127,14 +148,14 @@ Update fields:
 - `revision`: Current revision number (from Step 2 query)
 - `fieldmask`: `"start,end"`
 
-**Example**: Change Monday hours from 9 AM-5 PM to 12 AM-4 PM:
+**Example**: Change Monday hours to 8 AM-4 PM (use a Monday that is today or in the future — a past `start` is rejected for recurring events):
 ```json
 {
   "events": [{
     "event": {
       "id": "existing-monday-event-id",
-      "start": {"localDate": "2025-06-16T00:00:00"},
-      "end": {"localDate": "2025-06-16T16:00:00"},
+      "start": {"localDate": "2027-03-01T08:00:00"},
+      "end": {"localDate": "2027-03-01T16:00:00"},
       "revision": "current-revision-number"
     }
   }],
@@ -145,6 +166,9 @@ Update fields:
 ### 4B. Replace All Business Hours (Strategy B)
 
 #### Step 4B.1: Delete Existing Hours
+
+Cancelling is irreversible — a cancelled event can only be replaced by creating a new one. When the user names their complete desired schedule (e.g. "Monday through Friday, 8-4"), replacing all existing hours — including days outside that set — is part of the request. If it's ambiguous whether hours on other days should be kept, ask the user instead of assuming.
+
 Cancel existing MASTER events using `bulkCancelEvents` API (`POST https://www.wixapis.com/calendar/v3/bulk/events/cancel`) ([REST](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/bulk-cancel-event)):
 
 ```json
@@ -154,17 +178,28 @@ Cancel existing MASTER events using `bulkCancelEvents` API (`POST https://www.wi
 ```
 
 #### Step 4B.2: Create New Business Hours
-Create `WORKING_HOURS` events for each day using `bulkCreateEvents` API (`POST https://www.wixapis.com/calendar/v3/bulk/events/create`) ([REST](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/bulk-create-event)).
+Create `WORKING_HOURS` events for each day using `bulkCreateEvents` API (`POST https://www.wixapis.com/calendar/v3/bulk/events/create`) ([REST](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/bulk-create-event)). Note the request envelope: each event is wrapped in an `event` object — a flat event fails with 400 `event must not be empty`.
 
-**Each event pattern**:
-- `type`: `"WORKING_HOURS"`
-- `scheduleId`: Business schedule ID from step 1
-- `scheduleOwnerId`: `"4e0579a5-491e-4e70-a872-d097eed6e520"`
-- `externalScheduleId`: `"4e0579a5-491e-4e70-a872-d097eed6e520"`
-- `recurrenceRule`: Weekly recurring with single day
-- `start`/`end`: Business hours times
+```json
+{
+  "events": [
+    {
+      "event": {
+        "type": "WORKING_HOURS",
+        "scheduleId": "<BUSINESS_SCHEDULE_ID_FROM_STEP_1>",
+        "start": { "localDate": "2027-03-01T08:00:00" },
+        "end": { "localDate": "2027-03-01T16:00:00" },
+        "recurrenceRule": { "frequency": "WEEKLY", "interval": 1, "days": ["MONDAY"] }
+      }
+    }
+  ]
+}
+```
 
-**Note**: Create separate events for each day of the week (Monday, Tuesday, etc.).
+- `scheduleId` is the business schedule's real `id` from Step 1 — **not** the universal external ID (that constant is only the `querySchedules` lookup key; used here it 404s).
+- `scheduleOwnerId`/`externalScheduleId` are derived by the server; you do not need to send them.
+- `recurrenceRule.days` takes exactly one full uppercase day name (`MONDAY`…`SUNDAY`); create a separate event per weekday, with `start`/`end` today or in the future.
+- Check each `results[i].itemMetadata.success` (and `bulkActionMetadata.totalFailures`) before reporting the hours as set.
 
 ### 5. Verify Final Configuration
 
@@ -218,6 +253,7 @@ Query the business schedule events again to confirm:
 
 ## API Documentation References
 
+* [About Business Schedules](https://dev.wix.com/docs/api-reference/business-management/calendar/about-business-schedules)
 * [Query Schedules](https://dev.wix.com/docs/api-reference/business-management/calendar/schedules-v3/query-schedules)
 * [Query Events](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/query-events)
 * [Bulk Create Events](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/bulk-create-event)

package/skills/wix-manage/references/google-ads/billing-and-payment.md

@@ -1,12 +1,12 @@
 ---
 name: "Retrieve Google Ads Billing and Payment Details"
-description: "Retrieves billing and payment details for a Wix site's Google Ads account: the current billing period's ad spend (usage), the Wix service fee, the total charge, any promotional coupon adjustment, the billing period dates, and the account's credit balance (positive = available credits, negative = outstanding debt not yet charged). Also explains reading current vs remaining budget from the account object. Use when the user asks 'how much have I spent on Google Ads', 'what's my next Google Ads charge', 'show my ad billing', 'do I have ad credits left', 'why was I charged', or 'upcoming Google Ads payment'. Requires an existing Google Ads account. REST base https://www.wixapis.com/google-ads/v1."
+description: "Retrieves billing and payment details for a Wix site's Google Ads account: the current billing period's ad spend (usage), the Wix service fee, the total charge, any promotional coupon adjustment, the billing period dates, and the account's credit balance (positive = available credits, negative = outstanding debt not yet charged). Also explains reading current vs remaining budget from the account object. Use when the user asks 'how much have I spent on Google Ads', 'what's my next Google Ads charge', 'show my ad billing', 'do I have ad credits left', 'why was I charged', or 'upcoming Google Ads payment'. Requires an existing Google Ads account. REST base https://www.wixapis.com/_serverless/pa-google/v1."
 ---
 # RECIPE: Retrieve Google Ads Billing and Payment Details
 
 Report what a site owner will be charged for Google Ads: ad spend, the Wix service fee, coupon adjustments, the total, the billing period, and the account's credit balance.
 
-Base URL: `https://www.wixapis.com/google-ads/v1`. `<AUTH>` is the `Authorization` header. This endpoint is read-only.
+Base URL: `https://www.wixapis.com/_serverless/pa-google/v1`. `<AUTH>` is the `Authorization` header. This endpoint is read-only.
 
 **Prerequisite:** a Google Ads account must exist (`ACCOUNT_NOT_FOUND` → run [install-and-create-account](install-and-create-account.md)).
 
@@ -17,7 +17,7 @@ Base URL: `https://www.wixapis.com/google-ads/v1`. `<AUTH>` is the `Authorizatio
 Billing is calculated from cached subscription data (not fetched live from Google), and the charge calculation is heavy — this endpoint has a **30-second SLA**, so allow time and don't retry prematurely.
 
 ```bash
-curl -X GET 'https://www.wixapis.com/google-ads/v1/payment-details' -H 'Authorization: <AUTH>'
+curl -X GET 'https://www.wixapis.com/_serverless/pa-google/v1/payment-details' -H 'Authorization: <AUTH>'
 ```
 
 ```json

package/skills/wix-manage/references/google-ads/create-performance-max-campaign.md

@@ -1,6 +1,6 @@
 ---
 name: "Create and Launch a Performance Max Campaign"
-description: "Creates and launches a Google Ads Performance Max (PMAX) campaign for a Wix site — a goal-based campaign that runs across all Google channels (Search, Display, YouTube, Gmail, Discover, Maps) from an asset group of headlines, descriptions, images, and (for PMAX Leads) search-theme signals. Covers generating AI text and image assets, generating search themes, getting a Google budget recommendation, assembling the asset group with the required minimum assets, choosing PERFORMANCE_MAX vs PERFORMANCE_MAX_LEADS (leads: phone/form goals, negative keywords, 28-day learning) vs retail/Shopping (Merchant Center feed), creating in PAUSED, and launching. Use for 'create a Performance Max campaign', 'PMAX', 'run ads across all of Google', 'lead-gen Google campaign', or 'Google Shopping ads'. Requires an existing Google Ads account. REST base https://www.wixapis.com/google-ads/v1."
+description: "Creates and launches a Google Ads Performance Max (PMAX) campaign for a Wix site — a goal-based campaign that runs across all Google channels (Search, Display, YouTube, Gmail, Discover, Maps) from an asset group of headlines, descriptions, images, and (for PMAX Leads) search-theme signals. Covers generating AI text and image assets, generating search themes, getting a Google budget recommendation, assembling the asset group with the required minimum assets, choosing PERFORMANCE_MAX vs PERFORMANCE_MAX_LEADS (leads: phone/form goals, negative keywords, 28-day learning) vs retail/Shopping (Merchant Center feed), creating in PAUSED, and launching. Use for 'create a Performance Max campaign', 'PMAX', 'run ads across all of Google', 'lead-gen Google campaign', or 'Google Shopping ads'. Requires an existing Google Ads account. REST base https://www.wixapis.com/_serverless/pa-google/v1."
 ---
 # RECIPE: Create and Launch a Performance Max Campaign
 
@@ -10,7 +10,7 @@ A **Performance Max (PMAX)** campaign runs across every Google channel from a si
 - **`PERFORMANCE_MAX_LEADS`** — lead-gen variant (phone/form conversions, search-theme signals, negative keywords, a ~28-day learning phase). **Requires** at least one asset group with headlines, descriptions, and images; assets are validated synchronously, so bad assets fail the create call immediately.
 - **Retail / Shopping** — a `PERFORMANCE_MAX` campaign linked to a Google Merchant Center feed (set `merchantCenterAccountId` on the account first — see [install-and-create-account](install-and-create-account.md) — and use `feedLabel`). Retail campaigns don't require a hand-built asset group.
 
-Base URL: `https://www.wixapis.com/google-ads/v1`. `<AUTH>` is the `Authorization` header; body calls also need `Content-Type: application/json`. The bidding strategy is server-enforced to `MAXIMIZE_CONVERSIONS` — never set it yourself.
+Base URL: `https://www.wixapis.com/_serverless/pa-google/v1`. `<AUTH>` is the `Authorization` header; body calls also need `Content-Type: application/json`. The bidding strategy is server-enforced to `MAXIMIZE_CONVERSIONS` — never set it yourself.
 
 > **Launching spends real money.** Present the assembled asset group and budget and get explicit approval before the Launch call (STEP 5). Create in `PAUSED` first — nothing serves until Launch.
 
@@ -25,7 +25,7 @@ Base URL: `https://www.wixapis.com/google-ads/v1`. `<AUTH>` is the `Authorizatio
 `suggestionInfo.landingPageUrl` and `textSuggestionInfo.languageCode` are both required. Response may take up to 60s.
 
 ```bash
-curl -X POST 'https://www.wixapis.com/google-ads/v1/text-asset-suggestions' \
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/text-asset-suggestions' \
   -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
   -d '{
     "suggestionInfo": { "landingPageUrl": "https://www.example.com", "assetTypes": ["HEADLINE", "DESCRIPTION"] },
@@ -46,7 +46,7 @@ curl -X POST 'https://www.wixapis.com/google-ads/v1/text-asset-suggestions' \
 Images are generated with AI and **automatically uploaded to the site's Wix Media Manager** — the returned `url` is a `static.wixstatic.com` link you can use directly in the asset group. `suggestionInfo.landingPageUrl` is required.
 
 ```bash
-curl -X POST 'https://www.wixapis.com/google-ads/v1/image-asset-suggestions' \
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/image-asset-suggestions' \
   -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
   -d '{ "suggestionInfo": { "landingPageUrl": "https://www.example.com", "assetTypes": ["MARKETING_IMAGE", "SQUARE_MARKETING_IMAGE"] } }'
 ```
@@ -63,7 +63,7 @@ curl -X POST 'https://www.wixapis.com/google-ads/v1/image-asset-suggestions' \
 Search themes are the targeting signals for a leads campaign's asset group. `textSuggestionInfo.languageCode` is required.
 
 ```bash
-curl -X POST 'https://www.wixapis.com/google-ads/v1/search-theme-suggestions' \
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/search-theme-suggestions' \
   -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
   -d '{ "landingPageUrl": "https://www.example.com", "textSuggestionInfo": { "languageCode": "en" } }'
 ```
@@ -79,7 +79,7 @@ Each string becomes a `{ "searchTheme": { "text": "…" } }` signal in the asset
 PMAX uses **Generate Budget Recommendation** (not the Smart-campaign budget-suggestions endpoint). `campaignType`, `assetGroupInfo` (with a `finalUrl`), and `currency` are required.
 
 ```bash
-curl -X POST 'https://www.wixapis.com/google-ads/v1/budget-recommendation' \
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/budget-recommendation' \
   -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
   -d '{
     "campaignType": "PERFORMANCE_MAX",
@@ -129,7 +129,7 @@ Image `url` must be a Wix Media Manager URL (`static.wixstatic.com`) — the STE
 **Create a PMAX Leads campaign** (status required; create `PAUSED`):
 
 ```bash
-curl -X POST 'https://www.wixapis.com/google-ads/v1/campaigns' \
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/campaigns' \
   -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
   -d '{
     "campaign": {
@@ -178,7 +178,7 @@ Save the returned `campaign.id` and `resourceName`. `status` is read-only and sy
 ## STEP 5: Launch the campaign
 
 ```bash
-curl -X POST 'https://www.wixapis.com/google-ads/v1/campaigns/{campaignId}/launch' \
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/campaigns/{campaignId}/launch' \
   -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' -d '{}'
 ```
 

package/skills/wix-manage/references/google-ads/get-campaign-suggestions.md

@@ -1,12 +1,12 @@
 ---
 name: "Get AI Campaign Suggestions for Google Ads"
-description: "Reference for the Google Ads Suggestions API on a Wix site: AI/Google-generated inputs that help build effective campaigns — keyword themes (from a URL or autocomplete), geo-target options, low/recommended/high daily-budget tiers with estimated clicks, PMAX budget recommendations, text assets (headlines/descriptions), AI image assets (auto-uploaded to Wix Media), search themes, promotional incentive offers, and complete AI-generated campaign configurations from a campaign brief. Use when the user asks 'suggest keywords for my ads', 'what budget should I use', 'where should I target', 'generate ad copy/headlines', 'generate ad images', 'suggest a whole campaign', or when a create-campaign flow needs suggested values. REST base https://www.wixapis.com/google-ads/v1."
+description: "Reference for the Google Ads Suggestions API on a Wix site: AI/Google-generated inputs that help build effective campaigns — keyword themes (from a URL or autocomplete), geo-target options, low/recommended/high daily-budget tiers with estimated clicks, PMAX budget recommendations, text assets (headlines/descriptions), AI image assets (auto-uploaded to Wix Media), search themes, promotional incentive offers, and complete AI-generated campaign configurations from a campaign brief. Use when the user asks 'suggest keywords for my ads', 'what budget should I use', 'where should I target', 'generate ad copy/headlines', 'generate ad images', 'suggest a whole campaign', or when a create-campaign flow needs suggested values. REST base https://www.wixapis.com/_serverless/pa-google/v1."
 ---
 # RECIPE: Get AI Campaign Suggestions for Google Ads
 
 The Suggestions API produces the values that make a campaign effective — keywords, locations, budgets, and creative assets — either from Google directly or from Wix's AI. It's the input layer for the create-campaign recipes; this file is the standalone reference for each endpoint and for the two that don't appear there (full campaign suggestions from a brief, and incentive offers).
 
-Base URL: `https://www.wixapis.com/google-ads/v1`. `<AUTH>` is the `Authorization` header; body calls also need `Content-Type: application/json`. All suggestion endpoints are **read-only** — none create or spend anything, so run them freely.
+Base URL: `https://www.wixapis.com/_serverless/pa-google/v1`. `<AUTH>` is the `Authorization` header; body calls also need `Content-Type: application/json`. All suggestion endpoints are **read-only** — none create or spend anything, so run them freely.
 
 > **Two conventions to carry into every answer (this is where they trip people up):**
 > - **Budgets come back in micros.** Every `dailyBudget` / `budgetAmountMicros` / `recommendedBudgetAmountMicros` is in micros, where `1,000,000` micros = 1 unit of the account's currency (so `15000000` = $15.00/day). Always convert to currency units when presenting to a user, and pass micros back when creating a campaign.
@@ -39,7 +39,7 @@ Generates one or more complete, ready-to-use campaign configurations — assets,
 - `campaignType` — `SMART` (default) or `PERFORMANCE_MAX_LEADS`.
 
 ```bash
-curl -X POST 'https://www.wixapis.com/google-ads/v1/campaign-suggestions' \
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/campaign-suggestions' \
   -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
   -d '{ "campaignBriefId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "amount": 1, "campaignType": "SMART" }'
 ```
@@ -73,7 +73,7 @@ Present `campaignMessaging` and the config to the user, then use the `campaign`
 Credit offers for **new** accounts, granted after a spend threshold. Only supported currencies return offers. This drives the optional incentive step of [account setup](install-and-create-account.md).
 
 ```bash
-curl -X GET 'https://www.wixapis.com/google-ads/v1/incentives?currency=USD' -H 'Authorization: <AUTH>'
+curl -X GET 'https://www.wixapis.com/_serverless/pa-google/v1/incentives?currency=USD' -H 'Authorization: <AUTH>'
 ```
 
 Returns `lowOffer` / `mediumOffer` / `highOffer`, each with `incentiveId`, `awardAmount`, and `requiredAmount`, plus a `consolidatedTermsAndConditionsUrl`. Pass the chosen `incentiveId` as `selectedIncentiveId` when creating the account.

package/skills/wix-manage/references/google-ads/google-ads-dashboard-navigation.md

@@ -15,7 +15,7 @@ Build direct links into the Google Ads page of a site's dashboard. For the gener
 
 ## Pairing Entities with Their Read APIs
 
-Fetch state via the Google Ads recipes in this area (`GET /google-ads/v1/accounts/current-site`, `GET /google-ads/v1/accounts/current-site/conversion-actions`), then link the page.
+Fetch state via the Google Ads recipes in this area (`GET /_serverless/pa-google/v1/accounts/current-site`, `GET /_serverless/pa-google/v1/accounts/current-site/conversion-actions`), then link the page.
 
 Example — after creating a campaign: