@wix/bookings 1.0.407 → 1.0.409

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/bookings",
-  "version": "1.0.407",
+  "version": "1.0.409",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"
@@ -21,15 +21,15 @@
     "@wix/bookings_attendance": "1.0.39",
     "@wix/bookings_availability-calendar": "1.0.28",
     "@wix/bookings_availability-time-slots": "1.0.24",
-    "@wix/bookings_bookings": "1.0.40",
+    "@wix/bookings_bookings": "1.0.41",
     "@wix/bookings_categories": "1.0.29",
-    "@wix/bookings_extended-bookings": "1.0.33",
+    "@wix/bookings_extended-bookings": "1.0.34",
     "@wix/bookings_external-calendars": "1.0.26",
     "@wix/bookings_multi-service-availability-time-slots": "1.0.23",
-    "@wix/bookings_pricing": "1.0.25",
+    "@wix/bookings_pricing": "1.0.26",
     "@wix/bookings_resources": "1.0.29",
     "@wix/bookings_service-options-and-variants": "1.0.35",
-    "@wix/bookings_services": "1.0.51"
+    "@wix/bookings_services": "1.0.52"
   },
   "devDependencies": {
     "@wix/sdk": "https://cdn.dev.wixpress.com/@wix/sdk/02e8069ab2fd783e0e6a080fc7d590e76cb26ab93c8389574286305b.tar.gz",
@@ -54,5 +54,5 @@
       "fqdn": ""
     }
   },
-  "falconPackageHash": "ab6d9b06613edb46693f1ba445543e61c51b447d088cf1223330f59c"
+  "falconPackageHash": "834d10bbf27b6618972fc9166b6a20c495507bee451e74acee8a83b3"
 }

package/type-bundles/context.bundle.d.ts

