@wix/auto_sdk_bookings_bookings 1.0.89 → 1.0.90

package/build/cjs/index.d.ts

@@ -1,46 +1,7 @@
 import { HttpClient, NonNullablePaths, EventDefinition, MaybeContext, BuildRESTFunction, BuildEventDefinition } from '@wix/sdk-types';
-import { GetAnonymousActionDetailsOptions, GetAnonymousActionDetailsResponse, CancelBookingAnonymouslyOptions, CancelBookingAnonymouslyResponse, V2Slot, RescheduleBookingAnonymouslyOptions, RescheduleBookingAnonymouslyResponse, GetBookingAnonymouslyResponse, ConfirmOrDeclineBookingOptions, ConfirmOrDeclineBookingResponse, ConfirmOrDeclineBookingApplicationErrors, BulkConfirmOrDeclineBookingRequestBookingDetails, BulkConfirmOrDeclineBookingOptions, BulkConfirmOrDeclineBookingResponse, BulkConfirmOrDeclineBookingApplicationErrors, Booking, CreateBookingOptions, CreateBookingResponse, CreateBookingApplicationErrors, CreateBookingInfo, BulkCreateBookingOptions, BulkCreateBookingResponse, BulkCreateBookingApplicationErrors, RescheduleBookingOptions, RescheduleBookingResponse, RescheduleBookingApplicationErrors, ConfirmBookingOptions, ConfirmBookingResponse, ConfirmBookingApplicationErrors, SetBookingSubmissionIdResponse, SetBookingSubmissionIdApplicationErrors, UpdateExtendedFieldsOptions, UpdateExtendedFieldsResponse, UpdateExtendedFieldsApplicationErrors, DeclineBookingOptions, DeclineBookingResponse, DeclineBookingApplicationErrors, CancelBookingOptions, CancelBookingResponse, CancelBookingApplicationErrors, UpdateNumberOfParticipantsOptions, UpdateNumberOfParticipantsResponse, UpdateNumberOfParticipantsApplicationErrors, MarkBookingAsPendingOptions, MarkBookingAsPendingResponse, MarkBookingAsPendingApplicationErrors, CreateMultiServiceBookingOptions, CreateMultiServiceBookingResponse, CreateMultiServiceBookingApplicationErrors, RescheduleBookingInfo, RescheduleMultiServiceBookingOptions, RescheduleMultiServiceBookingResponse, RescheduleMultiServiceBookingApplicationErrors, GetMultiServiceBookingAvailabilityResponse, GetMultiServiceBookingAvailabilityApplicationErrors, CancelMultiServiceBookingOptions, CancelMultiServiceBookingResponse, CancelMultiServiceBookingApplicationErrors, MarkMultiServiceBookingAsPendingOptions, MarkMultiServiceBookingAsPendingResponse, MarkMultiServiceBookingAsPendingApplicationErrors, ConfirmMultiServiceBookingOptions, ConfirmMultiServiceBookingResponse, ConfirmMultiServiceBookingApplicationErrors, DeclineMultiServiceBookingOptions, DeclineMultiServiceBookingResponse, DeclineMultiServiceBookingApplicationErrors, BulkGetMultiServiceBookingAllowedActionsResponse, MultiServiceBooking, AddBookingsToMultiServiceBookingOptions, AddBookingsToMultiServiceBookingResponse, AddBookingsToMultiServiceBookingApplicationErrors, RemoveBookingsFromMultiServiceBookingOptions, RemoveBookingsFromMultiServiceBookingResponse, RemoveBookingsFromMultiServiceBookingApplicationErrors, BookingCanceledEnvelope, BookingConfirmedEnvelope, BookingCreatedEnvelope, BookingDeclinedEnvelope, BookingNumberOfParticipantsUpdatedEnvelope, BookingRescheduledEnvelope, BookingUpdatedEnvelope } from './index.typings.js';
-export { ActionEvent, Actor, ActorWithLiterals, AddBookingsToMultiServiceBookingRequest, Address, AddressLocation, AddressStreetOneOf, AllowedActions, AllowedActionsAnonymously, AnonymousBookingUrls, ApplicationError, AvailableResources, BaseEventMetadata, BookedAddOn, BookedEntity, BookedEntityItemOneOf, BookedResource, BookedSchedule, BookedSlot, BookingCanceled, BookingChanged, BookingConfirmed, BookingDeclined, BookingDetails, BookingFormFilled, BookingIdAndRevision, BookingInfo, BookingMarkedAsPending, BookingParticipantsInfoOneOf, BookingPolicySettings, BookingPolicyViolations, BookingRescheduled, BookingRescheduledPreviousParticipantsInfoOneOf, BookingResult, BookingSource, BookingStatus, BookingStatusWithLiterals, BulkActionMetadata, BulkBookingResult, BulkCalculateAllowedActionsRequest, BulkCalculateAllowedActionsResponse, BulkCalculateAllowedActionsResult, BulkConfirmOrDeclineBookingRequest, BulkCreateBookingRequest, BulkGetMultiServiceBookingAllowedActionsRequest, BulkRescheduleBookingRequest, BulkRescheduleBookingRequestBooking, BulkRescheduleBookingResponse, BulkUpdateBookedScheduleRequest, BulkUpdateBookedScheduleResponse, BulkUpdateBookingRequest, BulkUpdateBookingResponse, CancelBookingAnonymouslyRequest, CancelBookingFlowControlSettings, CancelBookingRequest, CancelBookingRequestFlowControlSettings, CancelMultiServiceBookingRequest, Clash, CommonIdentificationData, CommonIdentificationDataIdOneOf, ConfirmBookingFlowControlSettings, ConfirmBookingRequest, ConfirmMultiServiceBookingRequest, ConfirmOrDeclineBookingRequest, ConfirmRequest, ConfirmResponse, ConsistentQueryBookingsRequest, ConsistentQueryBookingsResponse, ContactDetails, CountBookingsRequest, CountBookingsResponse, CreateBookingFlowControlSettings, CreateBookingRequest, CreateBookingRequestFlowControlSettings, CreateMultiServiceBookingRequest, CursorPaging, Cursors, CustomFormField, DeclineBookingFlowControlSettings, DeclineBookingRequest, DeclineMultiServiceBookingRequest, DomainEvent, DomainEventBodyOneOf, Duration, EntityCreatedEvent, EntityDeletedEvent, EntityUpdatedEvent, EventMetadata, ExtendedFields, FlowControlSettings, GetAnonymousActionDetailsRequest, GetBookingAnonymouslyRequest, GetMultiServiceBookingAvailabilityRequest, GetMultiServiceBookingAvailabilityResponseBookingInfo, GetMultiServiceBookingRequest, GetMultiServiceBookingResponse, GetScheduleAvailabilityRequest, GetScheduleAvailabilityResponse, GetSlotAvailabilityRequest, GetSlotAvailabilityResponse, IdentificationData, IdentificationDataIdOneOf, IdentificationDataIdentityType, IdentificationDataIdentityTypeWithLiterals, IdentityType, IdentityTypeWithLiterals, ItemMetadata, LegacyCreateBookingRequest, LegacyCreateBookingResponse, Location, LocationLocationType, LocationLocationTypeWithLiterals, LocationType, LocationTypeWithLiterals, MarkBookingAsPendingFlowControlSettings, MarkBookingAsPendingRequest, MarkMultiServiceBookingAsPendingRequest, MaskedBooking, MessageEnvelope, MigrationCheckIfClashesWithBlockedTimeRequest, MigrationCheckIfClashesWithBlockedTimeResponse, MsidAndBookingId, MultiServiceBookingInfo, MultiServiceBookingMetadata, MultiServiceBookingType, MultiServiceBookingTypeWithLiterals, NumberOfParticipantsUpdated, NumberOfParticipantsUpdatedPreviousParticipantsInfoOneOf, Paging, PagingMetadataV2, ParticipantChoices, ParticipantNotification, PaymentStatus, PaymentStatusWithLiterals, PhoneCall, Platform, PlatformWithLiterals, QueryBookingsRequest, QueryBookingsResponse, QueryV2, QueryV2PagingMethodOneOf, RemoveBookingsFromMultiServiceBookingRequest, RescheduleBookingAnonymouslyRequest, RescheduleBookingFlowControlSettings, RescheduleBookingInfoParticipantsInfoOneOf, RescheduleBookingOptionsParticipantsInfoOneOf, RescheduleBookingRequest, RescheduleBookingRequestFlowControlSettings, RescheduleBookingRequestParticipantsInfoOneOf, RescheduleMultiServiceBookingRequest, ResourceSelection, RestoreInfo, ScheduleAvailability, SelectedPaymentOption, SelectedPaymentOptionWithLiterals, SelectionMethod, SelectionMethodWithLiterals, ServiceChoice, ServiceChoiceChoiceOneOf, ServiceChoices, SetBookingFormAndSubmissionIdRequest, SetBookingFormAndSubmissionIdRequestCreatedByOneOf, SetBookingFormAndSubmissionIdResponse, SetBookingSessionIdRequest, SetBookingSessionIdResponse, SetBookingSubmissionIdRequest, Slot, SlotAvailability, SlotBookings, SlotLocation, SlotResource, SlotSlotResource, SortOrder, SortOrderWithLiterals, Sorting, StreetAddress, Subdivision, UpdateBookingRequest, UpdateBookingResponse, UpdateExtendedFieldsRequest, UpdateNumberOfParticipantsOptionsParticipantsInfoOneOf, UpdateNumberOfParticipantsRequest, UpdateNumberOfParticipantsRequestParticipantsInfoOneOf, V2CancelBookingRequest, V2CancelBookingResponse, V2ConfirmBookingRequest, V2ConfirmBookingResponse, V2CreateBookingRequest, V2CreateBookingRequestBookableItemOneOf, V2CreateBookingRequestParticipantsInfoOneOf, V2CreateBookingResponse, V2DeclineBookingRequest, V2DeclineBookingResponse, V2PhoneCall, V2RescheduleBookingRequest, V2RescheduleBookingRequestParticipantsInfoOneOf, V2RescheduleBookingResponse, V2UpdateNumberOfParticipantsRequest, V2UpdateNumberOfParticipantsRequestParticipantsInfoOneOf, V2UpdateNumberOfParticipantsResponse, ValueType, ValueTypeWithLiterals, WaitingList, WebhookIdentityType, WebhookIdentityTypeWithLiterals, WebhooksIdentificationData, WebhooksIdentificationDataIdOneOf } from './index.typings.js';
+import { ConfirmOrDeclineBookingOptions, ConfirmOrDeclineBookingResponse, ConfirmOrDeclineBookingApplicationErrors, BulkConfirmOrDeclineBookingRequestBookingDetails, BulkConfirmOrDeclineBookingOptions, BulkConfirmOrDeclineBookingResponse, BulkConfirmOrDeclineBookingApplicationErrors, Booking, CreateMultiServiceBookingOptions, CreateMultiServiceBookingResponse, CreateMultiServiceBookingApplicationErrors, RescheduleBookingInfo, RescheduleMultiServiceBookingOptions, RescheduleMultiServiceBookingResponse, RescheduleMultiServiceBookingApplicationErrors, GetMultiServiceBookingAvailabilityResponse, GetMultiServiceBookingAvailabilityApplicationErrors, CancelMultiServiceBookingOptions, CancelMultiServiceBookingResponse, CancelMultiServiceBookingApplicationErrors, MarkMultiServiceBookingAsPendingOptions, MarkMultiServiceBookingAsPendingResponse, MarkMultiServiceBookingAsPendingApplicationErrors, ConfirmMultiServiceBookingOptions, ConfirmMultiServiceBookingResponse, ConfirmMultiServiceBookingApplicationErrors, DeclineMultiServiceBookingOptions, DeclineMultiServiceBookingResponse, DeclineMultiServiceBookingApplicationErrors, BulkGetMultiServiceBookingAllowedActionsResponse, MultiServiceBooking, AddBookingsToMultiServiceBookingOptions, AddBookingsToMultiServiceBookingResponse, AddBookingsToMultiServiceBookingApplicationErrors, RemoveBookingsFromMultiServiceBookingOptions, RemoveBookingsFromMultiServiceBookingResponse, RemoveBookingsFromMultiServiceBookingApplicationErrors, CreateBookingOptions, CreateBookingResponse, CreateBookingApplicationErrors, CreateBookingInfo, BulkCreateBookingOptions, BulkCreateBookingResponse, BulkCreateBookingApplicationErrors, V2Slot, RescheduleBookingOptions, RescheduleBookingResponse, RescheduleBookingApplicationErrors, ConfirmBookingOptions, ConfirmBookingResponse, ConfirmBookingApplicationErrors, SetBookingSubmissionIdResponse, SetBookingSubmissionIdApplicationErrors, UpdateExtendedFieldsOptions, UpdateExtendedFieldsResponse, UpdateExtendedFieldsApplicationErrors, DeclineBookingOptions, DeclineBookingResponse, DeclineBookingApplicationErrors, CancelBookingOptions, CancelBookingResponse, CancelBookingApplicationErrors, UpdateNumberOfParticipantsOptions, UpdateNumberOfParticipantsResponse, UpdateNumberOfParticipantsApplicationErrors, MarkBookingAsPendingOptions, MarkBookingAsPendingResponse, MarkBookingAsPendingApplicationErrors, GetAnonymousActionDetailsOptions, GetAnonymousActionDetailsResponse, CancelBookingAnonymouslyOptions, CancelBookingAnonymouslyResponse, RescheduleBookingAnonymouslyOptions, RescheduleBookingAnonymouslyResponse, GetBookingAnonymouslyResponse, BookingCanceledEnvelope, BookingConfirmedEnvelope, BookingCreatedEnvelope, BookingDeclinedEnvelope, BookingRescheduledEnvelope, BookingUpdatedEnvelope, BookingNumberOfParticipantsUpdatedEnvelope } from './index.typings.js';
+export { ActionEvent, Actor, ActorWithLiterals, AddBookingsToMultiServiceBookingRequest, Address, AddressLocation, AddressStreetOneOf, AllowedActions, AllowedActionsAnonymously, AnonymousBookingUrls, ApplicationError, AvailableResources, BaseEventMetadata, BookedAddOn, BookedEntity, BookedEntityItemOneOf, BookedResource, BookedSchedule, BookedSlot, BookingCanceled, BookingChanged, BookingConfirmed, BookingDeclined, BookingDetails, BookingFormFilled, BookingIdAndRevision, BookingInfo, BookingMarkedAsPending, BookingParticipantsInfoOneOf, BookingPolicySettings, BookingPolicyViolations, BookingRescheduled, BookingRescheduledPreviousParticipantsInfoOneOf, BookingResult, BookingSource, BookingStatus, BookingStatusWithLiterals, BulkActionMetadata, BulkBookingResult, BulkCalculateAllowedActionsRequest, BulkCalculateAllowedActionsResponse, BulkCalculateAllowedActionsResult, BulkConfirmOrDeclineBookingRequest, BulkCreateBookingRequest, BulkGetMultiServiceBookingAllowedActionsRequest, BulkRescheduleBookingRequest, BulkRescheduleBookingRequestBooking, BulkRescheduleBookingResponse, BulkUpdateBookedScheduleRequest, BulkUpdateBookedScheduleResponse, BulkUpdateBookingRequest, BulkUpdateBookingResponse, CancelBookingAnonymouslyRequest, CancelBookingFlowControlSettings, CancelBookingRequest, CancelBookingRequestFlowControlSettings, CancelMultiServiceBookingRequest, Clash, CommonIdentificationData, CommonIdentificationDataIdOneOf, ConfirmBookingFlowControlSettings, ConfirmBookingRequest, ConfirmMultiServiceBookingRequest, ConfirmOrDeclineBookingRequest, ConfirmRequest, ConfirmResponse, ConsistentQueryBookingsRequest, ConsistentQueryBookingsResponse, ContactDetails, CountBookingsRequest, CountBookingsResponse, CreateBookingFlowControlSettings, CreateBookingRequest, CreateBookingRequestFlowControlSettings, CreateMultiServiceBookingRequest, CursorPaging, Cursors, CustomFormField, DeclineBookingFlowControlSettings, DeclineBookingRequest, DeclineMultiServiceBookingRequest, DomainEvent, DomainEventBodyOneOf, Duration, EntityCreatedEvent, EntityDeletedEvent, EntityUpdatedEvent, EventMetadata, ExtendedFields, FlowControlSettings, GetAnonymousActionDetailsRequest, GetBookingAnonymouslyRequest, GetMultiServiceBookingAvailabilityRequest, GetMultiServiceBookingAvailabilityResponseBookingInfo, GetMultiServiceBookingRequest, GetMultiServiceBookingResponse, GetScheduleAvailabilityRequest, GetScheduleAvailabilityResponse, GetSlotAvailabilityRequest, GetSlotAvailabilityResponse, IdentificationData, IdentificationDataIdOneOf, IdentificationDataIdentityType, IdentificationDataIdentityTypeWithLiterals, IdentityType, IdentityTypeWithLiterals, ItemMetadata, LegacyCreateBookingRequest, LegacyCreateBookingResponse, Location, LocationLocationType, LocationLocationTypeWithLiterals, LocationType, LocationTypeWithLiterals, MarkBookingAsPendingFlowControlSettings, MarkBookingAsPendingRequest, MarkMultiServiceBookingAsPendingRequest, MaskedBooking, MessageEnvelope, MigrationCheckIfClashesWithBlockedTimeRequest, MigrationCheckIfClashesWithBlockedTimeResponse, MsidAndBookingId, MultiServiceBookingInfo, MultiServiceBookingMetadata, MultiServiceBookingType, MultiServiceBookingTypeWithLiterals, NumberOfParticipantsUpdated, NumberOfParticipantsUpdatedPreviousParticipantsInfoOneOf, Paging, PagingMetadataV2, ParticipantChoices, ParticipantNotification, PaymentStatus, PaymentStatusWithLiterals, PhoneCall, Platform, PlatformWithLiterals, QueryBookingsRequest, QueryBookingsResponse, QueryV2, QueryV2PagingMethodOneOf, RemoveBookingsFromMultiServiceBookingRequest, RescheduleBookingAnonymouslyRequest, RescheduleBookingFlowControlSettings, RescheduleBookingInfoParticipantsInfoOneOf, RescheduleBookingOptionsParticipantsInfoOneOf, RescheduleBookingRequest, RescheduleBookingRequestFlowControlSettings, RescheduleBookingRequestParticipantsInfoOneOf, RescheduleMultiServiceBookingRequest, ResourceSelection, RestoreInfo, ScheduleAvailability, SelectedPaymentOption, SelectedPaymentOptionWithLiterals, SelectionMethod, SelectionMethodWithLiterals, ServiceChoice, ServiceChoiceChoiceOneOf, ServiceChoices, SetBookingSessionIdRequest, SetBookingSessionIdResponse, SetBookingSubmissionIdRequest, Slot, SlotAvailability, SlotBookings, SlotLocation, SlotResource, SlotSlotResource, SortOrder, SortOrderWithLiterals, Sorting, StreetAddress, Subdivision, UpdateBookingRequest, UpdateBookingResponse, UpdateExtendedFieldsRequest, UpdateNumberOfParticipantsOptionsParticipantsInfoOneOf, UpdateNumberOfParticipantsRequest, UpdateNumberOfParticipantsRequestParticipantsInfoOneOf, V2CancelBookingRequest, V2CancelBookingResponse, V2ConfirmBookingRequest, V2ConfirmBookingResponse, V2CreateBookingRequest, V2CreateBookingRequestBookableItemOneOf, V2CreateBookingRequestParticipantsInfoOneOf, V2CreateBookingResponse, V2DeclineBookingRequest, V2DeclineBookingResponse, V2PhoneCall, V2RescheduleBookingRequest, V2RescheduleBookingRequestParticipantsInfoOneOf, V2RescheduleBookingResponse, V2UpdateNumberOfParticipantsRequest, V2UpdateNumberOfParticipantsRequestParticipantsInfoOneOf, V2UpdateNumberOfParticipantsResponse, ValueType, ValueTypeWithLiterals, WaitingList, WebhookIdentityType, WebhookIdentityTypeWithLiterals, WebhooksIdentificationData, WebhooksIdentificationDataIdOneOf } from './index.typings.js';
 
