@wix/auto_sdk_bookings_bookings 1.0.40 → 1.0.42

package/build/es/index.typings.d.mts

@@ -3,16 +3,19 @@ import { NonNullablePaths } from '@wix/sdk-types';
 /** An entity representing a scheduled appointment, class session, or course. */
 interface Booking extends BookingParticipantsInfoOneOf {
     /**
-     * Total number of participants. Available only when the relevant service
-     * doesn't have _variants and options_
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
+     * Total number of participants.
+     * When creating a booking, use this field only if the relevant service has fixed pricing and doesn't offer variants and options ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
      * @min 1
      */
     totalParticipants?: number;
     /**
-     * Information about the booked service choices and participants.
-     * Available only when the booking includes multiple _service variants_
+     * Information about the booked service choices and participant count for each choice.
+     * When creating a booking, use this field only if the booking includes multiple service variants
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
+     *
+     * For example, use this for a spa package booking that includes different service levels:
+     * - 2 participants chose "Standard Package".
+     * - 1 participant chose "VIP Package".
      */
     participantsChoices?: ParticipantChoices;
     /**
@@ -22,15 +25,24 @@ interface Booking extends BookingParticipantsInfoOneOf {
      */
     _id?: string | null;
     /**
-     * An object describing the *slot*
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/availability-calendar/query-availability) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/time-slots/availability-calendar/query-availability))
-     * or *schedule*
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/calendar/schedules/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction))
-     * that was booked.
+     * An object describing the bookable entity - either a specific time slot or a recurring schedule.
+     *
+     * The structure depends on the type of service being booked:
+     *
+     * *For appointment services:** Use `slot` to book a specific time slot with a
+     * service provider. Appointments are typically one-time sessions at a specific date and time.
+     *
+     * *For class services:** Use `slot` to book a specific class session. Classes
+     * are individual sessions that can have multiple participants.
+     *
+     * *For course services:** Use `schedule` to book an entire course consisting of
+     * multiple sessions over time. Courses are recurring, multi-session offerings.
+     *
+     * Choose the appropriate field based on your service type and booking requirements.
      */
     bookedEntity?: BookedEntity;
     /**
-     * Contact details of the site visitor or *member*
+     * Contact details of the site visitor or member
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/members/members/introduction) | [REST](https://dev.wix.com/docs/rest/crm/members-contacts/members/members/introduction))
      * making the booking.
      */
@@ -45,20 +57,27 @@ interface Booking extends BookingParticipantsInfoOneOf {
      */
     status?: BookingStatusWithLiterals;
     /**
-     * The payment status of the booking corresponds to the `paymentStatus` of the
-     * related *eCommerce order*
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/orders/setup)| [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction)),
-     * if one exists. All payment statuses are supported for every booking `status`.
+     * The payment status of the booking. This field automatically syncs with the
+     * `paymentStatus` of the corresponding eCommerce order
+     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/orders/setup)| [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction))
+     * when customers use Wix eCommerce checkout.
+     *
+     * ## Integration patterns
+     *
+     * *When using Wix eCommerce checkout:** Wix Bookings automatically syncs the payment status based on the eCommerce order's payment status.
+     * Do not manually update this field.
+     *
+     * *When using custom payment flows:** You can manually update the payment status with Confirm Booking or Decline Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/confirm-or-decline-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking)) to reflect the customer's payment state.
+     *
+     * *For membership/pricing plan payments:** Wix Bookings automatically manages the payment status when customers pay with an active pricing plan ([SDK](https://dev.wix.com/docs/sdk/backend-modules/pricing-plans/plans/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/pricing-plans/pricing-plans/introduction)) subscription.
+     *
+     * All payment statuses are supported for every booking `status`.
      */
     paymentStatus?: PaymentStatusWithLiterals;
     /**
-     * Payment option selected by the customer. If the customer hasn't completed their
-     * checkout, they may still change the payment method. Must be one of the payment
-     * options offered by the service ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/services/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/introduction)),
-     * unless `skipSelectedPaymentOptionValidation` is `true`.
-     * When undefined during an *eCommerce checkout*
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction)),
-     * Wix Bookings uses the service's default payment option
+     * Payment option selected by the customer. If the customer hasn't completed their checkout, they may still change the payment method. Must be one of the payment options offered by the service ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/services/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/introduction)), unless `skipSelectedPaymentOptionValidation` is `true`.
+     *
+     * When undefined during an eCommerce checkout ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction)), Wix Bookings uses the service's default payment option
      */
     selectedPaymentOption?: SelectedPaymentOptionWithLiterals;
     /**
@@ -69,10 +88,8 @@ interface Booking extends BookingParticipantsInfoOneOf {
     /** External user ID that you can provide. */
     externalUserId?: string | null;
     /**
-     * Revision number to be used when updating, rescheduling, or cancelling the
-     * booking. Increments by 1 each time the booking is updated, rescheduled, or
-     * canceled. To prevent conflicting changes, the current revision must be
-     * specified when updating the booking.
+     * Revision number to be used when updating, rescheduling, or cancelling the booking.
+     * Increments by 1 each time the booking is updated, rescheduled, or canceled. To prevent conflicting changes, the current revision must be specified when updating the booking.
      */
     revision?: string | null;
     /**
@@ -113,50 +130,64 @@ interface Booking extends BookingParticipantsInfoOneOf {
 /** @oneof */
 interface BookingParticipantsInfoOneOf {
     /**
-     * Total number of participants. Available only when the relevant service
-     * doesn't have _variants and options_
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
+     * Total number of participants.
+     * When creating a booking, use this field only if the relevant service has fixed pricing and doesn't offer variants and options ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
      * @min 1
      */
     totalParticipants?: number;
     /**
-     * Information about the booked service choices and participants.
-     * Available only when the booking includes multiple _service variants_
+     * Information about the booked service choices and participant count for each choice.
+     * When creating a booking, use this field only if the booking includes multiple service variants
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
+     *
+     * For example, use this for a spa package booking that includes different service levels:
+     * - 2 participants chose "Standard Package".
+     * - 1 participant chose "VIP Package".
      */
     participantsChoices?: ParticipantChoices;
 }
 /**
- * A multi-service booking is considered available if all individual bookings are available as returned from List Multi Service Availability Time Slots.
+ * A multi-service booking is considered available if all single-service bookings are available as returned from List Multi Service Availability Time Slots.
  * Currently, `SEPARATE_BOOKINGS` and `PARALLEL_BOOKINGS` are not supported.
  * Multi-service booking is available if each of its bookings is available separately.
  * For `SEQUENTIAL_BOOKINGS`, see `List Multi Service Availability Time Slots` documentation.
  */
 declare enum MultiServiceBookingType {
+    /** You must schedule single-service bookings back-to-back with each booking starting when the previous booking ends */
     SEQUENTIAL_BOOKINGS = "SEQUENTIAL_BOOKINGS",
+    /** Not currently supported. */
     SEPARATE_BOOKINGS = "SEPARATE_BOOKINGS",
+    /** Not currently supported. */
     PARALLEL_BOOKINGS = "PARALLEL_BOOKINGS"
 }
 /** @enumType */
 type MultiServiceBookingTypeWithLiterals = MultiServiceBookingType | 'SEQUENTIAL_BOOKINGS' | 'SEPARATE_BOOKINGS' | 'PARALLEL_BOOKINGS';
 interface BookedEntity extends BookedEntityItemOneOf {
     /**
-     * Booked *slot*
+     * Booked slot
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/availability-calendar/query-availability) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/time-slots/availability-calendar/query-availability)).
-     * Available only for appointment-based services and classes.
-     * For appointment-based services, a new session is created, while for classes,
-     * the booking is automatically linked to the existing session.
+     *
+     * Specify `slot` when creating bookings for:
+     * - **Appointment-based services:** Individual sessions with service providers (consultations, treatments).
+     * Wix Bookings creates a new session when the booking is confirmed.
+     * - **Class services:** Group sessions at specific times (fitness classes, workshops).
+     * Wix Bookings links the booking to an existing scheduled session.
+     *
+     * For course services, specify `schedule` instead of `slot`.
      */
     slot?: BookedSlot;
     /**
-     * Booked *schedule*
+     * Booked schedule
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/calendar/schedules/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction)).
-     * Available only for course bookings.
+     *
+     * Specify `schedule` when creating bookings for:
+     * - **Course services:** Multi-session offerings spanning weeks or months (educational courses, training programs).
+     * Wix Bookings enrolls participants in all sessions defined by the course schedule.
      */
     schedule?: BookedSchedule;
     /**
      * Session title at the time of booking. If there is no pre-existing session,
-     * for example for appointment-based services, `title` is set to the service name.
+     * for example for appointment-based services, Wix Bookings sets `title` to the service name.
      * @readonly
      * @maxLength 6000
      */
@@ -173,17 +204,25 @@ interface BookedEntity extends BookedEntityItemOneOf {
 /** @oneof */
 interface BookedEntityItemOneOf {
     /**
-     * Booked *slot*
+     * Booked slot
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/availability-calendar/query-availability) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/time-slots/availability-calendar/query-availability)).
-     * Available only for appointment-based services and classes.
-     * For appointment-based services, a new session is created, while for classes,
-     * the booking is automatically linked to the existing session.
+     *
+     * Specify `slot` when creating bookings for:
+     * - **Appointment-based services:** Individual sessions with service providers (consultations, treatments).
+     * Wix Bookings creates a new session when the booking is confirmed.
+     * - **Class services:** Group sessions at specific times (fitness classes, workshops).
+     * Wix Bookings links the booking to an existing scheduled session.
+     *
+     * For course services, specify `schedule` instead of `slot`.
      */
     slot?: BookedSlot;
     /**
-     * Booked *schedule*
+     * Booked schedule
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/calendar/schedules/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction)).
-     * Available only for course bookings.
+     *
+     * Specify `schedule` when creating bookings for:
+     * - **Course services:** Multi-session offerings spanning weeks or months (educational courses, training programs).
+     * Wix Bookings enrolls participants in all sessions defined by the course schedule.
      */
     schedule?: BookedSchedule;
 }
@@ -195,35 +234,25 @@ interface BookedSlot {
     /** Schedule ID. */
     scheduleId?: string;
     /**
-     * ID of the corresponding *event*
+     * ID of the corresponding event
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/calendar/events/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction)).
      * Available for both appointment and class bookings, not available for course bookings.
-     * For appointment-based services, Wix Bookings automatically populates `eventId`
-     * when the booking `status` changes to `CONFIRMED`. For class bookings, it's
-     * automatically populated upon booking creation.
+     * For appointment-based services, Wix Bookings automatically populates `eventId` when the booking `status` changes to `CONFIRMED`.
+     * For class bookings, Wix Bookings automatically populates `eventId` upon booking creation.
      * @minLength 36
      * @maxLength 250
      */
     eventId?: string | null;
-    /**
-     * The start time of this slot in [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339)
-     * format.
-     */
+    /** The start time of this slot in [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339) format. */
     startDate?: string | null;
-    /**
-     * The end time of this slot in [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339)
-     * format.
-     */
+    /** The end time of this slot in [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339) format. */
     endDate?: string | null;
-    /** The timezone according to which the slot was shown to the user when booking, and should be shown in the future. */
+    /** The time zone according to which the slot was shown to the user when booking, and should be shown in the future. */
     timezone?: string | null;
     /**
-     * Primary *resource*
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/resources/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/resources-v2/introduction))
-     * for the booking. For example, the *staff member*
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/staff-members/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/staff-members/introduction))
-     * providing the
-     * service.
+     * Primary resource
+     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/resources/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/resources-v2/introduction)) for the booking.
+     * For example, the staff member ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/staff-members/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/staff-members/introduction)) providing the service.
      */
     resource?: BookedResource;
     /** Location where the session takes place. */
@@ -285,10 +314,7 @@ declare enum LocationType {
 /** @enumType */
 type LocationTypeWithLiterals = LocationType | 'UNDEFINED' | 'OWNER_BUSINESS' | 'OWNER_CUSTOM' | 'CUSTOM';
 interface BookedSchedule {
-    /**
-     * _Schedule ID_
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/calendar/schedules/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction)).
-     */
+    /** Schedule ID ([SDK](https://dev.wix.com/docs/sdk/backend-modules/calendar/schedules/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction)). */
     scheduleId?: string;
     /**
      * Booked service ID.
@@ -296,26 +322,22 @@ interface BookedSchedule {
      */
     serviceId?: string | null;
     /**
-     * _Location_
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/business-tools/locations/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/locations/introduction))
-     * where the schedule's sessions take place.
+     * Location ([SDK](https://dev.wix.com/docs/sdk/backend-modules/business-tools/locations/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/locations/introduction)) where the schedule's sessions take place.
      * @readonly
      */
     location?: Location;
     /**
-     * Timezone in which the slot or session was shown to the customer when they booked.
+     * Time zone in which the slot or session was shown to the customer when they booked.
      * Also used whenever the customer reviews the booking's timing in the future.
      */
     timezone?: string | null;
     /**
-     * Start time of the first session related to the booking in
-     * [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339) format.
+     * Start time of the first session related to the booking in [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339) format.
      * @readonly
      */
     firstSessionStart?: string | null;
     /**
-     * End time of the last session related to the booking in
-     * [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339) format.
+     * End time of the last session related to the booking in [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339) format.
      * @readonly
      */
     lastSessionEnd?: string | null;
@@ -442,38 +464,26 @@ declare enum ValueType {
 type ValueTypeWithLiterals = ValueType | 'SHORT_TEXT' | 'LONG_TEXT' | 'CHECK_BOX';
 /** Booking status. */
 declare enum BookingStatus {
-    /**
-     * The booking was created, but the customer hasn't completed the related
-     * eCommerce order yet.
-     */
+    /** The booking was created, but the customer hasn't completed the related eCommerce order yet. */
     CREATED = "CREATED",
     /**
-     * The merchant has confirmed the booking and it appears in the
-     * business calendar. Merchants can set up their *services*
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/services/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/introduction))
-     * to automatically confirm all `PENDING` bookings.
+     * The merchant has confirmed the booking and it appears in the business calendar. Merchants can set up their services
+     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/services/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/introduction)) to automatically confirm all `PENDING` bookings.
      */
     CONFIRMED = "CONFIRMED",
     /**
-     * The customer has canceled the booking. Depending on the relevant service's
-     * _policy snapshot_
+     * The customer has canceled the booking. Depending on the relevant service's policy snapshot
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/booking-policy-snapshots/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/policies/booking-policy-snapshots/introduction))
-     * they may have to pay a _cancellation fee_
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/booking-fees/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/pricing/booking-fees/introduction)).
+     * they may have to pay a cancellation fee ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/booking-fees/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/pricing/booking-fees/introduction)).
      */
     CANCELED = "CANCELED",
-    /**
-     * The merchant must manually confirm the booking before it appears
-     * in the business calendar.
-     */
+    /** The merchant must manually confirm the booking before it appears in the business calendar. */
     PENDING = "PENDING",
     /** The merchant has declined the booking before the customer was charged. */
     DECLINED = "DECLINED",
     /**
      * The booking is on a waitlist.
-     * Currently, you can't call Register to Waitlist
-     * ([REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/waitlist/register-to-waitlist))
-     * for course or appointment bookings, even though this is supported in live sites.
+     * Currently, you can't call Register to Waitlist ([REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/waitlist/register-to-waitlist)) for course or appointment bookings, even though this is supported in live sites.
      * You can call Register to Waitlist only for class session bookings.
      */
     WAITING_LIST = "WAITING_LIST"
@@ -557,7 +567,7 @@ declare enum Actor {
 type ActorWithLiterals = Actor | 'UNDEFINED_ACTOR' | 'BUSINESS' | 'CUSTOMER';
 interface ParticipantNotification {
     /**
-     * Whether to send the message about the changes to the customer.
+     * Whether to send a message about the changes to the customer.
      *
      * Default: `false`
      */
@@ -624,12 +634,25 @@ declare enum IdentificationDataIdentityType {
 }
 /** @enumType */
 type IdentificationDataIdentityTypeWithLiterals = IdentificationDataIdentityType | 'UNKNOWN' | 'ANONYMOUS_VISITOR' | 'MEMBER' | 'WIX_USER' | 'APP';
+/**
+ * Settings that control booking flow behavior and override default business rules.
+ *
+ * These settings allow administrators to bypass standard validation checks
+ * and policies when creating, confirming, rescheduling, or canceling bookings.
+ * Most settings require elevated permissions to use.
+ *
+ * Use flow control settings to handle special scenarios like:
+ * - Emergency bookings outside normal business hours
+ * - Admin-initiated bookings that bypass availability checks
+ * - Custom payment flows that don't use standard eCommerce checkout
+ * - Overriding cancellation or rescheduling policies in exceptional cases
+ */
 interface FlowControlSettings {
     /** Whether availability is checked when creating or confirming the booking. */
     skipAvailabilityValidation?: boolean;
     /**
      * Whether the booking's `status` is automatically updated to `CONFIRMED` when
-     * the customer completes the *eCommerce checkout*
+     * the customer completes the eCommerce checkout
      * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction)),
      * regardless of whether the relevant service requires manual business confirmation.
      */
@@ -667,8 +690,7 @@ interface ParticipantChoices {
 }
 interface ServiceChoices {
     /**
-     * Number of participants for this _variant_
-     * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
+     * Number of participants for this variant ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
      * @min 1
      */
     numberOfParticipants?: number | null;
@@ -733,36 +755,36 @@ interface MultiServiceBookingInfo {
 }
 interface BookedAddOn {
     /**
-     * The ID of the Add-On.
+     * The ID of the add-on.
      * @format GUID
      */
     _id?: string;
     /**
-     * The ID of the Add-Ons group.
+     * The ID of the add-on group.
      * @format GUID
      */
     groupId?: string;
     /**
-     * The Add-On duration in minutes at the time of Booking.
+     * The add-on duration in minutes at the time of booking.
      * @min 1
      * @max 1440
      * @readonly
      */
     durationInMinutes?: number | null;
     /**
-     * The quantity of booked Add-Ons.
+     * The quantity of booked add-ons.
      * @min 1
      * @max 1000
      */
     quantity?: number | null;
     /**
-     * Add-On name at the time of booking.
+     * Add-on `name` at the time of booking.
      * @maxLength 100
      * @readonly
      */
     name?: string | null;
     /**
-     * Add-On name translated to the language the booking was made in.
+     * Add-on name translated to the language the customer used during booking.
      * @maxLength 100
      * @readonly
      */
@@ -1482,7 +1504,14 @@ interface CreateBookingFlowControlSettings {
     /**
      * Whether the availability is checked before creating the booking.
      *
-     * When passing `false`, a booking is only created when the slot or schedule is available.
+     * - `false`: A booking is only created when the slot or schedule is available.
+     * - `true`: The booking is created regardless of availability conflicts. Make sure the call's [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities) has the required permissions.
+     *
+     * *Use cases for `true`:**
+     * - Emergency or priority bookings that must be accommodated.
+     * - Administrative bookings that override normal availability rules.
+     * - Testing or demonstration purposes.
+     *
      * Default: `false`.
      */
     skipAvailabilityValidation?: boolean;
@@ -1490,7 +1519,7 @@ interface CreateBookingFlowControlSettings {
      * Whether `PENDING` bookings are automatically set to `CONFIRMED` for
      * services that normally require the owner's manual confirmation.
      *
-     * Your app must have the `BOOKINGS.OVERRIDE_AVAILABILITY` permission scope
+     * Your app must have the `BOOKINGS.OVERRIDE_AVAILABILITY` permission
      * when passing `true`.
      * Default: `false`.
      */
@@ -1499,7 +1528,7 @@ interface CreateBookingFlowControlSettings {
      * Whether customers can pay using a payment method that isn't supported
      * for the service, but that's supported for other services.
      *
-     * Your app must have the `BOOKINGS.MANAGE_PAYMENTS` permission scope when passing
+     * Your app must have the `BOOKINGS.MANAGE_PAYMENTS` permission when passing
      * `true`.
      * Default: `false`.
      */
@@ -2595,47 +2624,58 @@ interface CountBookingsResponse {
 }
 interface CreateMultiServiceBookingRequest {
     /**
-     * Single-service bookings to combine in a multi-service booking.
+     * Between 2 to 8 new single-service booking specifications to create and combine in a multi-service booking.
+     *
+     * Each single-service booking specification must include `slot` details (`scheduleId`, `startDate`, and `endDate`).
+     * Specify contact details, number of participants, and any additional fields as needed.
+     *
+     * For sequential bookings, ensure the timing allows services to be scheduled back-to-back.
      * @minSize 2
      * @maxSize 8
      */
     bookings: Booking[];
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Whether to send an SMS reminder to the customer 24 hours before the
-     * session starts. The phone number is taken from `contactDetails.phone`.
+     * Whether to send an SMS reminder to the customer 24 hours before the session starts.
+     * Wix Bookings takes the phone number from `contactDetails.phone`.
      *
      * Default: `true`
      */
     sendSmsReminder?: boolean | null;
     /**
      * Whether to ignore specific standard procedures of the Wix Bookings flow.
-     * For example, whether to check availability before updating the status.
+     * For example, whether to skip checking availability before updating the status.
      */
     flowControlSettings?: CreateBookingFlowControlSettings;
     /** Whether to return the created single-service bookings. */
     returnFullEntity?: boolean;
-    /** Multi service booking type. */
+    /**
+     * Multi-service booking type.
+     *
+     * Currently only `SEQUENTIAL_BOOKINGS` is supported.
+     */
     multiServiceBookingType?: MultiServiceBookingTypeWithLiterals;
 }
 interface CreateMultiServiceBookingResponse {
     /**
-     * Created multi service booking.
-     * Contains the booking results in the same order as specified in the request.
+     * Created multi-service booking.
+     * Contains the single-service bookings in the same order as specified in the request.
      */
     multiServiceBooking?: MultiServiceBooking;
 }
+/**
+ * A multi-service booking combines multiple single-service bookings into a package.
+ *
+ * Currently, multi-service bookings support only sequential scheduling where services are scheduled back-to-back at the same location, with each single-service booking starting when the previous 1 ends.
+ */
 interface MultiServiceBooking {
     /**
      * Multi-service booking ID.
      * @format GUID
      */
     _id?: string | null;
-    /** The created bookings that are part of the multi-service booking. */
+    /** The single-service bookings that make up the multi-service booking package. */
     bookings?: BookingResult[];
 }
 interface BookingResult {
@@ -2649,22 +2689,17 @@ interface BookingResult {
 }
 interface RescheduleMultiServiceBookingRequest {
     /**
-     * ID of the multi service booking to reschedule.
+     * ID of the multi-service booking to reschedule.
      * @format GUID
      */
     multiServiceBookingId: string | null;
     /** Information about the single-service bookings to reschedule. */
     rescheduleBookingsInfo: RescheduleBookingInfo[];
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * rescheduling flow are changed. For example, whether the availability of
-     * the new slot is checked before rescheduling the booking or if you can
-     * reschedule the booking even though the rescheduling policy doesn't allow it.
+     * Information about whether specific procedures of the standard Wix Bookings rescheduling flow are changed.
+     * For example, whether the availability of the new slot is checked before rescheduling the booking or if the customer can reschedule the booking even though the service's rescheduling policy doesn't allow it.
      */
     flowControlSettings?: RescheduleBookingFlowControlSettings;
     /** Whether to return the rescheduled bookings entities. */
@@ -2672,13 +2707,12 @@ interface RescheduleMultiServiceBookingRequest {
 }
 interface RescheduleBookingInfo extends RescheduleBookingInfoParticipantsInfoOneOf {
     /**
-     * Total number of participants. Available only for services with variants.
+     * Total number of participants. Available only for services with variants ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
      * Specify when all participants book the same variant.
      */
     totalParticipants?: number;
     /**
-     * Information about the service choices to book. Available only for services with
-     * variants.
+     * Information about the service choices to book. Available only for services with variants ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
      * Specify when not all participants book the same variant.
      */
     participantsChoices?: ParticipantChoices;
@@ -2691,21 +2725,19 @@ interface RescheduleBookingInfo extends RescheduleBookingInfoParticipantsInfoOne
     slot?: V2Slot;
     /**
      * Revision number, which increments by 1 each time the booking is updated.
-     * To prevent conflicting changes, the current revision must be specified when
-     * managing the booking.
+     * To prevent conflicting changes, the current revision must be specified when managing the booking.
      */
     revision?: string | null;
 }
 /** @oneof */
 interface RescheduleBookingInfoParticipantsInfoOneOf {
     /**
-     * Total number of participants. Available only for services with variants.
+     * Total number of participants. Available only for services with variants ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
      * Specify when all participants book the same variant.
      */
     totalParticipants?: number;
     /**
-     * Information about the service choices to book. Available only for services with
-     * variants.
+     * Information about the service choices to book. Available only for services with variants ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
      * Specify when not all participants book the same variant.
      */
     participantsChoices?: ParticipantChoices;
@@ -2728,11 +2760,11 @@ interface GetMultiServiceBookingAvailabilityResponse {
     totalCapacity?: number | null;
     /** Number of open spots. */
     remainingCapacity?: number | null;
-    /** Indicators for policy violations of the multi service booking. */
+    /** Indicators for policy violations of the multi-service booking. */
     policyViolations?: BookingPolicyViolations;
     /** Multi-service booking policy settings. */
     policySettings?: BookingPolicySettings;
-    /** Info of the bookings this availability was calculated for. */
+    /** Details of the multi-service booking. */
     multiServiceBookingInfo?: GetMultiServiceBookingAvailabilityResponseBookingInfo[];
 }
 interface GetMultiServiceBookingAvailabilityResponseBookingInfo {
@@ -2748,16 +2780,11 @@ interface CancelMultiServiceBookingRequest {
      * @format GUID
      */
     multiServiceBookingId: string | null;
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * cancellation flow are changed. For example, whether you can cancel
-     * a booking even though the cancellation policy doesn't allow it or whether
-     * to issue a refund.
+     * Information about whether specific procedures of the standard Wix Bookings cancellation flow are changed.
+     * For example, whether the customer can cancel the booking even though the service's cancellation policy doesn't allow it or whether to issue a refund upon cancellation.
      */
     flowControlSettings?: CancelBookingFlowControlSettings;
     /** Whether to return the canceled single-service bookings. */
@@ -2775,26 +2802,26 @@ interface MarkMultiServiceBookingAsPendingRequest {
     multiServiceBookingId: string | null;
     /** Information about the single-service bookings to mark as `PENDING`. */
     markAsPendingBookingsInfo?: BookingInfo[];
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Whether to send an SMS reminder to the customer 24 hours before the
-     * session starts. The phone number is taken from `contactDetails.phone`.
+     * Whether to send an SMS reminder to the customer 24 hours before the session starts.
+     * Wix Bookings takes the phone number from `contactDetails.phone`.
      *
      * Default: `true`
      */
     sendSmsReminder?: boolean | null;
     /** Whether this booking has a conflict with at least 1 other confirmed booking. */
     doubleBooked?: boolean | null;
-    /** Whether to return the single-service bookings that were marked as `PENDING`. */
+    /**
+     * Whether to return the single-service bookings that were marked as `PENDING`.
+     *
+     * Default: `false`
+     */
     returnFullEntity?: boolean;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * creation flow are changed. For example, whether the availability is checked
-     * before updating the booking.
+     * Information about whether specific procedures of the standard Wix Bookings creation flow are changed.
+     * For example, whether Wix Bookings checks availability before updating the booking.
      */
     flowControlSettings?: MarkBookingAsPendingFlowControlSettings;
 }
@@ -2806,8 +2833,7 @@ interface BookingInfo {
     bookingId?: string | null;
     /**
      * Revision number, which increments by 1 each time the booking is updated.
-     * To prevent conflicting changes, the current revision must be specified when
-     * managing the booking.
+     * To prevent conflicting changes, the current revision must be specified when managing the booking.
      */
     revision?: string | null;
     /** Payment status to set for the single-service booking. */
@@ -2825,14 +2851,11 @@ interface ConfirmMultiServiceBookingRequest {
     multiServiceBookingId: string | null;
     /** Information about the single-service bookings to confirm. */
     confirmBookingsInfo?: BookingInfo[];
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Whether to send an SMS reminder to the customer 24 hours before the
-     * session starts. The phone number is taken from `contactDetails.phone`.
+     * Whether to send an SMS reminder to the customer 24 hours before the session starts.
+     * Wix Bookings takes the phone number from `contactDetails.phone`.
      *
      * Default: `true`
      */
@@ -2842,36 +2865,32 @@ interface ConfirmMultiServiceBookingRequest {
     /** Whether to return the confirmed single-service bookings. */
     returnFullEntity?: boolean;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * confirmation flow are changed. For example, whether the availability is
-     * checked before confirming the booking.
+     * Information about whether specific procedures of the standard Wix Bookings confirmation flow are changed.
+     * For example, whether Wix Bookings checks availability before confirming the booking.
      */
     flowControlSettings?: ConfirmBookingFlowControlSettings;
 }
 interface ConfirmMultiServiceBookingResponse {
-    /** Confirmed multi service booking. */
+    /** Confirmed multi-service booking. */
     multiServiceBooking?: MultiServiceBooking;
 }
 interface DeclineMultiServiceBookingRequest {
     /**
-     * ID of the multi service booking to decline.
+     * ID of the multi-service booking to decline.
      * @format GUID
      */
     multiServiceBookingId: string | null;
     /** Information about the single-service bookings to decline. */
     declineBookingsInfo?: BookingInfo[];
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /** Whether this booking has a conflict with at least 1 other confirmed booking. */
     doubleBooked?: boolean | null;
     /** Whether to return the declined single-service bookings. */
     returnFullEntity?: boolean;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * declining flow are changed. For example, whether to issue a refund.
+     * Information about whether specific procedures of the standard Wix Bookings declining flow are changed.
+     * For example, whether to issue a refund upon cancellation.
      */
     flowControlSettings?: DeclineBookingFlowControlSettings;
 }
@@ -2891,11 +2910,10 @@ interface BulkGetMultiServiceBookingAllowedActionsRequest {
 interface BulkGetMultiServiceBookingAllowedActionsResponse {
     /**
      * Information about the multi-service bookings that were retrieved.
-     * Including their ID, index in the bulk request and whether they were
-     * successfully updated.
+     * Includes their ID, index in the bulk request and whether they were successfully processed.
      */
     results?: BulkCalculateAllowedActionsResult[];
-    /** Total number of successes and failures for Bulk Update Bookings. */
+    /** Total number of successes and failures for Bulk Get Multi Service Booking Allowed Actions. */
     bulkActionMetadata?: BulkActionMetadata;
 }
 interface GetMultiServiceBookingRequest {
@@ -2913,9 +2931,8 @@ interface GetMultiServiceBookingResponse {
 }
 interface MultiServiceBookingMetadata {
     /**
-     * Total number of `CONFIRMED` and `PENDING` single-service bookings belonging
-     * to the multi-service booking. The total includes the number of single-service
-     * bookings which couldn't be retrieved due to lack of permissions.
+     * Total number of `CONFIRMED` and `PENDING` single-service bookings belonging to the multi-service booking.
+     * The total includes the number of single-service bookings which couldn't be retrieved due to lack of permissions.
      */
     totalNumberOfScheduledBookings?: number | null;
 }
@@ -2930,19 +2947,22 @@ interface AddBookingsToMultiServiceBookingRequest {
      * @maxSize 8
      */
     bookings: BookingIdAndRevision[];
-    /** Whether to return the single-service bookings that were added to the multi-service booking. */
+    /**
+     * Whether to return the single-service bookings that were added to the multi-service booking.
+     *
+     * Default: `false`
+     */
     returnFullEntity?: boolean;
 }
 interface BookingIdAndRevision {
     /**
-     * ID of the booking.
+     * ID of the single-service booking.
      * @format GUID
      */
     bookingId?: string | null;
     /**
      * Revision number, which increments by 1 each time the booking is updated.
-     * To prevent conflicting changes, the current revision must be specified when
-     * managing the booking.
+     * To prevent conflicting changes, the current revision must be specified when managing the booking.
      */
     revision?: string | null;
 }
@@ -2961,7 +2981,11 @@ interface RemoveBookingsFromMultiServiceBookingRequest {
      * @maxSize 8
      */
     bookings?: BookingIdAndRevision[];
-    /** Whether to return the single-service bookings. */
+    /**
+     * Whether to return the single-service bookings.
+     *
+     * Default: `false`
+     */
     returnFullEntity?: boolean;
 }
 interface RemoveBookingsFromMultiServiceBookingResponse {
@@ -3828,16 +3852,16 @@ interface BulkConfirmOrDeclineBookingOptions {
  *
  * For appointment-based services, specify the relevant `slot` in
  * `bookedEntity.slot`. We recommend specifying the complete
- * `availabilityEntries.slot` returned in *Query Availability*
+ * `availabilityEntries.slot` returned in Query Availability
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/availability-calendar/query-availability) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/availability-calendar/query-availability))
  * in your call's request to avoid failed calls due to unavailability.
  *
  * ## Class session booking
  *
- * For class services, specify the relevant *event ID*
+ * For class services, specify the relevant event ID
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/calendar/events/introduction) | [REST](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction))
  * as `bookedEntity.slot.eventId`.
- * We recommend retrieving the event ID from *Query Availability's*
+ * We recommend retrieving the event ID from Query Availability's
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/availability-calendar/query-availability) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/availability-calendar/query-availability))
  * `availabilityEntries.slot.eventId` to avoid failed calls due to unavailability.
  * Specifying an event ID leads to automatic calculations of `slot.startDate`, `slot.endDate`,
@@ -3892,12 +3916,12 @@ interface BulkConfirmOrDeclineBookingOptions {
  * _eCommerce checkout_
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/orders/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction)),
  * Wix Bookings automatically syncs the booking's payment status from
- * the corresponding *eCommerce order*
+ * the corresponding eCommerce order
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction)).
  *
  * If a booking doesn't have a corresponding eCommerce order, for example, since
  * the customer didn't use the eCommerce checkout, you can update the booking's
- * payment status with *Confirm Or Decline Booking*
+ * payment status with Confirm Or Decline Booking
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings/confirm-or-decline-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking)).
  *
  * ## Booking form data
@@ -3972,7 +3996,7 @@ interface CreateBookingOptions {
  * Creates up to 8 bookings.
  *
  *
- * See *Create Booking*
+ * See Create Booking
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings/create-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/create-booking))
  * for more information.
  *
@@ -4016,7 +4040,7 @@ interface BulkCreateBookingOptions {
  * ## Appointment sessions
  *
  * For appointments, the old session is removed from the business calendar
- * while a new session is added. We recommend calling *Query Availability*
+ * while a new session is added. We recommend calling Query Availability
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/availability-calendar/query-availability) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/availability-calendar/query-availability))
  * first and specifying the entire retrieved `slot`.
  *
@@ -4024,7 +4048,7 @@ interface BulkCreateBookingOptions {
  *
  * For classes, the new session must be an existing session belonging to the
  * same class. We recommend retrieving `availabilityEntries.slot.eventId`
- * from *Query Availability*
+ * from Query Availability
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/availability-calendar/query-availability) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/availability-calendar/query-availability))
  * to avoid failed Reschedule Booking calls due to unavailability. Specify
  * only `slot.eventId` instead of the entire `slot` object.
@@ -4122,24 +4146,22 @@ interface RescheduleBookingOptionsParticipantsInfoOneOf {
     participantsChoices?: ParticipantChoices;
 }
 /**
- * Updates the booking status to `CONFIRMED` and updates the relevant session's
- * `participants.approvalStatus` to `APPROVED` without checking whether the relevant
- * slot or schedule is still available.
+ * Updates the booking status to `CONFIRMED` without checking whether the relevant slot or schedule is still available.
+ *
  *
  * ## eCommerce checkout restriction
  *
  * Call this method only when using a custom checkout page. Don't
- * call it when using a *Wix eCommerce checkout*
+ * call it when using a Wix eCommerce checkout
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/orders/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction)).
  * In such cases, Wix automatically updates the booking status based on
- * the `paymentStatus` of the corresponding *Wix eCommerce order*
+ * the `paymentStatus` of the corresponding Wix eCommerce order
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction)).
  *
  * ## When to call Confirm Or Decline Booking instead
  *
- * Confirm Booking doesn't check whether a slot or schedule is still available. For
- * these checks you can call *Confirm or Decline Booking*
- * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings/confirm-or-decline-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking)).
+ * Confirm Booking doesn't check whether a slot or schedule is still available.
+ * For these checks, call Confirm or Decline Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings/confirm-or-decline-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking)) instead.
  *
  * ## Original status validation
  *
@@ -4266,16 +4288,16 @@ interface UpdateExtendedFieldsOptions {
  * ## eCommerce checkout restriction
  *
  * Call this method only when using a custom checkout page. Don't
- * call it when using a *Wix eCommerce checkout*
+ * call it when using a Wix eCommerce checkout
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/orders/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction)).
  * In such cases, Wix automatically updates the booking status based on
- * the `paymentStatus` of the corresponding *Wix eCommerce order*
+ * the `paymentStatus` of the corresponding Wix eCommerce order
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction)).
  *
  * ## When to call Confirm Or Decline Booking instead
  *
  * The method doesn't check whether a slot or schedule is still available. For
- * these checks you can call *Confirm or Decline Booking*
+ * these checks you can call Confirm or Decline Booking
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings/confirm-or-decline-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking)).
  *
  * ## Original status validation
@@ -4421,7 +4443,7 @@ interface CancelBookingOptions {
  *
  * You must specify either `participantsChoices` or `totalParticipants`.
  * The call fails if the specified `participantsChoices` aren't among the
- * supported *service options and variants*
+ * supported service options and variants
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/service-options-and-variants/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction)).
  * @param bookingId - ID of the booking to update the number of participants for.
  * @public
@@ -4469,11 +4491,34 @@ interface UpdateNumberOfParticipantsOptionsParticipantsInfoOneOf {
     participantsChoices?: ParticipantChoices;
 }
 /**
- * Creates a multi-service booking.
+ * Creates a multi-service booking and all included single-service bookings simultaneously.
+ *
+ *
+ * ## When to call this method
+ *
+ * Create sequential appointments where customers book related services together. For adding existing single-service bookings to an existing multi-service booking, call Add Bookings to Multi Service Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/add-bookings-to-multi-service-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/add-bookings-to-multi-service-booking)) instead.
+ *
+ * ## Requirements and behavior
+ *
+ * __Package constraints__: Multi-service bookings support 2-8 appointment-based single-service bookings only (course and class bookings aren't supported). All single-service bookings must be at the same location with sequential scheduling and no gaps between appointments.
+ *
+ * __Timing specification__: You must provide complete `slot` details (`scheduleId`, `startDate`, `endDate`) for each single-service booking. Wix Bookings validates sequential timing but doesn't auto-calculate it.
+ *
+ * __Package pricing__: The total price equals the sum of individual services. Wix Bookings automatically syncs the payment status from the corresponding Wix eCommerce order ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecommerce/orders/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction)) if the customer paid via an eCommerce checkout ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecommerce/checkout/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction)).
  *
+ * __Package notifications__: Customers receive 1 unified notification for the entire multi-service booking. Wix Bookings doesn't send notifications for the package's individual single-service bookings.
  *
- * See Create Booking for more information.
- * @param bookings - Single-service bookings to combine in a multi-service booking.
+ * ## Related methods
+ *
+ * Verify availability first with List Multi Service Availability Time Slots ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-reader-v2/list-multi-service-availability-time-slots) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-reader-v2/list-multi-service-availability-time-slots)).
+ *
+ * See Create Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/create-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/create-booking)) for more details about constraints and effects of creating single-service bookings.
+ * @param bookings - Between 2 to 8 new single-service booking specifications to create and combine in a multi-service booking.
+ *
+ * Each single-service booking specification must include `slot` details (`scheduleId`, `startDate`, and `endDate`).
+ * Specify contact details, number of participants, and any additional fields as needed.
+ *
+ * For sequential bookings, ensure the timing allows services to be scheduled back-to-back.
  * @public
  * @documentationMaturity preview
  * @requiredField bookings
@@ -4496,38 +4541,39 @@ declare function createMultiServiceBooking(bookings: NonNullablePaths<Booking, `
     __applicationErrorsType?: CreateMultiServiceBookingApplicationErrors;
 }>;
 interface CreateMultiServiceBookingOptions {
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Whether to send an SMS reminder to the customer 24 hours before the
-     * session starts. The phone number is taken from `contactDetails.phone`.
+     * Whether to send an SMS reminder to the customer 24 hours before the session starts.
+     * Wix Bookings takes the phone number from `contactDetails.phone`.
      *
      * Default: `true`
      */
     sendSmsReminder?: boolean | null;
     /**
      * Whether to ignore specific standard procedures of the Wix Bookings flow.
-     * For example, whether to check availability before updating the status.
+     * For example, whether to skip checking availability before updating the status.
      */
     flowControlSettings?: CreateBookingFlowControlSettings;
     /** Whether to return the created single-service bookings. */
     returnFullEntity?: boolean;
-    /** Multi service booking type. */
+    /**
+     * Multi-service booking type.
+     *
+     * Currently only `SEQUENTIAL_BOOKINGS` is supported.
+     */
     multiServiceBookingType?: MultiServiceBookingTypeWithLiterals;
 }
 /**
- * Reschedules a multi-service booking.
+ * Reschedules a multi-service booking by changing the timing for all or specific single-service bookings in the package.
  *
  *
- * The call fails if at least 1 individual booking can't be rescheduled due
- * the service being unavailable or a rescheduling policy violation.
+ * This method reschedules single-service bookings within the multi-service booking while maintaining sequential order. You must specify exact new timing for each service to ensure they remain back-to-back with no gaps or overlaps.
  *
+ * This method fails if it can't reschedule at least 1 single-service booking. You must provide the current revision number for each single-service booking you're rescheduling to prevent conflicting changes.
  *
- * See Reschedule Booking for more information.
- * @param multiServiceBookingId - ID of the multi service booking to reschedule.
+ * See Reschedule Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/reschedule-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/reschedule-booking)) for single-service booking rescheduling details.
+ * @param multiServiceBookingId - ID of the multi-service booking to reschedule.
  * @param rescheduleBookingsInfo - Information about the single-service bookings to reschedule.
  * @public
  * @documentationMaturity preview
@@ -4547,27 +4593,29 @@ declare function rescheduleMultiServiceBooking(multiServiceBookingId: string, re
     __applicationErrorsType?: RescheduleMultiServiceBookingApplicationErrors;
 }>;
 interface RescheduleMultiServiceBookingOptions {
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * rescheduling flow are changed. For example, whether the availability of
-     * the new slot is checked before rescheduling the booking or if you can
-     * reschedule the booking even though the rescheduling policy doesn't allow it.
+     * Information about whether specific procedures of the standard Wix Bookings rescheduling flow are changed.
+     * For example, whether the availability of the new slot is checked before rescheduling the booking or if the customer can reschedule the booking even though the service's rescheduling policy doesn't allow it.
      */
     flowControlSettings?: RescheduleBookingFlowControlSettings;
     /** Whether to return the rescheduled bookings entities. */
     returnFullEntity?: boolean;
 }
 /**
- * Retrieves a multi-service booking's availability.
+ * Checks if the business can still accommodate an existing multi-service booking and returns overall bookability status, capacity details, and policy violations.
  *
  *
- * Use List Multi Service Availability Time Slots to check availability for a
- * `SEQUENTIAL_BOOKINGS` multi-service booking.
+ * Wix Bookings considers:
+ * - The relevant services' booking policies ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/booking-policies/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/policies/booking-policies/introduction)).
+ * - The availability of all required resources ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/resources/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/introduction)).
+ *
+ * Call this method to check if an existing multi-service booking is still valid after business configuration changes.
+ * For example, staff changes, policy updates, or capacity modifications.
+ *
+ * For checking availability before creating new multi-service bookings, call List Multi Service Availability Time Slots
+ * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/time-slots/multi-service-availability-time-slots/list-multi-service-availability-time-slots) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/time-slots-v2/list-multi-service-availability-time-slots)) instead.
  * @param multiServiceBookingId - ID of the multi-service booking to retrieve.
  * @public
  * @documentationMaturity preview
@@ -4581,7 +4629,13 @@ declare function getMultiServiceBookingAvailability(multiServiceBookingId: strin
     __applicationErrorsType?: GetMultiServiceBookingAvailabilityApplicationErrors;
 }>;
 /**
- * Cancels a multi-service booking and thus all its individual bookings.
+ * Cancels a multi-service booking and all its associated single-service bookings.
+ *
+ *
+ * Cancels the entire multi-service booking, updating the status of all single-service bookings to `CANCELED`.
+ * The call fails if all single-service bookings are already canceled or declined.
+ *
+ * See Cancel Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/cancel-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/cancel-booking)) for single-service booking cancellation details.
  * @param multiServiceBookingId - ID of the multi-service booking to cancel.
  * @public
  * @documentationMaturity preview
@@ -4597,30 +4651,39 @@ declare function cancelMultiServiceBooking(multiServiceBookingId: string, option
     __applicationErrorsType?: CancelMultiServiceBookingApplicationErrors;
 }>;
 interface CancelMultiServiceBookingOptions {
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * cancellation flow are changed. For example, whether you can cancel
-     * a booking even though the cancellation policy doesn't allow it or whether
-     * to issue a refund.
+     * Information about whether specific procedures of the standard Wix Bookings cancellation flow are changed.
+     * For example, whether the customer can cancel the booking even though the service's cancellation policy doesn't allow it or whether to issue a refund upon cancellation.
      */
     flowControlSettings?: CancelBookingFlowControlSettings;
     /** Whether to return the canceled single-service bookings. */
     returnFullEntity?: boolean;
 }
 /**
- * Updates the status of a multi-service booking to `PENDING`.
+ * Updates the status for all single-service bookings in a multi-service booking to `PENDING`.
+ *
+ *
+ * Call this method for multi-service bookings requiring manual business approval before confirmation.
  *
+ * ## Status requirements
  *
- * Also updates the status of each of individual bookings within the multi-service booking to `PENDING`.
+ * - __Original status__: All single-service bookings must have `CREATED` status.
+ * - __Target status__: All bookings move to `PENDING` together (all-or-nothing operation).
  *
- * The call fails if the status for at least a single individual booking can't be updated.
+ * ## Checkout restrictions
  *
- * See Mark Booking as Pending for more information.
+ * Only call this method if the customer paid via a custom checkout. For Wix eCommerce checkouts,
+ * Wix Bookings automatically manages the bookings' statuses based on payment processing.
+ *
+ * ## Additional updates
+ *
+ * - __Payment status__: Updates if you specify a new `markAsPendingBookingsInfo.paymentStatus`.
+ * - __Customer notifications__: Send messages using `participantNotification`.
+ * - __Revision control__: Requires current revision numbers for all single-service bookings.
+ *
+ * See Mark Booking as Pending ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/mark-booking-as-pending) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/mark-booking-as-pending)) for more details about marking single-service bookings as pending.
  * @param multiServiceBookingId - ID of the multi-service booking to mark as `PENDING`.
  * @public
  * @documentationMaturity preview
@@ -4637,38 +4700,52 @@ declare function markMultiServiceBookingAsPending(multiServiceBookingId: string,
 interface MarkMultiServiceBookingAsPendingOptions {
     /** Information about the single-service bookings to mark as `PENDING`. */
     markAsPendingBookingsInfo?: BookingInfo[];
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Whether to send an SMS reminder to the customer 24 hours before the
-     * session starts. The phone number is taken from `contactDetails.phone`.
+     * Whether to send an SMS reminder to the customer 24 hours before the session starts.
+     * Wix Bookings takes the phone number from `contactDetails.phone`.
      *
      * Default: `true`
      */
     sendSmsReminder?: boolean | null;
     /** Whether this booking has a conflict with at least 1 other confirmed booking. */
     doubleBooked?: boolean | null;
-    /** Whether to return the single-service bookings that were marked as `PENDING`. */
+    /**
+     * Whether to return the single-service bookings that were marked as `PENDING`.
+     *
+     * Default: `false`
+     */
     returnFullEntity?: boolean;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * creation flow are changed. For example, whether the availability is checked
-     * before updating the booking.
+     * Information about whether specific procedures of the standard Wix Bookings creation flow are changed.
+     * For example, whether Wix Bookings checks availability before updating the booking.
      */
     flowControlSettings?: MarkBookingAsPendingFlowControlSettings;
 }
 /**
- * Updates the status of a multi-service booking to `CONFIRMED`.
+ * Updates the status for all single-service bookings in a multi-service booking to `CONFIRMED`.
  *
  *
- * Also updates the status of each of individual bookings within the multi-service booking to `CONFIRMED`.
+ * Call this method for multi-service bookings requiring manual business approval.
  *
- * The call fails if the status for at least a single individual booking can't be updated.
+ * ## Status requirements
  *
- * See Confirm Booking for more information.
+ * - __Original status__: All single-service bookings must have `PENDING`, `CREATED`, or `WAITING_LIST` status.
+ * - __Target status__: All bookings move to `CONFIRMED` together (all-or-nothing operation).
+ *
+ * ## Checkout restrictions
+ *
+ * Only call this method if the customer paid via a custom checkout. For Wix eCommerce checkouts,
+ * Wix Bookings automatically manages the bookings' statuses based on payment processing.
+ *
+ * ## Additional updates
+ *
+ * - __Payment status__: Updates if you specify a new `confirmBookingsInfo.paymentStatus`.
+ * - __Customer notifications__: Send messages using `participantNotification`.
+ * - __Revision control__: Requires current revision numbers for all single-service bookings.
+ *
+ * See Confirm Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/confirm-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-booking)) for more details about confirming single-service bookings.
  * @param multiServiceBookingId - ID of the multi-service booking to confirm its related bookings.
  * @public
  * @documentationMaturity preview
@@ -4685,14 +4762,11 @@ declare function confirmMultiServiceBooking(multiServiceBookingId: string, optio
 interface ConfirmMultiServiceBookingOptions {
     /** Information about the single-service bookings to confirm. */
     confirmBookingsInfo?: BookingInfo[];
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /**
-     * Whether to send an SMS reminder to the customer 24 hours before the
-     * session starts. The phone number is taken from `contactDetails.phone`.
+     * Whether to send an SMS reminder to the customer 24 hours before the session starts.
+     * Wix Bookings takes the phone number from `contactDetails.phone`.
      *
      * Default: `true`
      */
@@ -4702,22 +4776,35 @@ interface ConfirmMultiServiceBookingOptions {
     /** Whether to return the confirmed single-service bookings. */
     returnFullEntity?: boolean;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * confirmation flow are changed. For example, whether the availability is
-     * checked before confirming the booking.
+     * Information about whether specific procedures of the standard Wix Bookings confirmation flow are changed.
+     * For example, whether Wix Bookings checks availability before confirming the booking.
      */
     flowControlSettings?: ConfirmBookingFlowControlSettings;
 }
 /**
- * Updates the status of a multi-service booking to `DECLINED`.
+ * Updates the status for all single-service bookings in a multi-service booking to `DECLINED`.
+ *
+ *
+ * Call this method to reject multi-service bookings that can't be accommodated or don't meet business requirements.
  *
+ * ## Status requirements
  *
- * Also updates the status of each of individual bookings within the multi-service booking to `DECLINED`.
+ * - __Original status__: All single-service bookings must have `PENDING`, `CREATED`, or `WAITING_LIST` status.
+ * - __Target status__: All bookings move to `DECLINED` together (all-or-nothing operation).
  *
- * The call fails if the status for at least a single individual booking can't be updated.
+ * ## Checkout restrictions
  *
- * See Decline Booking for more information.
- * @param multiServiceBookingId - ID of the multi service booking to decline.
+ * Only call this method if the customer paid via a custom checkout. For Wix eCommerce checkouts,
+ * Wix Bookings automatically manages the bookings' statuses based on payment processing.
+ *
+ * ## Additional updates
+ *
+ * - __Payment status__: Updates if you specify a new `declineBookingsInfo.paymentStatus`.
+ * - __Customer notifications__: Send messages using `participantNotification`.
+ * - __Revision control__: Requires current revision numbers for all single-service bookings.
+ *
+ * Refer to Decline Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/decline-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/decline-booking)) for more details about declining single-service bookings.
+ * @param multiServiceBookingId - ID of the multi-service booking to decline.
  * @public
  * @documentationMaturity preview
  * @requiredField multiServiceBookingId
@@ -4733,23 +4820,34 @@ declare function declineMultiServiceBooking(multiServiceBookingId: string, optio
 interface DeclineMultiServiceBookingOptions {
     /** Information about the single-service bookings to decline. */
     declineBookingsInfo?: BookingInfo[];
-    /**
-     * Information about whether to notify the customer and
-     * the message to send.
-     */
+    /** Information about whether to notify the customer and the message to send. */
     participantNotification?: ParticipantNotification;
     /** Whether this booking has a conflict with at least 1 other confirmed booking. */
     doubleBooked?: boolean | null;
     /** Whether to return the declined single-service bookings. */
     returnFullEntity?: boolean;
     /**
-     * Information about whether specific procedures of the standard Wix Bookings
-     * declining flow are changed. For example, whether to issue a refund.
+     * Information about whether specific procedures of the standard Wix Bookings declining flow are changed.
+     * For example, whether to issue a refund upon cancellation.
      */
     flowControlSettings?: DeclineBookingFlowControlSettings;
 }
 /**
- * Retrieves the allowed actions for a list of multi-service bookings.
+ * Retrieves information about which actions the customer can perform for up to 50 multi-service bookings.
+ *
+ *
+ * For each multi-service booking, the response indicates which actions are currently allowed:
+ * - `cancel`: Whether the customer can cancel the multi-service booking.
+ * - `reschedule`: Whether the customer can adjust the multi-service booking's timing.
+ *
+ * Bear the following considerations in mind when calling this method:
+ *
+ * __Real-time validation__: Wix Bookings calculates allowed actions based on current multi-service booking status, booking policies ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/booking-policies/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/policies/booking-policies/introduction)), and available resources ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/resources/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/resources-v2/introduction)) at the time of the call.
+ *
+ * __Permission context__: Depending on the permissions of the calling [identity](https://dev.wix.com/build-apps/develop-your-app/about-identities), you may see different allowed actions for the same multi-service booking. For example, if the identity has permissions to read only part of the multi-service booking, the response indicates which single-service bookings the identity can read.
+ *
+ * __Status dependencies__: Allowed actions change as bookings progress through their lifecycle (`CREATED` → `PENDING` → `CONFIRMED`/`DECLINED` → `CANCELED`).
+ * Bookings can skip `PENDING` and move directly from `CREATED` to `CONFIRMED`/`DECLINED` based on service configuration.
  * @param multiServiceBookingIds - IDs of the multi-service bookings to retrieve allowed actions for.
  * @public
  * @documentationMaturity preview
@@ -4761,13 +4859,15 @@ interface DeclineMultiServiceBookingOptions {
  */
 declare function bulkGetMultiServiceBookingAllowedActions(multiServiceBookingIds: string[]): Promise<NonNullablePaths<BulkGetMultiServiceBookingAllowedActionsResponse, `results` | `results.${number}.itemMetadata.originalIndex` | `results.${number}.itemMetadata.success` | `results.${number}.itemMetadata.error.code` | `results.${number}.itemMetadata.error.description` | `results.${number}.item.cancel` | `results.${number}.item.reschedule` | `bulkActionMetadata.totalSuccesses` | `bulkActionMetadata.totalFailures` | `bulkActionMetadata.undetailedFailures`>>;
 /**
- * Retrieves all single-service bookings belonging to a multi-service booking.
+ * Retrieves a multi-service booking and all its associated single-service bookings.
  *
  *
- * If you call as an [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities)
- * who has permissions to read only part of the bookings,
- * only the permitted bookings are retrieved. The returned total number of
- * bookings includes also the bookings for which you don't have permissions.
+ * Returns the complete multi-service booking information including its ID, associated single-service bookings, and the total number of scheduled single-service bookings.
+ *
+ * If you call on behalf of an [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities) with permissions to read only part of the multi-service booking, only the permitted single-service bookings are retrieved.
+ * The returned total number includes single-service bookings for which you don't have permissions.
+ *
+ * See Query Extended Bookings ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/extended-bookings/query-extended-bookings) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-reader-v2/query-extended-bookings)) for details about retrieving individual single-service bookings and additional metadata.
  * @param multiServiceBookingId - ID of the multi-service booking.
  * @public
  * @documentationMaturity preview
@@ -4781,11 +4881,24 @@ declare function getMultiServiceBooking(multiServiceBookingId: string): Promise<
     [P in BookingNonNullablePaths]: `bookings.${number}.booking.${P}`;
 }[BookingNonNullablePaths]>>;
 /**
- * Adds a list of single-service bookings to a multi-service booking.
+ * Expands an existing multi-service booking by adding existing single-service bookings to the package.
+ *
+ *
+ * ## When to call this method
+ *
+ * Call this method to add 1 or more existing single-service bookings to an existing multi-service booking.
+ * For creating a new multi-service booking with new single-service bookings, call Create Multi Service Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/create-multi-service-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/create-multi-service-booking)) instead.
+ *
+ * ## Package integration
+ *
+ * The timing of the single-service bookings to add must be compatible with the multi-service booking's sequential schedule to ensure no gaps or overlaps between services in the updated package.
  *
+ * ## Requirements and limitations
  *
- * The call fails, if at least 1 of the specified booking is already part of a
- * multi-service booking.
+ * - __Maximum capacity__: The total number of single-service bookings can't exceed 8.
+ * - __Booking eligibility__: You can add only independent single-service bookings that aren't part of another multi-service booking.
+ * - __Status compatibility__: Added bookings must have compatible status with the target multi-service booking.
+ * - __Revision control__: You must provide current revision numbers for all single-service bookings to add.
  * @param multiServiceBookingId - ID of the multi-service booking.
  * @public
  * @documentationMaturity preview
@@ -4807,20 +4920,34 @@ interface AddBookingsToMultiServiceBookingOptions {
      * @maxSize 8
      */
     bookings: BookingIdAndRevision[];
-    /** Whether to return the single-service bookings that were added to the multi-service booking. */
+    /**
+     * Whether to return the single-service bookings that were added to the multi-service booking.
+     *
+     * Default: `false`
+     */
     returnFullEntity?: boolean;
 }
 /**
- * Removes single-service bookings from a multi-service booking and returns the
- * removed bookings.
+ * Removes single-service bookings from a multi-service booking and converts them to independent single-service bookings.
+ *
+ *
+ * ## Removal options
+ *
+ * __Remove all permitted bookings__: If you specify an empty `bookings` array, all single-service bookings for which the call's [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities) has read permissions are removed from the multi-service booking.
  *
+ * __Selective removal__: Specify single-service booking IDs and revisions to remove only specific single-service bookings from the package.
  *
- * If you specify an empty `bookings` array, all single-service bookings for which
- * the call's [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities)
- * has read permissions are removed from the multi-service booking.
+ * __Sequential scheduling__: To maintain sequential scheduling, remove only first or last single-service bookings. For middle bookings, first reschedule all relevant single-service bookings to eliminate gaps. To do so, call Reschedule Multi Service Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-writer-v2/reschedule-multi-service-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/multi-service-bookings/reschedule-multi-service-booking)) before removing the unwanted bookings.
  *
- * If the call would create a multi-service booking including only 1 single-service
- * booking, the multi-service booking is also deleted.
+ * ## Removal behavior
+ *
+ * __Independent bookings__: Removed single-service bookings become independent bookings.
+ * You can manage them using single-service booking methods.
+ *
+ * __Automatic cleanup__: Multi-service bookings must contain at least 2 services.
+ * If removal results in only 1 remaining single-service booking for the multi-service booking, the entire multi-service booking is deleted and the remaining single-service booking becomes a standalone booking.
+ *
+ * __Revision control__: Specify current revision numbers to prevent conflicting modifications during the removal process.
  * @param multiServiceBookingId - ID of the multi-service booking.
  * @public
  * @documentationMaturity preview
@@ -4840,7 +4967,11 @@ interface RemoveBookingsFromMultiServiceBookingOptions {
      * @maxSize 8
      */
     bookings?: BookingIdAndRevision[];
-    /** Whether to return the single-service bookings. */
+    /**
+     * Whether to return the single-service bookings.
+     *
+     * Default: `false`
+     */
     returnFullEntity?: boolean;
 }