@wix/auto_sdk_bookings_bookings 1.0.40 → 1.0.41

package/build/cjs/index.d.ts

@@ -81,16 +81,16 @@ interface CreateBookingSignature {
      *
      * 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`,
@@ -145,12 +145,12 @@ interface CreateBookingSignature {
      * _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
@@ -202,7 +202,7 @@ interface BulkCreateBookingSignature {
      * 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.
      *
@@ -236,7 +236,7 @@ interface RescheduleBookingSignature {
      * ## 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`.
      *
@@ -244,7 +244,7 @@ interface RescheduleBookingSignature {
      *
      * 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.
@@ -296,24 +296,22 @@ interface RescheduleBookingSignature {
 declare function confirmBooking$1(httpClient: HttpClient): ConfirmBookingSignature;
 interface ConfirmBookingSignature {
     /**
-     * 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
      *
@@ -403,16 +401,16 @@ interface DeclineBookingSignature {
      * ## 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
@@ -515,7 +513,7 @@ interface UpdateNumberOfParticipantsSignature {
      *
      * 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 - ID of the booking to update the number of participants for.
      */
@@ -528,11 +526,34 @@ interface UpdateNumberOfParticipantsSignature {
 declare function createMultiServiceBooking$1(httpClient: HttpClient): CreateMultiServiceBookingSignature;
 interface CreateMultiServiceBookingSignature {
     /**
-     * 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. 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 - 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 - 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.
      */
     (bookings: NonNullablePaths<Booking, `additionalFields.${number}._id` | `bookedEntity` | `bookedEntity.slot` | `bookedEntity.slot.endDate` | `bookedEntity.slot.location.locationType` | `bookedEntity.slot.scheduleId` | `bookedEntity.slot.startDate`>[], options?: CreateMultiServiceBookingOptions): Promise<NonNullablePaths<CreateMultiServiceBookingResponse, `multiServiceBooking.bookings` | {
         [P in BookingNonNullablePaths]: `multiServiceBooking.bookings.${number}.booking.${P}`;
@@ -543,15 +564,15 @@ interface CreateMultiServiceBookingSignature {
 declare function rescheduleMultiServiceBooking$1(httpClient: HttpClient): RescheduleMultiServiceBookingSignature;
 interface RescheduleMultiServiceBookingSignature {
     /**
-     * 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 booking you're rescheduling to prevent conflicting changes.
      *
-     * See Reschedule Booking for more information.
-     * @param - 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 - ID of the multi-service booking to reschedule.
      * @param - Information about the single-service bookings to reschedule.
      */
     (multiServiceBookingId: string, rescheduleBookingsInfo: NonNullablePaths<RescheduleBookingInfo, `bookingId` | `revision` | `slot`>[], options?: RescheduleMultiServiceBookingOptions): Promise<NonNullablePaths<RescheduleMultiServiceBookingResponse, `multiServiceBooking.bookings` | {
@@ -563,11 +584,21 @@ interface RescheduleMultiServiceBookingSignature {
 declare function getMultiServiceBookingAvailability$1(httpClient: HttpClient): GetMultiServiceBookingAvailabilitySignature;
 interface GetMultiServiceBookingAvailabilitySignature {
     /**
-     * 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.
+     *
+     *
+     * 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)).
+     *
+     * ## When to call this method
+     *
+     * Check if an existing multi-service booking is still valid after business configuration changes. For example, staff changes, policy updates, or capacity modifications.
      *
+     * ## When to call List Multi Service Availability Time Slots instead
      *
-     * Use List Multi Service Availability Time Slots to check availability for a
-     * `SEQUENTIAL_BOOKINGS` multi-service booking.
+     * 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/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)) instead.
      * @param - ID of the multi-service booking to retrieve.
      */
     (multiServiceBookingId: string): Promise<NonNullablePaths<GetMultiServiceBookingAvailabilityResponse, `bookable` | `multiServiceBookingInfo`> & {
@@ -577,7 +608,13 @@ interface GetMultiServiceBookingAvailabilitySignature {
 declare function cancelMultiServiceBooking$1(httpClient: HttpClient): CancelMultiServiceBookingSignature;
 interface CancelMultiServiceBookingSignature {
     /**
-     * Cancels a multi-service booking and thus all its individual bookings.
+     * Cancels a multi-service booking and all its 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 - ID of the multi-service booking to cancel.
      */
     (multiServiceBookingId: string, options?: CancelMultiServiceBookingOptions): Promise<NonNullablePaths<CancelMultiServiceBookingResponse, `multiServiceBooking.bookings` | {
@@ -589,14 +626,28 @@ interface CancelMultiServiceBookingSignature {
 declare function markMultiServiceBookingAsPending$1(httpClient: HttpClient): MarkMultiServiceBookingAsPendingSignature;
 interface MarkMultiServiceBookingAsPendingSignature {
     /**
-     * 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
+     *
+     * - **Original status**: All single-service bookings must have `CREATED` status.
+     * - **Target status**: All bookings move to `PENDING` together (all-or-nothing operation).
      *
+     * ## Checkout restrictions
      *
-     * Also updates the status of each of individual bookings within the multi-service booking to `PENDING`.
+     * 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.
      *
-     * The call fails if the status for at least a single individual booking can't be updated.
+     * ## Additional updates
      *
-     * See Mark Booking as Pending for more information.
+     * - **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 - ID of the multi-service booking to mark as `PENDING`.
      */
     (multiServiceBookingId: string, options?: MarkMultiServiceBookingAsPendingOptions): Promise<NonNullablePaths<MarkMultiServiceBookingAsPendingResponse, `multiServiceBooking.bookings` | {
@@ -608,14 +659,28 @@ interface MarkMultiServiceBookingAsPendingSignature {
 declare function confirmMultiServiceBooking$1(httpClient: HttpClient): ConfirmMultiServiceBookingSignature;
 interface ConfirmMultiServiceBookingSignature {
     /**
-     * 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`.
+     *
+     *
+     * Call this method for multi-service bookings requiring manual business approval.
+     *
+     * ## Status requirements
      *
+     * - **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).
      *
-     * Also updates the status of each of individual bookings within the multi-service booking to `CONFIRMED`.
+     * ## Checkout restrictions
      *
-     * The call fails if the status for at least a single individual booking can't be updated.
+     * 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.
      *
-     * See Confirm Booking for more information.
+     * ## 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 - ID of the multi-service booking to confirm its related bookings.
      */
     (multiServiceBookingId: string, options?: ConfirmMultiServiceBookingOptions): Promise<NonNullablePaths<ConfirmMultiServiceBookingResponse, `multiServiceBooking.bookings` | {
@@ -627,15 +692,29 @@ interface ConfirmMultiServiceBookingSignature {
 declare function declineMultiServiceBooking$1(httpClient: HttpClient): DeclineMultiServiceBookingSignature;
 interface DeclineMultiServiceBookingSignature {
     /**
-     * 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 - 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 - ID of the multi-service booking to decline.
      */
     (multiServiceBookingId: string, options?: DeclineMultiServiceBookingOptions): Promise<NonNullablePaths<DeclineMultiServiceBookingResponse, `multiServiceBooking.bookings` | {
         [P in BookingNonNullablePaths]: `multiServiceBooking.bookings.${number}.booking.${P}`;
@@ -646,7 +725,21 @@ interface DeclineMultiServiceBookingSignature {
 declare function bulkGetMultiServiceBookingAllowedActions$1(httpClient: HttpClient): BulkGetMultiServiceBookingAllowedActionsSignature;
 interface BulkGetMultiServiceBookingAllowedActionsSignature {
     /**
-     * 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.
+     *
+     * ## Important considerations
+     *
+     * *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 - IDs of the multi-service bookings to retrieve allowed actions for.
      */
     (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`>>;
@@ -654,13 +747,15 @@ interface BulkGetMultiServiceBookingAllowedActionsSignature {
 declare function getMultiServiceBooking$1(httpClient: HttpClient): GetMultiServiceBookingSignature;
 interface GetMultiServiceBookingSignature {
     /**
-     * Retrieves all single-service bookings belonging to a multi-service booking.
+     * Retrieves a multi-service booking and all its associated single-service bookings.
+     *
+     *
+     * Returns the complete multi-service booking information including its ID, included single-service bookings, and the total number of scheduled 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 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.
      *
-     * 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.
+     * See Query Extended Bookings ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings-reader-v2/query-extended-bookings) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-reader-v2/query-extended-booking)) for details about retrieving individual single-service bookings and additional metadata.
      * @param - ID of the multi-service booking.
      * @returns Retrieved multi-service booking.
      */
@@ -671,11 +766,24 @@ interface GetMultiServiceBookingSignature {
 declare function addBookingsToMultiServiceBooking$1(httpClient: HttpClient): AddBookingsToMultiServiceBookingSignature;
 interface AddBookingsToMultiServiceBookingSignature {
     /**
-     * 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.
      *
-     * The call fails, if at least 1 of the specified booking is already part of a
-     * multi-service booking.
+     * ## Requirements and limitations
+     *
+     * - **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 - ID of the multi-service booking.
      */
     (multiServiceBookingId: string, options?: NonNullablePaths<AddBookingsToMultiServiceBookingOptions, `bookings` | `bookings.${number}.bookingId` | `bookings.${number}.revision`>): Promise<NonNullablePaths<AddBookingsToMultiServiceBookingResponse, `bookings` | {
@@ -687,16 +795,26 @@ interface AddBookingsToMultiServiceBookingSignature {
 declare function removeBookingsFromMultiServiceBooking$1(httpClient: HttpClient): RemoveBookingsFromMultiServiceBookingSignature;
 interface RemoveBookingsFromMultiServiceBookingSignature {
     /**
-     * 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.
+     *
+     * *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.
+     *
+     * ## Removal behavior
      *
+     * *Independent bookings**: Removed single-service bookings become independent bookings.
+     * You can manage them using single-service booking methods.
      *
-     * 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.
+     * *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.
      *
-     * If the call would create a multi-service booking including only 1 single-service
-     * booking, the multi-service booking is also deleted.
+     * *Revision control**: Specify current revision numbers to prevent conflicting modifications during the removal process.
      * @param - ID of the multi-service booking.
      */
     (multiServiceBookingId: string, options?: RemoveBookingsFromMultiServiceBookingOptions): Promise<NonNullablePaths<RemoveBookingsFromMultiServiceBookingResponse, `bookings` | {