-declare function getAnonymousActionDetails$1(httpClient: HttpClient): GetAnonymousActionDetailsSignature;
-interface GetAnonymousActionDetailsSignature {
-    /**
-     * Returns booking details related to AnonymousActions
-     * Anonymous tokens for getting, canceling or rescheduling the booking.
-     * That token is symmetrically encrypted and Url-safe.
-     * That allows the UoU to cancel or reschedule without Authentication.
-     * @returns Response for GetAnonymousActionDetails
-     */
-    (options?: GetAnonymousActionDetailsOptions): Promise<GetAnonymousActionDetailsResponse>;
-}
-declare function cancelBookingAnonymously$1(httpClient: HttpClient): CancelBookingAnonymouslySignature;
-interface CancelBookingAnonymouslySignature {
-    /**
-     * Cancel booking using an anonymous token
-     * @param - The token provided in the booking links for anonymous access
-     * @returns Response for CancelBookingAnonymously
-     */
-    (token: string, options?: CancelBookingAnonymouslyOptions): Promise<NonNullablePaths<CancelBookingAnonymouslyResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7>>;
-}
-declare function rescheduleBookingAnonymously$1(httpClient: HttpClient): RescheduleBookingAnonymouslySignature;
-interface RescheduleBookingAnonymouslySignature {
-    /**
-     * Reschedule booking using an anonymous token
-     * @param - The token provided in the booking links for anonymous access
-     * @param - New slot of the booking.
-     * @returns Response for RescheduleBookingAnonymously
-     */
-    (token: string, slot: V2Slot, options: NonNullablePaths<RescheduleBookingAnonymouslyOptions, `revision`, 2>): Promise<NonNullablePaths<RescheduleBookingAnonymouslyResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7>>;
-}
-declare function getBookingAnonymously$1(httpClient: HttpClient): GetBookingAnonymouslySignature;
-interface GetBookingAnonymouslySignature {
-    /**
-     * Get booking using an anonymous token
-     * @param - The token provided in the booking links for anonymous access
-     * @returns Response for GetBookingAnonymously
-     */
-    (token: string): Promise<NonNullablePaths<GetBookingAnonymouslyResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId` | `allowedActionsAnonymously.cancel` | `allowedActionsAnonymously.reschedule`, 7>>;
-}
 declare function confirmOrDeclineBooking$1(httpClient: HttpClient): ConfirmOrDeclineBookingSignature;
 interface ConfirmOrDeclineBookingSignature {
     /**
@@ -102,162 +63,440 @@ interface BulkConfirmOrDeclineBookingSignature {
         __applicationErrorsType?: BulkConfirmOrDeclineBookingApplicationErrors;
     }>;
 }
-declare function createBooking$1(httpClient: HttpClient): CreateBookingSignature;
-interface CreateBookingSignature {
+declare function createMultiServiceBooking$1(httpClient: HttpClient): CreateMultiServiceBookingSignature;
+interface CreateMultiServiceBookingSignature {
     /**
-     * Creates a booking.
-     *
-     *
-     * ### Appointment booking
-     *
-     * For appointment-based services, specify the relevant time slot in `bookedEntity.slot`.
-     *
-     * We recommend following the [appointment booking sample flow](https://dev.wix.com/docs/api-reference/business-solutions/bookings/bookings/bookings-writer-v2/sample-flows#book-an-appointment) using Time Slots V2.
-     * Specify the slot's `startDate`, `endDate`, `resource`, and `location` in `booking.bookedEntity.slot`.
+     * Creates a multi-service booking and all included single-service bookings simultaneously.
      *
-     * ### Class session booking
      *
-     * For class services, specify the relevant event ID as `bookedEntity.slot.eventId`.
+     * ### When to call this method
      *
-     * We recommend following the [class session booking sample flow](https://dev.wix.com/docs/api-reference/business-solutions/bookings/bookings/bookings-writer-v2/sample-flows#book-a-class-session) using Time Slots V2.
-     * Specify the `eventId` from the selected time slot in `booking.bookedEntity.slot.eventId`.
+     * 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](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/add-bookings-to-multi-service-booking) instead.
      *
-     * When you specify `eventId`, Wix Bookings automatically derives `startDate`, `endDate`, `timezone`, `resource`, and `location` based on the event details. Manually specified values are ignored.
+     * ### Requirements and behavior
      *
-     * ### Course booking
+     * __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.
      *
-     * For course services, specify the course's schedule ID in `bookedEntity.schedule.scheduleId`.
-     * We recommend following [this sample flow](https://dev.wix.com/docs/rest/business-solutions/bookings/end-to-end-booking-flows#book-a-course)
-     * to minimize failed calls due to unavailability.
+     * __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.
      *
-     * ### Booking status
+     * __Package pricing__: The total price equals the sum of individual services. Wix Bookings automatically syncs the payment status from the corresponding [Wix eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) if the customer paid via an [eCommerce checkout](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction).
      *
-     * Create Booking defaults to `status=CREATED`. Such bookings aren't visible in the [Booking Calendar](https://support.wix.com/en/article/wix-bookings-about-the-wix-booking-calendar).
+     * __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.
      *
-     * Only [identities](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities) with `Manage Bookings` permissions can set `status=CONFIRMED`.
+     * ### Related methods
      *
-     * ### Related resources
+     * Verify availability first with [List Multi Service Availability Time Slots](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/time-slots-v2/list-multi-service-availability-time-slots).
      *
-     * Specifying a `resource` triggers an availability check, and the Create Booking call fails if the resource is unavailable.
+     * See [Create Booking](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.
      *
-     * If you omit `resource`, resource assignment and availability validation occur during booking confirmation.
-     * If no resources are available, the behavior depends on the confirmation method used and payment status.
+     * 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.
      *
-     * ### Booking form data
+     * 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`, 5>[], options?: CreateMultiServiceBookingOptions): Promise<NonNullablePaths<CreateMultiServiceBookingResponse, `multiServiceBooking.bookings` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
+        __applicationErrorsType?: CreateMultiServiceBookingApplicationErrors;
+    }>;
+}
+declare function rescheduleMultiServiceBooking$1(httpClient: HttpClient): RescheduleMultiServiceBookingSignature;
+interface RescheduleMultiServiceBookingSignature {
+    /**
+     * Reschedules a multi-service booking by changing the timing for all or specific single-service bookings in the package.
      *
-     * When customers sign up for a service, they must fill out the [booking form](https://support.wix.com/en/article/wix-bookings-creating-and-setting-up-your-booking-forms).
-     * To create a booking with a completed booking form, specify the relevant data in `formSubmission`.
-     * Ensure the values of the corresponding fields in `booking.contactDetails` and `formSubmission` are identical.
-     * If these values don't match, Create Booking fails.
-     * Therefore, we recommend specifying only `booking.contactDetails.contactId` when providing `formSubmission`.
-     * Learn more about the [Bookings and Wix Forms integration](https://dev.wix.com/docs/rest/business-solutions/bookings/wix-forms-integration).
      *
-     * ### Participant information
+     * 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.
      *
-     * You must specify either `participantsChoices` or `totalParticipants`.
-     * The call fails if the specified `participantsChoices` aren't among the supported
-     * [service options and variants](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction).
+     * 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.
      *
-     * ### Add-ons
+     * See [Reschedule Booking](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`, 2>[], options?: RescheduleMultiServiceBookingOptions): Promise<NonNullablePaths<RescheduleMultiServiceBookingResponse, `multiServiceBooking.bookings` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
+        __applicationErrorsType?: RescheduleMultiServiceBookingApplicationErrors;
+    }>;
+}
+declare function getMultiServiceBookingAvailability$1(httpClient: HttpClient): GetMultiServiceBookingAvailabilitySignature;
+interface GetMultiServiceBookingAvailabilitySignature {
+    /**
+     * Checks if the business can still accommodate an existing multi-service booking and returns overall bookability status, capacity details, and policy violations.
      *
-     * You can include [add-ons](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/add-ons/introduction) when creating a booking by specifying `bookedAddOns`.
-     * Each selected add-on must belong to an [add-on group](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/about-add-on-groups) associated with the service and respect the group's selection limits.
      *
-     * ### Notify customers
+     * Wix Bookings considers:
+     * - The relevant services' [booking policies](https://dev.wix.com/docs/rest/business-solutions/bookings/policies/booking-policies/introduction).
+     * - The availability of all required [resources](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/resources-v2/introduction).
      *
-     * You can specify a `participantNotification.message` for the customer that's send
-     * immediately. Ensure `participantNotification.notifyParticipants` is set to `true`
-     * to send the message.
+     * 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.
      *
-     * If you specify `{"sendSmsReminder": true}`, the customer receives an SMS 24 hours
-     * before the session starts. The phone number is taken from `contactDetails.phone`.
+     * For checking availability before creating new multi-service bookings, call [List Multi Service Availability Time Slots](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/time-slots-v2/list-multi-service-availability-time-slots) instead.
+     * @param - ID of the multi-service booking to retrieve.
+     */
+    (multiServiceBookingId: string): Promise<NonNullablePaths<GetMultiServiceBookingAvailabilityResponse, `bookable` | `multiServiceBookingInfo`, 2> & {
+        __applicationErrorsType?: GetMultiServiceBookingAvailabilityApplicationErrors;
+    }>;
+}
+declare function cancelMultiServiceBooking$1(httpClient: HttpClient): CancelMultiServiceBookingSignature;
+interface CancelMultiServiceBookingSignature {
+    /**
+     * Cancels a multi-service booking and all its associated single-service bookings.
      *
-     * ### Payment options
      *
-     * The specified `selectedPaymentOption` indicates how the customer intends to pay, allowing for later changes to a different method supported by the service.
+     * 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.
      *
-     * ### Payment status
+     * See [Cancel Booking](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` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
+        __applicationErrorsType?: CancelMultiServiceBookingApplicationErrors;
+    }>;
+}
+declare function markMultiServiceBookingAsPending$1(httpClient: HttpClient): MarkMultiServiceBookingAsPendingSignature;
+interface MarkMultiServiceBookingAsPendingSignature {
+    /**
+     * Updates the status for all single-service bookings in a multi-service booking to `PENDING`.
      *
-     * All bookings are created with `paymentStatus=UNDEFINED`, ignoring the payment status you specify.
      *
-     * For customers paying with a [Wix eCommerce checkout](https://dev.wix.com/docs/rest/business-solutions/e-commerce/purchase-flow/checkout/checkout/introduction), Wix Bookings automatically syncs the booking's payment status from the corresponding [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction).
+     * Call this method for multi-service bookings requiring manual business approval before confirmation.
      *
-     * For customers using a custom checkout, call [Confirm or Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking) to update booking's payment status manually.
+     * ### Status requirements
      *
-     * ### Admin overwrites
+     * - __Original status__: All single-service bookings must have `CREATED` status.
+     * - __Target status__: All bookings move to `PENDING` together (all-or-nothing operation).
      *
-     * There are small but important differences when you specify special
-     * `flowControlSettings`:
+     * ### Checkout restrictions
      *
-     * - `{"skipAvailabilityValidation": true}`: The call succeeds
-     * regardless of availability. If you don't specify any resource, the call
-     * succeeds even if no resource of the relevant type is available.
-     * - `{"skipBusinessConfirmation": true}`: Automatically confirms `PENDING`
-     * bookings that require manual confirmation.
-     * - `{"skipSelectedPaymentOptionValidation": true}`: Allows customers to pay
-     * with payment methods that aren't supported for the service.
-     * - `{"skipAddOnValidation": true}`: Allows customers to choose add-ons that aren't associated with the service or exceed group selection limits.
-     * - `{"allowAddOnChanges": true}`: Allows customers to update the list of add-ons associated with the booking when rescheduling.
+     * 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.
      *
-     * When using special `flowControlSettings`, ensure you have sufficient
-     * permissions. If you encounter failed calls due to insufficient permissions,
-     * consider the following options:
+     * ### Additional updates
      *
-     * - **App developers** can use a higher
-     * [permission](https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions),
-     * such as `MANAGE BOOKINGS - ALL PERMISSIONS`.
-     * - **Site developers** can utilize
-     * [elevation](https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/authorization/elevation).
+     * - __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.
      *
-     * Granting additional permissions and using elevation permits method calls that
-     * would typically fail due to authorization checks. Therefore, you should use
-     * them intentionally and securely.
-     * @param - The booking to create.
+     * See [Mark Booking as Pending](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`.
      */
-    (booking: NonNullablePaths<Booking, `additionalFields.${number}._id` | `bookedEntity`, 4>, options?: CreateBookingOptions): Promise<NonNullablePaths<CreateBookingResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7> & {
-        __applicationErrorsType?: CreateBookingApplicationErrors;
+    (multiServiceBookingId: string, options?: MarkMultiServiceBookingAsPendingOptions): Promise<NonNullablePaths<MarkMultiServiceBookingAsPendingResponse, `multiServiceBooking.bookings` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
+        __applicationErrorsType?: MarkMultiServiceBookingAsPendingApplicationErrors;
     }>;
 }