@@ -3010,27 +3010,15 @@ interface Booking$2 extends BookingParticipantsInfoOneOf$2 {
     additionalFields?: CustomFormField$2[];
     /**
      * Booking status.
-     * One of:
-     * - `"CREATED"` - The booking was created.
-     * - `"UPDATED"` - The booking was updated.
-     * - `"CONFIRMED"` - The booking was confirmed and appears on the bookings calendar.
-     * A booking can be manually confirmed using the [`Confirm Or Decline API`](www.example.com).
-     * A booking can be automatically confirmed when the following requirements are met:
-     * + The service is configured as automatically confirmed.
-     * + The system invoked the eCommerce checkout API and created an order.
-     * - `"CANCELED"` - The booking has been canceled and synced to the bookings calendar.
-     * The booking can be canceled using [`Cancel Booking API`](www.example.com).
-     * - `"PENDING"` - The booking is waiting to be confirmed or declined by the owner and the booking is synced to the bookings calendar.
-     * Bookings can be manually set as `PENDING` using the [`setAsPending` API](www.example.com), by those with Manage Booking Status permissions scopes.
-     * Bookings can be automatically set as `PENDING` when the following requirements are met:
-     * + The service is configured as manually confirmed.
-     * + Invoking the eCommerce checkout API and an order has been created.
-     * - `"WAITING_LIST"` - The booking is on a waiting list.
-     * - `"DECLINED"` - The booking was declined by the owner and synced to the Bookings calendar.
-     * Bookings can be manually declined using the [`Decline Booking` API](www.example.com) by those with Manage Booking Status permissions scopes.
-     * Booking can be automatically declined when one of the following requirements are met:
-     * + Invoking the `eCommerce checkout` API and the order declined event has been sent.
-     * + Invoking the `eCommerce checkout` API and order approved event has been sent, but the booking is offline and the booking causes a double booking.
+     *
+     * Supported values:
+     * - `CREATED`: The booking was created.
+     * - `UPDATED`: The booking was updated.
+     * - `PENDING`: The booking is waiting to be confirmed or declined by the business owner. A booking is automatically set as `PENDING` if the service is configured to require manual business onwer confirmation and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created.
+     * - `CONFIRMED`: The booking was confirmed. A booking is automatically confirmed if the service is configured to automatically confirm bookings and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created. If the service isn't configured to automatically confirm bookings, you can use [Confirm Or Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/confirm-or-decline-booking).
+     * - `DECLINED`: The booking was declined by the business owner. A booking is also declined if an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created that resulted in a double booking.
+     * - `CANCELED`: The booking was canceled.
+     * - `WAITING_LIST`: The booking is on a wait list.
      */
     status?: BookingStatus$2;
     /**

package/type-bundles/index.bundle.d.ts

@@ -8389,27 +8389,15 @@ interface Booking$2 extends BookingParticipantsInfoOneOf$2 {
     additionalFields?: CustomFormField$2[];
     /**
      * Booking status.
-     * One of:
-     * - `"CREATED"` - The booking was created.
-     * - `"UPDATED"` - The booking was updated.
-     * - `"CONFIRMED"` - The booking was confirmed and appears on the bookings calendar.
-     * A booking can be manually confirmed using the [`Confirm Or Decline API`](www.example.com).
-     * A booking can be automatically confirmed when the following requirements are met:
-     * + The service is configured as automatically confirmed.
-     * + The system invoked the eCommerce checkout API and created an order.
-     * - `"CANCELED"` - The booking has been canceled and synced to the bookings calendar.
-     * The booking can be canceled using [`Cancel Booking API`](www.example.com).
-     * - `"PENDING"` - The booking is waiting to be confirmed or declined by the owner and the booking is synced to the bookings calendar.
-     * Bookings can be manually set as `PENDING` using the [`setAsPending` API](www.example.com), by those with Manage Booking Status permissions scopes.
-     * Bookings can be automatically set as `PENDING` when the following requirements are met:
-     * + The service is configured as manually confirmed.
-     * + Invoking the eCommerce checkout API and an order has been created.
-     * - `"WAITING_LIST"` - The booking is on a waiting list.
-     * - `"DECLINED"` - The booking was declined by the owner and synced to the Bookings calendar.
-     * Bookings can be manually declined using the [`Decline Booking` API](www.example.com) by those with Manage Booking Status permissions scopes.
-     * Booking can be automatically declined when one of the following requirements are met:
-     * + Invoking the `eCommerce checkout` API and the order declined event has been sent.
-     * + Invoking the `eCommerce checkout` API and order approved event has been sent, but the booking is offline and the booking causes a double booking.
+     *
+     * Supported values:
+     * - `CREATED`: The booking was created.
+     * - `UPDATED`: The booking was updated.
+     * - `PENDING`: The booking is waiting to be confirmed or declined by the business owner. A booking is automatically set as `PENDING` if the service is configured to require manual business onwer confirmation and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created.
+     * - `CONFIRMED`: The booking was confirmed. A booking is automatically confirmed if the service is configured to automatically confirm bookings and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created. If the service isn't configured to automatically confirm bookings, you can use [Confirm Or Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/confirm-or-decline-booking).
+     * - `DECLINED`: The booking was declined by the business owner. A booking is also declined if an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created that resulted in a double booking.
+     * - `CANCELED`: The booking was canceled.
+     * - `WAITING_LIST`: The booking is on a wait list.
      */
     status?: BookingStatus$2;
     /**
@@ -10001,6 +9989,7 @@ interface ServiceResource extends ServiceResourceSelectionOneOf {
     resourceIds?: ResourceIds;
     /** The unique identifier for the service resource, if not provided, would default to the resource type id. */
     _id?: string | null;
+    /** Service resource type data. */
     resourceType?: ResourceType;
     /**
      * How many resources of the are required in order to book the service.
@@ -10217,7 +10206,9 @@ interface BulkCreateServicesResponse {
     bulkActionMetadata?: BulkActionMetadata$2;
 }
 interface BulkServiceResult {
+    /** Updated service metadata. */
     itemMetadata?: ItemMetadata$2;
+    /** The updated service. */
     item?: Service;
 }
 interface ItemMetadata$2 {
@@ -10289,10 +10280,11 @@ interface ServiceAvailabilityConstraints {
      */
     locations?: V2Location[];
     /**
+     * Resource groups required to book the service. For backwards compatibility only. Use `serviceResources` instead.
      * @readonly
-     * @deprecated
+     * @deprecated Resource groups required to book the service. For backwards compatibility only. Use `serviceResources` instead.
      * @replacedBy service_resources
-     * @removalDate 2023-09-01
+     * @removalDate 2024-09-01
      */
     resourceGroups?: ResourceGroup[];
     /**
@@ -10374,13 +10366,15 @@ interface V2ParticipantNotification {
 interface DeleteServiceResponse {
 }
 interface BulkDeleteServicesRequest {
+    /** Ids of the services for deletion. */
     ids?: string[];
-    preserveFutureSessionsWithParticipants?: boolean;
     /**
      * Whether to preserve future sessions with participants.
      *
      * Default: `false`.
      */
+    preserveFutureSessionsWithParticipants?: boolean;
+    /** Whether to notify participants about the change and an optional custom message. */
     participantNotification?: V2ParticipantNotification;
 }
 interface BulkDeleteServicesResponse {
@@ -10476,6 +10470,7 @@ interface Cursors$2 {
     prev?: string | null;
 }
 interface SearchServicesRequest {
+    /** WQL, search or aggregation expression. */
     search?: CursorSearch;
 }
 interface CursorSearch extends CursorSearchPagingMethodOneOf {

package/type-bundles/meta.bundle.d.ts

@@ -7126,27 +7126,15 @@ interface Booking$5 extends BookingParticipantsInfoOneOf$5 {
     additionalFields?: CustomFormField$5[];
     /**
      * Booking status.
-     * One of:
-     * - `"CREATED"` - The booking was created.
-     * - `"UPDATED"` - The booking was updated.
-     * - `"CONFIRMED"` - The booking was confirmed and appears on the bookings calendar.
-     * A booking can be manually confirmed using the [`Confirm Or Decline API`](www.example.com).
-     * A booking can be automatically confirmed when the following requirements are met:
-     * + The service is configured as automatically confirmed.
-     * + The system invoked the eCommerce checkout API and created an order.
-     * - `"CANCELED"` - The booking has been canceled and synced to the bookings calendar.
-     * The booking can be canceled using [`Cancel Booking API`](www.example.com).
-     * - `"PENDING"` - The booking is waiting to be confirmed or declined by the owner and the booking is synced to the bookings calendar.
-     * Bookings can be manually set as `PENDING` using the [`setAsPending` API](www.example.com), by those with Manage Booking Status permissions scopes.
-     * Bookings can be automatically set as `PENDING` when the following requirements are met:
-     * + The service is configured as manually confirmed.
-     * + Invoking the eCommerce checkout API and an order has been created.
-     * - `"WAITING_LIST"` - The booking is on a waiting list.
-     * - `"DECLINED"` - The booking was declined by the owner and synced to the Bookings calendar.
-     * Bookings can be manually declined using the [`Decline Booking` API](www.example.com) by those with Manage Booking Status permissions scopes.
-     * Booking can be automatically declined when one of the following requirements are met:
-     * + Invoking the `eCommerce checkout` API and the order declined event has been sent.
-     * + Invoking the `eCommerce checkout` API and order approved event has been sent, but the booking is offline and the booking causes a double booking.
+     *
+     * Supported values:
+     * - `CREATED`: The booking was created.
+     * - `UPDATED`: The booking was updated.
+     * - `PENDING`: The booking is waiting to be confirmed or declined by the business owner. A booking is automatically set as `PENDING` if the service is configured to require manual business onwer confirmation and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created.
+     * - `CONFIRMED`: The booking was confirmed. A booking is automatically confirmed if the service is configured to automatically confirm bookings and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created. If the service isn't configured to automatically confirm bookings, you can use [Confirm Or Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/confirm-or-decline-booking).
+     * - `DECLINED`: The booking was declined by the business owner. A booking is also declined if an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created that resulted in a double booking.
+     * - `CANCELED`: The booking was canceled.
+     * - `WAITING_LIST`: The booking is on a wait list.
      */
     status?: BookingStatus$5;
     /**
@@ -7848,27 +7836,15 @@ interface Booking$4 extends BookingParticipantsInfoOneOf$4 {
     additionalFields?: CustomFormField$4[];
     /**
      * Booking status.
-     * One of:
-     * - `"CREATED"` - The booking was created.
-     * - `"UPDATED"` - The booking was updated.
-     * - `"CONFIRMED"` - The booking was confirmed and appears on the bookings calendar.
-     * A booking can be manually confirmed using the [`Confirm Or Decline API`](www.example.com).
-     * A booking can be automatically confirmed when the following requirements are met:
-     * + The service is configured as automatically confirmed.
-     * + The system invoked the eCommerce checkout API and created an order.
-     * - `"CANCELED"` - The booking has been canceled and synced to the bookings calendar.
-     * The booking can be canceled using [`Cancel Booking API`](www.example.com).
-     * - `"PENDING"` - The booking is waiting to be confirmed or declined by the owner and the booking is synced to the bookings calendar.
-     * Bookings can be manually set as `PENDING` using the [`setAsPending` API](www.example.com), by those with Manage Booking Status permissions scopes.
-     * Bookings can be automatically set as `PENDING` when the following requirements are met:
-     * + The service is configured as manually confirmed.
-     * + Invoking the eCommerce checkout API and an order has been created.
-     * - `"WAITING_LIST"` - The booking is on a waiting list.
-     * - `"DECLINED"` - The booking was declined by the owner and synced to the Bookings calendar.
-     * Bookings can be manually declined using the [`Decline Booking` API](www.example.com) by those with Manage Booking Status permissions scopes.
-     * Booking can be automatically declined when one of the following requirements are met:
-     * + Invoking the `eCommerce checkout` API and the order declined event has been sent.
-     * + Invoking the `eCommerce checkout` API and order approved event has been sent, but the booking is offline and the booking causes a double booking.
+     *
+     * Supported values:
+     * - `CREATED`: The booking was created.
+     * - `UPDATED`: The booking was updated.
+     * - `PENDING`: The booking is waiting to be confirmed or declined by the business owner. A booking is automatically set as `PENDING` if the service is configured to require manual business onwer confirmation and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created.
+     * - `CONFIRMED`: The booking was confirmed. A booking is automatically confirmed if the service is configured to automatically confirm bookings and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created. If the service isn't configured to automatically confirm bookings, you can use [Confirm Or Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/confirm-or-decline-booking).
+     * - `DECLINED`: The booking was declined by the business owner. A booking is also declined if an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created that resulted in a double booking.
+     * - `CANCELED`: The booking was canceled.
+     * - `WAITING_LIST`: The booking is on a wait list.
      */
     status?: BookingStatus$4;
     /**
@@ -12455,27 +12431,15 @@ interface Booking$3 extends BookingParticipantsInfoOneOf$3 {
     additionalFields?: CustomFormField$3[];
     /**
      * Booking status.
-     * One of:
-     * - `"CREATED"` - The booking was created.
-     * - `"UPDATED"` - The booking was updated.
-     * - `"CONFIRMED"` - The booking was confirmed and appears on the bookings calendar.
-     * A booking can be manually confirmed using the [`Confirm Or Decline API`](www.example.com).
-     * A booking can be automatically confirmed when the following requirements are met:
-     * + The service is configured as automatically confirmed.
-     * + The system invoked the eCommerce checkout API and created an order.
-     * - `"CANCELED"` - The booking has been canceled and synced to the bookings calendar.
-     * The booking can be canceled using [`Cancel Booking API`](www.example.com).
-     * - `"PENDING"` - The booking is waiting to be confirmed or declined by the owner and the booking is synced to the bookings calendar.
-     * Bookings can be manually set as `PENDING` using the [`setAsPending` API](www.example.com), by those with Manage Booking Status permissions scopes.
-     * Bookings can be automatically set as `PENDING` when the following requirements are met:
-     * + The service is configured as manually confirmed.
-     * + Invoking the eCommerce checkout API and an order has been created.
-     * - `"WAITING_LIST"` - The booking is on a waiting list.
-     * - `"DECLINED"` - The booking was declined by the owner and synced to the Bookings calendar.
-     * Bookings can be manually declined using the [`Decline Booking` API](www.example.com) by those with Manage Booking Status permissions scopes.
-     * Booking can be automatically declined when one of the following requirements are met:
-     * + Invoking the `eCommerce checkout` API and the order declined event has been sent.
-     * + Invoking the `eCommerce checkout` API and order approved event has been sent, but the booking is offline and the booking causes a double booking.
+     *
+     * Supported values:
+     * - `CREATED`: The booking was created.
+     * - `UPDATED`: The booking was updated.
+     * - `PENDING`: The booking is waiting to be confirmed or declined by the business owner. A booking is automatically set as `PENDING` if the service is configured to require manual business onwer confirmation and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created.
+     * - `CONFIRMED`: The booking was confirmed. A booking is automatically confirmed if the service is configured to automatically confirm bookings and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created. If the service isn't configured to automatically confirm bookings, you can use [Confirm Or Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/confirm-or-decline-booking).
+     * - `DECLINED`: The booking was declined by the business owner. A booking is also declined if an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created that resulted in a double booking.
+     * - `CANCELED`: The booking was canceled.
+     * - `WAITING_LIST`: The booking is on a wait list.
      */
     status?: BookingStatus$3;
     /**
@@ -15516,27 +15480,15 @@ interface Booking$1 extends BookingParticipantsInfoOneOf$1 {
     additionalFields?: CustomFormField$1[];
     /**
      * Booking status.
-     * One of:
-     * - `"CREATED"` - The booking was created.
-     * - `"UPDATED"` - The booking was updated.
-     * - `"CONFIRMED"` - The booking was confirmed and appears on the bookings calendar.
-     * A booking can be manually confirmed using the [`Confirm Or Decline API`](www.example.com).
-     * A booking can be automatically confirmed when the following requirements are met:
-     * + The service is configured as automatically confirmed.
-     * + The system invoked the eCommerce checkout API and created an order.
-     * - `"CANCELED"` - The booking has been canceled and synced to the bookings calendar.
-     * The booking can be canceled using [`Cancel Booking API`](www.example.com).
-     * - `"PENDING"` - The booking is waiting to be confirmed or declined by the owner and the booking is synced to the bookings calendar.
-     * Bookings can be manually set as `PENDING` using the [`setAsPending` API](www.example.com), by those with Manage Booking Status permissions scopes.
-     * Bookings can be automatically set as `PENDING` when the following requirements are met:
-     * + The service is configured as manually confirmed.
-     * + Invoking the eCommerce checkout API and an order has been created.
-     * - `"WAITING_LIST"` - The booking is on a waiting list.
-     * - `"DECLINED"` - The booking was declined by the owner and synced to the Bookings calendar.
-     * Bookings can be manually declined using the [`Decline Booking` API](www.example.com) by those with Manage Booking Status permissions scopes.
-     * Booking can be automatically declined when one of the following requirements are met:
-     * + Invoking the `eCommerce checkout` API and the order declined event has been sent.
-     * + Invoking the `eCommerce checkout` API and order approved event has been sent, but the booking is offline and the booking causes a double booking.
+     *
+     * Supported values:
+     * - `CREATED`: The booking was created.
+     * - `UPDATED`: The booking was updated.
+     * - `PENDING`: The booking is waiting to be confirmed or declined by the business owner. A booking is automatically set as `PENDING` if the service is configured to require manual business onwer confirmation and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created.
+     * - `CONFIRMED`: The booking was confirmed. A booking is automatically confirmed if the service is configured to automatically confirm bookings and an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created. If the service isn't configured to automatically confirm bookings, you can use [Confirm Or Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/confirm-or-decline-booking).
+     * - `DECLINED`: The booking was declined by the business owner. A booking is also declined if an [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) was created that resulted in a double booking.
+     * - `CANCELED`: The booking was canceled.
+     * - `WAITING_LIST`: The booking is on a wait list.
      */
     status?: BookingStatus$1;
     /**