-declare function bulkCreateBooking$1(httpClient: HttpClient): BulkCreateBookingSignature;
-interface BulkCreateBookingSignature {
+declare function confirmMultiServiceBooking$1(httpClient: HttpClient): ConfirmMultiServiceBookingSignature;
+interface ConfirmMultiServiceBookingSignature {
     /**
-     * Creates up to 8 bookings.
+     * Updates the status for all single-service bookings in a multi-service booking to `CONFIRMED`.
      *
      *
-     * See [Create Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/create-booking)
-     * for more information.
+     * Call this method for multi-service bookings requiring manual business approval.
      *
-     * If any of the specified bookings is missing a required field the entire call
-     * fails.
+     * ### Status requirements
      *
-     * If you specify 1 or more unavailable bookings, the call succeeds
-     * while the unavailable bookings aren't created. Instead, they're counted as
-     * failures in the returned `bulkActionMetadata`.
-     * @param - Bookings to create.
+     * - __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).
      *
-     * Max: 8 bookings
+     * ### 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](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.
      */
-    (createBookingsInfo: NonNullablePaths<CreateBookingInfo, `booking` | `booking.additionalFields.${number}._id` | `booking.bookedEntity`, 5>[], options?: BulkCreateBookingOptions): Promise<NonNullablePaths<BulkCreateBookingResponse, `results` | `results.${number}.itemMetadata.originalIndex` | `results.${number}.itemMetadata.success` | `results.${number}.itemMetadata.error.code` | `results.${number}.itemMetadata.error.description` | `results.${number}.item.totalParticipants` | `results.${number}.item.status` | `results.${number}.item.paymentStatus` | `results.${number}.item.selectedPaymentOption` | `results.${number}.item.createdBy.anonymousVisitorId` | `results.${number}.item.createdBy.memberId` | `results.${number}.item.createdBy.wixUserId` | `results.${number}.item.createdBy.appId` | `bulkActionMetadata.totalSuccesses` | `bulkActionMetadata.totalFailures` | `bulkActionMetadata.undetailedFailures`, 6> & {
-        __applicationErrorsType?: BulkCreateBookingApplicationErrors;
+    (multiServiceBookingId: string, options?: ConfirmMultiServiceBookingOptions): Promise<NonNullablePaths<ConfirmMultiServiceBookingResponse, `multiServiceBooking.bookings` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
+        __applicationErrorsType?: ConfirmMultiServiceBookingApplicationErrors;
     }>;
 }
-declare function rescheduleBooking$1(httpClient: HttpClient): RescheduleBookingSignature;
-interface RescheduleBookingSignature {
+declare function declineMultiServiceBooking$1(httpClient: HttpClient): DeclineMultiServiceBookingSignature;
+interface DeclineMultiServiceBookingSignature {
     /**
-     * Reschedules an appointment booking to a different slot or a class booking to
-     * a different session.
+     * Updates the status for all single-service bookings in a multi-service booking to `DECLINED`.
      *
      *
-     * ### Updating add-ons
+     * Call this method to reject multi-service bookings that can't be accommodated or don't meet business requirements.
      *
-     * You can also call this method to update the list of [add-ons](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/add-ons/introduction) associated with the booking.
-     * To do so, both of these conditions must be met:
-     * + The booking must have been created with `flowControlSettings.allowAddOnChanges` set to `true`.
-     * + You must have `BOOKINGS.MANAGE_ADDONS` permissions and specify `flowControlSettings.allowAddOnChanges` as `true`.
+     * ### Status requirements
      *
-     * ### Course booking limitation
+     * - __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).
      *
-     * You can't reschedule course bookings.
+     * ### 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 `declineBookingsInfo.paymentStatus`.
+     * - __Customer notifications__: Send messages using `participantNotification`.
+     * - __Revision control__: Requires current revision numbers for all single-service bookings.
+     *
+     * Refer to [Decline Booking](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` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
+        __applicationErrorsType?: DeclineMultiServiceBookingApplicationErrors;
+    }>;
+}
+declare function bulkGetMultiServiceBookingAllowedActions$1(httpClient: HttpClient): BulkGetMultiServiceBookingAllowedActionsSignature;
+interface BulkGetMultiServiceBookingAllowedActionsSignature {
+    /**
+     * 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](https://dev.wix.com/docs/rest/business-solutions/bookings/policies/booking-policies/introduction), and [available resources](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/docs/build-apps/develop-your-app/access/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`, 6>>;
+}
+declare function getMultiServiceBooking$1(httpClient: HttpClient): GetMultiServiceBookingSignature;
+interface GetMultiServiceBookingSignature {
+    /**
+     * Retrieves a multi-service booking and all its associated single-service bookings.
+     *
+     *
+     * 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](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 - ID of the multi-service booking.
+     * @returns Retrieved multi-service booking.
+     */
+    (multiServiceBookingId: string): Promise<NonNullablePaths<MultiServiceBooking, `bookings` | `bookings.${number}.booking.totalParticipants` | `bookings.${number}.booking.status` | `bookings.${number}.booking.paymentStatus` | `bookings.${number}.booking.selectedPaymentOption` | `bookings.${number}.booking.createdBy.anonymousVisitorId` | `bookings.${number}.booking.createdBy.memberId` | `bookings.${number}.booking.createdBy.wixUserId` | `bookings.${number}.booking.createdBy.appId`, 6>>;
+}
+declare function addBookingsToMultiServiceBooking$1(httpClient: HttpClient): AddBookingsToMultiServiceBookingSignature;
+interface AddBookingsToMultiServiceBookingSignature {
+    /**
+     * 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](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
+     *
+     * - __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`, 4>): Promise<NonNullablePaths<AddBookingsToMultiServiceBookingResponse, `bookings` | `bookings.${number}.booking.totalParticipants` | `bookings.${number}.booking.status` | `bookings.${number}.booking.paymentStatus` | `bookings.${number}.booking.selectedPaymentOption` | `bookings.${number}.booking.createdBy.anonymousVisitorId` | `bookings.${number}.booking.createdBy.memberId` | `bookings.${number}.booking.createdBy.wixUserId` | `bookings.${number}.booking.createdBy.appId`, 6> & {
+        __applicationErrorsType?: AddBookingsToMultiServiceBookingApplicationErrors;
+    }>;
+}
+declare function removeBookingsFromMultiServiceBooking$1(httpClient: HttpClient): RemoveBookingsFromMultiServiceBookingSignature;
+interface RemoveBookingsFromMultiServiceBookingSignature {
+    /**
+     * 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](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/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.
+     *
+     * __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 - ID of the multi-service booking.
+     */
+    (multiServiceBookingId: string, options?: RemoveBookingsFromMultiServiceBookingOptions): Promise<NonNullablePaths<RemoveBookingsFromMultiServiceBookingResponse, `bookings` | `bookings.${number}.booking.totalParticipants` | `bookings.${number}.booking.status` | `bookings.${number}.booking.paymentStatus` | `bookings.${number}.booking.selectedPaymentOption` | `bookings.${number}.booking.createdBy.anonymousVisitorId` | `bookings.${number}.booking.createdBy.memberId` | `bookings.${number}.booking.createdBy.wixUserId` | `bookings.${number}.booking.createdBy.appId`, 6> & {
+        __applicationErrorsType?: RemoveBookingsFromMultiServiceBookingApplicationErrors;
+    }>;
+}
+declare function createBooking$1(httpClient: HttpClient): CreateBookingSignature;
+interface CreateBookingSignature {
+    /**
+     * Creates a booking.
+     *
+     *
+     * ### Appointment booking
+     *
+     * For appointment-based services, specify the relevant time slot in `bookedEntity.slot`.
+     *
+     * We recommend following the [appointment booking sample flow](https://dev.wix.com/docs/api-reference/business-solutions/bookings/bookings/bookings-writer-v2/sample-flows#book-an-appointment) using Time Slots V2.
+     * Specify the slot's `startDate`, `endDate`, `resource`, and `location` in `booking.bookedEntity.slot`.
+     *
+     * ### Class session booking
+     *
+     * For class services, specify the relevant event ID as `bookedEntity.slot.eventId`.
+     *
+     * We recommend following the [class session booking sample flow](https://dev.wix.com/docs/api-reference/business-solutions/bookings/bookings/bookings-writer-v2/sample-flows#book-a-class-session) using Time Slots V2.
+     * Specify the `eventId` from the selected time slot in `booking.bookedEntity.slot.eventId`.
+     *
+     * When you specify `eventId`, Wix Bookings automatically derives `startDate`, `endDate`, `timezone`, `resource`, and `location` based on the event details. Manually specified values are ignored.
+     *
+     * ### Course booking
+     *
+     * For course services, specify the course's schedule ID in `bookedEntity.schedule.scheduleId`.
+     * We recommend following [this sample flow](https://dev.wix.com/docs/rest/business-solutions/bookings/end-to-end-booking-flows#book-a-course)
+     * to minimize failed calls due to unavailability.
+     *
+     * ### Booking status
+     *
+     * Create Booking defaults to `status=CREATED`. Such bookings aren't visible in the [Booking Calendar](https://support.wix.com/en/article/wix-bookings-about-the-wix-booking-calendar).
+     *
+     * Only [identities](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities) with `Manage Bookings` permissions can set `status=CONFIRMED`.
+     *
+     * ### Related resources
+     *
+     * Specifying a `resource` triggers an availability check, and the Create Booking call fails if the resource is unavailable.
+     *
+     * If you omit `resource`, resource assignment and availability validation occur during booking confirmation.
+     * If no resources are available, the behavior depends on the confirmation method used and payment status.
+     *
+     * ### Booking form data
+     *
+     * When customers sign up for a service, they must fill out the [booking form](https://support.wix.com/en/article/wix-bookings-creating-and-setting-up-your-booking-forms).
+     * To create a booking with a completed booking form, specify the relevant data in `formSubmission`.
+     * Ensure the values of the corresponding fields in `booking.contactDetails` and `formSubmission` are identical.
+     * If these values don't match, Create Booking fails.
+     * Therefore, we recommend specifying only `booking.contactDetails.contactId` when providing `formSubmission`.
+     * Learn more about the [Bookings and Wix Forms integration](https://dev.wix.com/docs/rest/business-solutions/bookings/wix-forms-integration).
+     *
+     * ### Participant information
+     *
+     * You must specify either `participantsChoices` or `totalParticipants`.
+     * The call fails if the specified `participantsChoices` aren't among the supported
+     * [service options and variants](https://dev.wix.com/docs/rest/business-solutions/bookings/services/service-options-and-variants/introduction).
+     *
+     * ### Add-ons
+     *
+     * You can include [add-ons](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/add-ons/introduction) when creating a booking by specifying `bookedAddOns`.
+     * Each selected add-on must belong to an [add-on group](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/about-add-on-groups) associated with the service and respect the group's selection limits.
+     *
+     * ### Notify customers
+     *
+     * You can specify a `participantNotification.message` for the customer that's send
+     * immediately. Ensure `participantNotification.notifyParticipants` is set to `true`
+     * to send the message.
+     *
+     * If you specify `{"sendSmsReminder": true}`, the customer receives an SMS 24 hours
+     * before the session starts. The phone number is taken from `contactDetails.phone`.
+     *
+     * ### Payment options
+     *
+     * The specified `selectedPaymentOption` indicates how the customer intends to pay, allowing for later changes to a different method supported by the service.
+     *
+     * ### Payment status
+     *
+     * All bookings are created with `paymentStatus=UNDEFINED`, ignoring the payment status you specify.
+     *
+     * For customers paying with a [Wix eCommerce checkout](https://dev.wix.com/docs/rest/business-solutions/e-commerce/purchase-flow/checkout/checkout/introduction), Wix Bookings automatically syncs the booking's payment status from the corresponding [eCommerce order](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction).
+     *
+     * For customers using a custom checkout, call [Confirm or Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking) to update booking's payment status manually.
+     *
+     * ### Admin overwrites
+     *
+     * There are small but important differences when you specify special
+     * `flowControlSettings`:
+     *
+     * - `{"skipAvailabilityValidation": true}`: The call succeeds
+     * regardless of availability. If you don't specify any resource, the call
+     * succeeds even if no resource of the relevant type is available.
+     * - `{"skipBusinessConfirmation": true}`: Automatically confirms `PENDING`
+     * bookings that require manual confirmation.
+     * - `{"skipSelectedPaymentOptionValidation": true}`: Allows customers to pay
+     * with payment methods that aren't supported for the service.
+     * - `{"skipAddOnValidation": true}`: Allows customers to choose add-ons that aren't associated with the service or exceed group selection limits.
+     * - `{"allowAddOnChanges": true}`: Allows customers to update the list of add-ons associated with the booking when rescheduling.
+     *
+     * When using special `flowControlSettings`, ensure you have sufficient
+     * permissions. If you encounter failed calls due to insufficient permissions,
+     * consider the following options:
+     *
+     * - **App developers** can use a higher
+     * [permission](https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions),
+     * such as `MANAGE BOOKINGS - ALL PERMISSIONS`.
+     * - **Site developers** can utilize
+     * [elevation](https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/authorization/elevation).
+     *
+     * Granting additional permissions and using elevation permits method calls that
+     * would typically fail due to authorization checks. Therefore, you should use
+     * them intentionally and securely.
+     * @param - The booking to create.
+     */
+    (booking: NonNullablePaths<Booking, `additionalFields.${number}._id` | `bookedEntity`, 4>, options?: CreateBookingOptions): Promise<NonNullablePaths<CreateBookingResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7> & {
+        __applicationErrorsType?: CreateBookingApplicationErrors;
+    }>;
+}
+declare function bulkCreateBooking$1(httpClient: HttpClient): BulkCreateBookingSignature;
+interface BulkCreateBookingSignature {
+    /**
+     * Creates up to 8 bookings.
+     *
+     *
+     * See [Create Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/create-booking)
+     * for more information.
+     *
+     * If any of the specified bookings is missing a required field the entire call
+     * fails.
+     *
+     * If you specify 1 or more unavailable bookings, the call succeeds
+     * while the unavailable bookings aren't created. Instead, they're counted as
+     * failures in the returned `bulkActionMetadata`.
+     * @param - Bookings to create.
+     *
+     * Max: 8 bookings
+     */
+    (createBookingsInfo: NonNullablePaths<CreateBookingInfo, `booking` | `booking.additionalFields.${number}._id` | `booking.bookedEntity`, 5>[], options?: BulkCreateBookingOptions): Promise<NonNullablePaths<BulkCreateBookingResponse, `results` | `results.${number}.itemMetadata.originalIndex` | `results.${number}.itemMetadata.success` | `results.${number}.itemMetadata.error.code` | `results.${number}.itemMetadata.error.description` | `results.${number}.item.totalParticipants` | `results.${number}.item.status` | `results.${number}.item.paymentStatus` | `results.${number}.item.selectedPaymentOption` | `results.${number}.item.createdBy.anonymousVisitorId` | `results.${number}.item.createdBy.memberId` | `results.${number}.item.createdBy.wixUserId` | `results.${number}.item.createdBy.appId` | `bulkActionMetadata.totalSuccesses` | `bulkActionMetadata.totalFailures` | `bulkActionMetadata.undetailedFailures`, 6> & {
+        __applicationErrorsType?: BulkCreateBookingApplicationErrors;
+    }>;
+}
+declare function rescheduleBooking$1(httpClient: HttpClient): RescheduleBookingSignature;
+interface RescheduleBookingSignature {
+    /**
+     * Reschedules an appointment booking to a different slot or a class booking to
+     * a different session.
+     *
+     *
+     * ### Updating add-ons
+     *
+     * You can also call this method to update the list of [add-ons](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/add-ons/introduction) associated with the booking.
+     * To do so, both of these conditions must be met:
+     * + The booking must have been created with `flowControlSettings.allowAddOnChanges` set to `true`.
+     * + You must have `BOOKINGS.MANAGE_ADDONS` permissions and specify `flowControlSettings.allowAddOnChanges` as `true`.
+     *
+     * ### Course booking limitation
+     *
+     * You can't reschedule course bookings.
      *
      * ### Appointment sessions
      *
@@ -510,401 +749,148 @@ interface CancelBookingSignature {
 declare function updateNumberOfParticipants$1(httpClient: HttpClient): UpdateNumberOfParticipantsSignature;
 interface UpdateNumberOfParticipantsSignature {
     /**
-     * Updates the number of participants for a class or course booking and changes
-     * the `totalNumberOfParticipants` for the relevant sessions.
-     *
-     *
-     * ### Appointment limitation
-     *
-     * You can't update the number of participants for appointment bookings.
-     *
-     * ### Participant information
-     *
-     * You must specify either `participantsChoices` or `totalParticipants`.
-     * The call fails if the specified `participantsChoices` aren't among the
-     * supported [service options and variants](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.
-     */
-    (bookingId: string, options?: NonNullablePaths<UpdateNumberOfParticipantsOptions, `revision`, 2>): Promise<NonNullablePaths<UpdateNumberOfParticipantsResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7> & {
-        __applicationErrorsType?: UpdateNumberOfParticipantsApplicationErrors;
-    }>;
-}
-declare function markBookingAsPending$1(httpClient: HttpClient): MarkBookingAsPendingSignature;
-interface MarkBookingAsPendingSignature {
-    /**
-     * Updates the booking status to `PENDING`.
-     *
-     *
-     * ### Service requirement
-     *
-     * By default, this method only works for [services](https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/introduction) with `service.onlineBooking.requireManualApproval` set to `true`.
-     * If you attempt to mark a booking as pending for a service that doesn't require approval, the call fails unless you use the `skipPendingApprovalServiceValidation` admin overwrite.
-     *
-     * ### Status requirements
-     *
-     * - __Original status__: Booking must have `CREATED` status.
-     * - __Target status__: Booking moves to `PENDING`.
-     *
-     * ### Checkout restrictions
-     *
-     * Only call this method if the customer paid via a custom checkout. For [Wix eCommerce checkouts](https://dev.wix.com/docs/rest/business-solutions/e-commerce/purchase-flow/checkout/introduction), Wix Bookings automatically manages the bookings' statuses based on payment processing.
-     *
-     * When using custom checkouts, you can also update the booking's `paymentStatus` by specifying a new payment status.
-     *
-     * ### Business workflow
-     *
-     * After marking a booking as `PENDING`, the business must manually approve or reject it. You can call these methods:
-     * - [Confirm Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-booking).
-     * - [Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/decline-booking).
-     *
-     * ### Resource availability and scheduling
-     *
-     * Marking a booking as `PENDING` immediately affects resource availability:
-     *
-     * - **Calendar impact**: The booking appears on the business calendar.
-     * - **Availability**: The time slot becomes unavailable for other bookings, even while pending approval.
-     * - **Resource assignment**: Available [resources](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/resources-v2/introduction) are automatically assigned if none were explicitly selected during booking creation.
-     *
-     * ### Double bookings
-     *
-     * By default, the method doesn't check for availability conflicts. To detect and handle double bookings, use the `checkAvailabilityValidation: true` admin overwrite.
-     *
-     * ### Notify customers
-     *
-     * You can specify a `participantNotification.message` for the customer.
-     * To send the message, you must also specify `participantNotification.notifyParticipants` as `true`.
-     *
-     * ### Admin overwrites
-     *
-     * There are small but important differences when you specify special
-     * `flowControlSettings`:
-     *
-     * - `{"checkAvailabilityValidation": true}`: Checks for double booking conflicts before updating the status.
-     * When conflicts exist, the booking is still marked as `PENDING` and `doubleBooked` is set to `true` for the business to resolve manually.
-     * - `{"skipPendingApprovalServiceValidation": true}`: Allows marking any booking as pending, even if the service doesn't require manual approval.
-     *
-     * When using special `flowControlSettings`, ensure you have sufficient permissions.
-     * If you encounter failed calls due to insufficient permissions, consider the following options:
-     *
-     * - __App developers__ can use a higher
-     * [permission](https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions), such as `MANAGE BOOKINGS - ALL PERMISSIONS`.
-     * - __Site developers__ can utilize
-     * [elevation](https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/authorization/elevation).
-     *
-     * Granting additional permissions and using elevation permits method calls that would typically fail due to authorization checks.
-     * Therefore, you should use them intentionally and securely.
-     * @param - ID of the booking to mark as `PENDING`.
-     * @param - 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.
-     */
-    (bookingId: string, revision: string, options?: MarkBookingAsPendingOptions): Promise<NonNullablePaths<MarkBookingAsPendingResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7> & {
-        __applicationErrorsType?: MarkBookingAsPendingApplicationErrors;
-    }>;
-}
-declare function createMultiServiceBooking$1(httpClient: HttpClient): CreateMultiServiceBookingSignature;
-interface CreateMultiServiceBookingSignature {
-    /**
-     * 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](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](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction) if the customer paid via an [eCommerce checkout](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.
-     *
-     * ### Related methods
-     *
-     * Verify availability first with [List Multi Service Availability Time Slots](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/time-slots-v2/list-multi-service-availability-time-slots).
-     *
-     * See [Create Booking](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`, 5>[], options?: CreateMultiServiceBookingOptions): Promise<NonNullablePaths<CreateMultiServiceBookingResponse, `multiServiceBooking.bookings` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
-        __applicationErrorsType?: CreateMultiServiceBookingApplicationErrors;
-    }>;
-}
-declare function rescheduleMultiServiceBooking$1(httpClient: HttpClient): RescheduleMultiServiceBookingSignature;
-interface RescheduleMultiServiceBookingSignature {
-    /**
-     * Reschedules a multi-service booking by changing the timing for all or specific single-service bookings in the package.
-     *
-     *
-     * 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](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`, 2>[], options?: RescheduleMultiServiceBookingOptions): Promise<NonNullablePaths<RescheduleMultiServiceBookingResponse, `multiServiceBooking.bookings` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
-        __applicationErrorsType?: RescheduleMultiServiceBookingApplicationErrors;
-    }>;
-}
-declare function getMultiServiceBookingAvailability$1(httpClient: HttpClient): GetMultiServiceBookingAvailabilitySignature;
-interface GetMultiServiceBookingAvailabilitySignature {
-    /**
-     * 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](https://dev.wix.com/docs/rest/business-solutions/bookings/policies/booking-policies/introduction).
-     * - The availability of all required [resources](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/resources-v2/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](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/time-slots-v2/list-multi-service-availability-time-slots) instead.
-     * @param - ID of the multi-service booking to retrieve.
-     */
-    (multiServiceBookingId: string): Promise<NonNullablePaths<GetMultiServiceBookingAvailabilityResponse, `bookable` | `multiServiceBookingInfo`, 2> & {
-        __applicationErrorsType?: GetMultiServiceBookingAvailabilityApplicationErrors;
-    }>;
-}
-declare function cancelMultiServiceBooking$1(httpClient: HttpClient): CancelMultiServiceBookingSignature;
-interface CancelMultiServiceBookingSignature {
-    /**
-     * 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](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` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
-        __applicationErrorsType?: CancelMultiServiceBookingApplicationErrors;
-    }>;
-}
-declare function markMultiServiceBookingAsPending$1(httpClient: HttpClient): MarkMultiServiceBookingAsPendingSignature;
-interface MarkMultiServiceBookingAsPendingSignature {
-    /**
-     * 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).
+     * Updates the number of participants for a class or course booking and changes
+     * the `totalNumberOfParticipants` for the relevant sessions.
      *
-     * ### 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.
+     * ### Appointment limitation
      *
-     * ### Additional updates
+     * You can't update the number of participants for appointment bookings.
      *
-     * - __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.
+     * ### Participant information
      *
-     * See [Mark Booking as Pending](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`.
+     * You must specify either `participantsChoices` or `totalParticipants`.
+     * The call fails if the specified `participantsChoices` aren't among the
+     * supported [service options and variants](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.
      */
-    (multiServiceBookingId: string, options?: MarkMultiServiceBookingAsPendingOptions): Promise<NonNullablePaths<MarkMultiServiceBookingAsPendingResponse, `multiServiceBooking.bookings` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
-        __applicationErrorsType?: MarkMultiServiceBookingAsPendingApplicationErrors;
+    (bookingId: string, options?: NonNullablePaths<UpdateNumberOfParticipantsOptions, `revision`, 2>): Promise<NonNullablePaths<UpdateNumberOfParticipantsResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7> & {
+        __applicationErrorsType?: UpdateNumberOfParticipantsApplicationErrors;
     }>;
 }
-declare function confirmMultiServiceBooking$1(httpClient: HttpClient): ConfirmMultiServiceBookingSignature;
-interface ConfirmMultiServiceBookingSignature {
+declare function markBookingAsPending$1(httpClient: HttpClient): MarkBookingAsPendingSignature;
+interface MarkBookingAsPendingSignature {
     /**
-     * Updates the status for all single-service bookings in a multi-service booking to `CONFIRMED`.
+     * Updates the booking status to `PENDING`.
      *
      *
-     * Call this method for multi-service bookings requiring manual business approval.
+     * ### Service requirement
+     *
+     * By default, this method only works for [services](https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/introduction) with `service.onlineBooking.requireManualApproval` set to `true`.
+     * If you attempt to mark a booking as pending for a service that doesn't require approval, the call fails unless you use the `skipPendingApprovalServiceValidation` admin overwrite.
      *
      * ### 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).
+     * - __Original status__: Booking must have `CREATED` status.
+     * - __Target status__: Booking moves to `PENDING`.
      *
      * ### 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
+     * Only call this method if the customer paid via a custom checkout. For [Wix eCommerce checkouts](https://dev.wix.com/docs/rest/business-solutions/e-commerce/purchase-flow/checkout/introduction), Wix Bookings automatically manages the bookings' statuses based on payment processing.
      *
-     * - __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.
+     * When using custom checkouts, you can also update the booking's `paymentStatus` by specifying a new payment status.
      *
-     * See [Confirm Booking](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` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
-        __applicationErrorsType?: ConfirmMultiServiceBookingApplicationErrors;
-    }>;
-}
-declare function declineMultiServiceBooking$1(httpClient: HttpClient): DeclineMultiServiceBookingSignature;
-interface DeclineMultiServiceBookingSignature {
-    /**
-     * Updates the status for all single-service bookings in a multi-service booking to `DECLINED`.
+     * ### Business workflow
      *
+     * After marking a booking as `PENDING`, the business must manually approve or reject it. You can call these methods:
+     * - [Confirm Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-booking).
+     * - [Decline Booking](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/decline-booking).
      *
-     * Call this method to reject multi-service bookings that can't be accommodated or don't meet business requirements.
+     * ### Resource availability and scheduling
      *
-     * ### Status requirements
+     * Marking a booking as `PENDING` immediately affects resource availability:
      *
-     * - __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).
+     * - **Calendar impact**: The booking appears on the business calendar.
+     * - **Availability**: The time slot becomes unavailable for other bookings, even while pending approval.
+     * - **Resource assignment**: Available [resources](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/resources-v2/introduction) are automatically assigned if none were explicitly selected during booking creation.
      *
-     * ### Checkout restrictions
+     * ### Double bookings
      *
-     * 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.
+     * By default, the method doesn't check for availability conflicts. To detect and handle double bookings, use the `checkAvailabilityValidation: true` admin overwrite.
      *
-     * ### Additional updates
+     * ### Notify customers
      *
-     * - __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.
+     * You can specify a `participantNotification.message` for the customer.
+     * To send the message, you must also specify `participantNotification.notifyParticipants` as `true`.
      *
-     * Refer to [Decline Booking](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` | `multiServiceBooking.bookings.${number}.booking.totalParticipants` | `multiServiceBooking.bookings.${number}.booking.status` | `multiServiceBooking.bookings.${number}.booking.paymentStatus` | `multiServiceBooking.bookings.${number}.booking.selectedPaymentOption` | `multiServiceBooking.bookings.${number}.booking.createdBy.anonymousVisitorId` | `multiServiceBooking.bookings.${number}.booking.createdBy.memberId` | `multiServiceBooking.bookings.${number}.booking.createdBy.wixUserId` | `multiServiceBooking.bookings.${number}.booking.createdBy.appId`, 7> & {
-        __applicationErrorsType?: DeclineMultiServiceBookingApplicationErrors;
-    }>;
-}
-declare function bulkGetMultiServiceBookingAllowedActions$1(httpClient: HttpClient): BulkGetMultiServiceBookingAllowedActionsSignature;
-interface BulkGetMultiServiceBookingAllowedActionsSignature {
-    /**
-     * Retrieves information about which actions the customer can perform for up to 50 multi-service bookings.
+     * ### Admin overwrites
      *
+     * There are small but important differences when you specify special
+     * `flowControlSettings`:
      *
-     * 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.
+     * - `{"checkAvailabilityValidation": true}`: Checks for double booking conflicts before updating the status.
+     * When conflicts exist, the booking is still marked as `PENDING` and `doubleBooked` is set to `true` for the business to resolve manually.
+     * - `{"skipPendingApprovalServiceValidation": true}`: Allows marking any booking as pending, even if the service doesn't require manual approval.
      *
-     * Bear the following considerations in mind when calling this method:
+     * When using special `flowControlSettings`, ensure you have sufficient permissions.
+     * If you encounter failed calls due to insufficient permissions, consider the following options:
      *
-     * __Real-time validation__: Wix Bookings calculates allowed actions based on current multi-service booking status, [booking policies](https://dev.wix.com/docs/rest/business-solutions/bookings/policies/booking-policies/introduction), and [available resources](https://dev.wix.com/docs/rest/business-solutions/bookings/resources/resources-v2/introduction) at the time of the call.
+     * - __App developers__ can use a higher
+     * [permission](https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions), such as `MANAGE BOOKINGS - ALL PERMISSIONS`.
+     * - __Site developers__ can utilize
+     * [elevation](https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/authorization/elevation).
      *
-     * __Permission context__: Depending on the permissions of the calling [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/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.
+     * Granting additional permissions and using elevation permits method calls that would typically fail due to authorization checks.
+     * Therefore, you should use them intentionally and securely.
+     * @param - ID of the booking to mark as `PENDING`.
+     * @param - Revision number, which increments by 1 each time the booking is updated.
      *
-     * __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.
+     * To prevent conflicting changes, the current revision must be specified when
+     * managing the booking.
      */
-    (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`, 6>>;
+    (bookingId: string, revision: string, options?: MarkBookingAsPendingOptions): Promise<NonNullablePaths<MarkBookingAsPendingResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7> & {
+        __applicationErrorsType?: MarkBookingAsPendingApplicationErrors;
+    }>;
 }
-declare function getMultiServiceBooking$1(httpClient: HttpClient): GetMultiServiceBookingSignature;
-interface GetMultiServiceBookingSignature {
+declare function getAnonymousActionDetails$1(httpClient: HttpClient): GetAnonymousActionDetailsSignature;
+interface GetAnonymousActionDetailsSignature {
     /**
-     * Retrieves a multi-service booking and all its associated single-service bookings.
-     *
-     *
-     * 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](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 - ID of the multi-service booking.
-     * @returns Retrieved multi-service booking.
+     * Returns booking details related to AnonymousActions
+     * Anonymous tokens for getting, canceling or rescheduling the booking.
+     * That token is symmetrically encrypted and Url-safe.
+     * That allows the UoU to cancel or reschedule without Authentication.
+     * @returns Response for GetAnonymousActionDetails
      */
-    (multiServiceBookingId: string): Promise<NonNullablePaths<MultiServiceBooking, `bookings` | `bookings.${number}.booking.totalParticipants` | `bookings.${number}.booking.status` | `bookings.${number}.booking.paymentStatus` | `bookings.${number}.booking.selectedPaymentOption` | `bookings.${number}.booking.createdBy.anonymousVisitorId` | `bookings.${number}.booking.createdBy.memberId` | `bookings.${number}.booking.createdBy.wixUserId` | `bookings.${number}.booking.createdBy.appId`, 6>>;
+    (options?: GetAnonymousActionDetailsOptions): Promise<GetAnonymousActionDetailsResponse>;
 }
-declare function addBookingsToMultiServiceBooking$1(httpClient: HttpClient): AddBookingsToMultiServiceBookingSignature;
-interface AddBookingsToMultiServiceBookingSignature {
+declare function cancelBookingAnonymously$1(httpClient: HttpClient): CancelBookingAnonymouslySignature;
+interface CancelBookingAnonymouslySignature {
     /**
-     * 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](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
-     *
-     * - __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.
+     * Cancel booking using an anonymous token
+     * @param - The token provided in the booking links for anonymous access
+     * @returns Response for CancelBookingAnonymously
      */
-    (multiServiceBookingId: string, options?: NonNullablePaths<AddBookingsToMultiServiceBookingOptions, `bookings` | `bookings.${number}.bookingId` | `bookings.${number}.revision`, 4>): Promise<NonNullablePaths<AddBookingsToMultiServiceBookingResponse, `bookings` | `bookings.${number}.booking.totalParticipants` | `bookings.${number}.booking.status` | `bookings.${number}.booking.paymentStatus` | `bookings.${number}.booking.selectedPaymentOption` | `bookings.${number}.booking.createdBy.anonymousVisitorId` | `bookings.${number}.booking.createdBy.memberId` | `bookings.${number}.booking.createdBy.wixUserId` | `bookings.${number}.booking.createdBy.appId`, 6> & {
-        __applicationErrorsType?: AddBookingsToMultiServiceBookingApplicationErrors;
-    }>;
+    (token: string, options?: CancelBookingAnonymouslyOptions): Promise<NonNullablePaths<CancelBookingAnonymouslyResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7>>;
 }
-declare function removeBookingsFromMultiServiceBooking$1(httpClient: HttpClient): RemoveBookingsFromMultiServiceBookingSignature;
-interface RemoveBookingsFromMultiServiceBookingSignature {
+declare function rescheduleBookingAnonymously$1(httpClient: HttpClient): RescheduleBookingAnonymouslySignature;
+interface RescheduleBookingAnonymouslySignature {
     /**
-     * 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](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/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.
-     *
-     * __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 - ID of the multi-service booking.
+     * Reschedule booking using an anonymous token
+     * @param - The token provided in the booking links for anonymous access
+     * @param - New slot of the booking.
+     * @returns Response for RescheduleBookingAnonymously
      */
-    (multiServiceBookingId: string, options?: RemoveBookingsFromMultiServiceBookingOptions): Promise<NonNullablePaths<RemoveBookingsFromMultiServiceBookingResponse, `bookings` | `bookings.${number}.booking.totalParticipants` | `bookings.${number}.booking.status` | `bookings.${number}.booking.paymentStatus` | `bookings.${number}.booking.selectedPaymentOption` | `bookings.${number}.booking.createdBy.anonymousVisitorId` | `bookings.${number}.booking.createdBy.memberId` | `bookings.${number}.booking.createdBy.wixUserId` | `bookings.${number}.booking.createdBy.appId`, 6> & {
-        __applicationErrorsType?: RemoveBookingsFromMultiServiceBookingApplicationErrors;
-    }>;
+    (token: string, slot: V2Slot, options: NonNullablePaths<RescheduleBookingAnonymouslyOptions, `revision`, 2>): Promise<NonNullablePaths<RescheduleBookingAnonymouslyResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId`, 7>>;
+}
+declare function getBookingAnonymously$1(httpClient: HttpClient): GetBookingAnonymouslySignature;
+interface GetBookingAnonymouslySignature {
+    /**
+     * Get booking using an anonymous token
+     * @param - The token provided in the booking links for anonymous access
+     * @returns Response for GetBookingAnonymously
+     */
+    (token: string): Promise<NonNullablePaths<GetBookingAnonymouslyResponse, `booking.totalParticipants` | `booking.participantsChoices.serviceChoices` | `booking.bookedEntity.slot.serviceId` | `booking.bookedEntity.slot.scheduleId` | `booking.bookedEntity.slot.resource._id` | `booking.bookedEntity.slot.location.locationType` | `booking.bookedEntity.schedule.scheduleId` | `booking.bookedEntity.tags` | `booking.contactDetails.fullAddress.streetAddress.number` | `booking.contactDetails.fullAddress.streetAddress.name` | `booking.contactDetails.fullAddress.streetAddress.apt` | `booking.contactDetails.fullAddress.subdivisions` | `booking.contactDetails.fullAddress.subdivisions.${number}.code` | `booking.contactDetails.fullAddress.subdivisions.${number}.name` | `booking.additionalFields` | `booking.additionalFields.${number}._id` | `booking.additionalFields.${number}.valueType` | `booking.status` | `booking.paymentStatus` | `booking.selectedPaymentOption` | `booking.createdBy.anonymousVisitorId` | `booking.createdBy.memberId` | `booking.createdBy.wixUserId` | `booking.createdBy.appId` | `booking.bookedAddOns` | `booking.bookedAddOns.${number}._id` | `booking.bookedAddOns.${number}.groupId` | `allowedActionsAnonymously.cancel` | `allowedActionsAnonymously.reschedule`, 7>>;
 }
 declare const onBookingCanceled$1: EventDefinition<BookingCanceledEnvelope, "wix.bookings.v2.booking_canceled">;
 declare const onBookingConfirmed$1: EventDefinition<BookingConfirmedEnvelope, "wix.bookings.v2.booking_confirmed">;
 declare const onBookingCreated$1: EventDefinition<BookingCreatedEnvelope, "wix.bookings.v2.booking_created">;
 declare const onBookingDeclined$1: EventDefinition<BookingDeclinedEnvelope, "wix.bookings.v2.booking_declined">;
-declare const onBookingNumberOfParticipantsUpdated$1: EventDefinition<BookingNumberOfParticipantsUpdatedEnvelope, "wix.bookings.v2.booking_number_of_participants_updated">;
 declare const onBookingRescheduled$1: EventDefinition<BookingRescheduledEnvelope, "wix.bookings.v2.booking_rescheduled">;
 declare const onBookingUpdated$1: EventDefinition<BookingUpdatedEnvelope, "wix.bookings.v2.booking_updated">;
+declare const onBookingNumberOfParticipantsUpdated$1: EventDefinition<BookingNumberOfParticipantsUpdatedEnvelope, "wix.bookings.v2.booking_number_of_participants_updated">;
 
-declare const getAnonymousActionDetails: MaybeContext<BuildRESTFunction<typeof getAnonymousActionDetails$1> & typeof getAnonymousActionDetails$1>;
-declare const cancelBookingAnonymously: MaybeContext<BuildRESTFunction<typeof cancelBookingAnonymously$1> & typeof cancelBookingAnonymously$1>;
-declare const rescheduleBookingAnonymously: MaybeContext<BuildRESTFunction<typeof rescheduleBookingAnonymously$1> & typeof rescheduleBookingAnonymously$1>;
-declare const getBookingAnonymously: MaybeContext<BuildRESTFunction<typeof getBookingAnonymously$1> & typeof getBookingAnonymously$1>;
 declare const confirmOrDeclineBooking: MaybeContext<BuildRESTFunction<typeof confirmOrDeclineBooking$1> & typeof confirmOrDeclineBooking$1>;
 declare const bulkConfirmOrDeclineBooking: MaybeContext<BuildRESTFunction<typeof bulkConfirmOrDeclineBooking$1> & typeof bulkConfirmOrDeclineBooking$1>;
-declare const createBooking: MaybeContext<BuildRESTFunction<typeof createBooking$1> & typeof createBooking$1>;
-declare const bulkCreateBooking: MaybeContext<BuildRESTFunction<typeof bulkCreateBooking$1> & typeof bulkCreateBooking$1>;
-declare const rescheduleBooking: MaybeContext<BuildRESTFunction<typeof rescheduleBooking$1> & typeof rescheduleBooking$1>;
-declare const confirmBooking: MaybeContext<BuildRESTFunction<typeof confirmBooking$1> & typeof confirmBooking$1>;
-declare const setBookingSubmissionId: MaybeContext<BuildRESTFunction<typeof setBookingSubmissionId$1> & typeof setBookingSubmissionId$1>;
-declare const updateExtendedFields: MaybeContext<BuildRESTFunction<typeof updateExtendedFields$1> & typeof updateExtendedFields$1>;
-declare const declineBooking: MaybeContext<BuildRESTFunction<typeof declineBooking$1> & typeof declineBooking$1>;
-declare const cancelBooking: MaybeContext<BuildRESTFunction<typeof cancelBooking$1> & typeof cancelBooking$1>;
-declare const updateNumberOfParticipants: MaybeContext<BuildRESTFunction<typeof updateNumberOfParticipants$1> & typeof updateNumberOfParticipants$1>;
-declare const markBookingAsPending: MaybeContext<BuildRESTFunction<typeof markBookingAsPending$1> & typeof markBookingAsPending$1>;
 declare const createMultiServiceBooking: MaybeContext<BuildRESTFunction<typeof createMultiServiceBooking$1> & typeof createMultiServiceBooking$1>;
 declare const rescheduleMultiServiceBooking: MaybeContext<BuildRESTFunction<typeof rescheduleMultiServiceBooking$1> & typeof rescheduleMultiServiceBooking$1>;
 declare const getMultiServiceBookingAvailability: MaybeContext<BuildRESTFunction<typeof getMultiServiceBookingAvailability$1> & typeof getMultiServiceBookingAvailability$1>;
@@ -916,6 +902,20 @@ declare const bulkGetMultiServiceBookingAllowedActions: MaybeContext<BuildRESTFu
 declare const getMultiServiceBooking: MaybeContext<BuildRESTFunction<typeof getMultiServiceBooking$1> & typeof getMultiServiceBooking$1>;
 declare const addBookingsToMultiServiceBooking: MaybeContext<BuildRESTFunction<typeof addBookingsToMultiServiceBooking$1> & typeof addBookingsToMultiServiceBooking$1>;
 declare const removeBookingsFromMultiServiceBooking: MaybeContext<BuildRESTFunction<typeof removeBookingsFromMultiServiceBooking$1> & typeof removeBookingsFromMultiServiceBooking$1>;
+declare const createBooking: MaybeContext<BuildRESTFunction<typeof createBooking$1> & typeof createBooking$1>;
+declare const bulkCreateBooking: MaybeContext<BuildRESTFunction<typeof bulkCreateBooking$1> & typeof bulkCreateBooking$1>;
+declare const rescheduleBooking: MaybeContext<BuildRESTFunction<typeof rescheduleBooking$1> & typeof rescheduleBooking$1>;
+declare const confirmBooking: MaybeContext<BuildRESTFunction<typeof confirmBooking$1> & typeof confirmBooking$1>;
+declare const setBookingSubmissionId: MaybeContext<BuildRESTFunction<typeof setBookingSubmissionId$1> & typeof setBookingSubmissionId$1>;
+declare const updateExtendedFields: MaybeContext<BuildRESTFunction<typeof updateExtendedFields$1> & typeof updateExtendedFields$1>;
+declare const declineBooking: MaybeContext<BuildRESTFunction<typeof declineBooking$1> & typeof declineBooking$1>;
+declare const cancelBooking: MaybeContext<BuildRESTFunction<typeof cancelBooking$1> & typeof cancelBooking$1>;
+declare const updateNumberOfParticipants: MaybeContext<BuildRESTFunction<typeof updateNumberOfParticipants$1> & typeof updateNumberOfParticipants$1>;
+declare const markBookingAsPending: MaybeContext<BuildRESTFunction<typeof markBookingAsPending$1> & typeof markBookingAsPending$1>;
+declare const getAnonymousActionDetails: MaybeContext<BuildRESTFunction<typeof getAnonymousActionDetails$1> & typeof getAnonymousActionDetails$1>;
+declare const cancelBookingAnonymously: MaybeContext<BuildRESTFunction<typeof cancelBookingAnonymously$1> & typeof cancelBookingAnonymously$1>;
+declare const rescheduleBookingAnonymously: MaybeContext<BuildRESTFunction<typeof rescheduleBookingAnonymously$1> & typeof rescheduleBookingAnonymously$1>;
+declare const getBookingAnonymously: MaybeContext<BuildRESTFunction<typeof getBookingAnonymously$1> & typeof getBookingAnonymously$1>;
 /**
  * Triggered when a booking is canceled.
  */
@@ -932,10 +932,6 @@ declare const onBookingCreated: BuildEventDefinition<typeof onBookingCreated$1>
  * Triggered when a booking is declined.
  */
 declare const onBookingDeclined: BuildEventDefinition<typeof onBookingDeclined$1> & typeof onBookingDeclined$1;
-/**
- * Triggered when the number of participants is updated.
- */
-declare const onBookingNumberOfParticipantsUpdated: BuildEventDefinition<typeof onBookingNumberOfParticipantsUpdated$1> & typeof onBookingNumberOfParticipantsUpdated$1;
 /**
  * Triggered when a booking is rescheduled.
  */
@@ -944,5 +940,9 @@ declare const onBookingRescheduled: BuildEventDefinition<typeof onBookingResched
  * Triggered when a booked schedule is updated.
  */
 declare const onBookingUpdated: BuildEventDefinition<typeof onBookingUpdated$1> & typeof onBookingUpdated$1;
+/**
+ * Triggered when the number of participants is updated.
+ */
+declare const onBookingNumberOfParticipantsUpdated: BuildEventDefinition<typeof onBookingNumberOfParticipantsUpdated$1> & typeof onBookingNumberOfParticipantsUpdated$1;
 
 export { AddBookingsToMultiServiceBookingApplicationErrors, AddBookingsToMultiServiceBookingOptions, AddBookingsToMultiServiceBookingResponse, Booking, BookingCanceledEnvelope, BookingConfirmedEnvelope, BookingCreatedEnvelope, BookingDeclinedEnvelope, BookingNumberOfParticipantsUpdatedEnvelope, BookingRescheduledEnvelope, BookingUpdatedEnvelope, BulkConfirmOrDeclineBookingApplicationErrors, BulkConfirmOrDeclineBookingOptions, BulkConfirmOrDeclineBookingRequestBookingDetails, BulkConfirmOrDeclineBookingResponse, BulkCreateBookingApplicationErrors, BulkCreateBookingOptions, BulkCreateBookingResponse, BulkGetMultiServiceBookingAllowedActionsResponse, CancelBookingAnonymouslyOptions, CancelBookingAnonymouslyResponse, CancelBookingApplicationErrors, CancelBookingOptions, CancelBookingResponse, CancelMultiServiceBookingApplicationErrors, CancelMultiServiceBookingOptions, CancelMultiServiceBookingResponse, ConfirmBookingApplicationErrors, ConfirmBookingOptions, ConfirmBookingResponse, ConfirmMultiServiceBookingApplicationErrors, ConfirmMultiServiceBookingOptions, ConfirmMultiServiceBookingResponse, ConfirmOrDeclineBookingApplicationErrors, ConfirmOrDeclineBookingOptions, ConfirmOrDeclineBookingResponse, CreateBookingApplicationErrors, CreateBookingInfo, CreateBookingOptions, CreateBookingResponse, CreateMultiServiceBookingApplicationErrors, CreateMultiServiceBookingOptions, CreateMultiServiceBookingResponse, DeclineBookingApplicationErrors, DeclineBookingOptions, DeclineBookingResponse, DeclineMultiServiceBookingApplicationErrors, DeclineMultiServiceBookingOptions, DeclineMultiServiceBookingResponse, GetAnonymousActionDetailsOptions, GetAnonymousActionDetailsResponse, GetBookingAnonymouslyResponse, GetMultiServiceBookingAvailabilityApplicationErrors, GetMultiServiceBookingAvailabilityResponse, MarkBookingAsPendingApplicationErrors, MarkBookingAsPendingOptions, MarkBookingAsPendingResponse, MarkMultiServiceBookingAsPendingApplicationErrors, MarkMultiServiceBookingAsPendingOptions, MarkMultiServiceBookingAsPendingResponse, MultiServiceBooking, RemoveBookingsFromMultiServiceBookingApplicationErrors, RemoveBookingsFromMultiServiceBookingOptions, RemoveBookingsFromMultiServiceBookingResponse, RescheduleBookingAnonymouslyOptions, RescheduleBookingAnonymouslyResponse, RescheduleBookingApplicationErrors, RescheduleBookingInfo, RescheduleBookingOptions, RescheduleBookingResponse, RescheduleMultiServiceBookingApplicationErrors, RescheduleMultiServiceBookingOptions, RescheduleMultiServiceBookingResponse, SetBookingSubmissionIdApplicationErrors, SetBookingSubmissionIdResponse, UpdateExtendedFieldsApplicationErrors, UpdateExtendedFieldsOptions, UpdateExtendedFieldsResponse, UpdateNumberOfParticipantsApplicationErrors, UpdateNumberOfParticipantsOptions, UpdateNumberOfParticipantsResponse, V2Slot, addBookingsToMultiServiceBooking, bulkConfirmOrDeclineBooking, bulkCreateBooking, bulkGetMultiServiceBookingAllowedActions, cancelBooking, cancelBookingAnonymously, cancelMultiServiceBooking, confirmBooking, confirmMultiServiceBooking, confirmOrDeclineBooking, createBooking, createMultiServiceBooking, declineBooking, declineMultiServiceBooking, getAnonymousActionDetails, getBookingAnonymously, getMultiServiceBooking, getMultiServiceBookingAvailability, markBookingAsPending, markMultiServiceBookingAsPending, onBookingCanceled, onBookingConfirmed, onBookingCreated, onBookingDeclined, onBookingNumberOfParticipantsUpdated, onBookingRescheduled, onBookingUpdated, removeBookingsFromMultiServiceBooking, rescheduleBooking, rescheduleBookingAnonymously, rescheduleMultiServiceBooking, setBookingSubmissionId, updateExtendedFields, updateNumberOfParticipants };