@wix/auto_sdk_bookings_bookings 1.0.83 → 1.0.84

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -249,7 +249,20 @@ interface BookedEntityItemOneOf {
249
249
  schedule?: BookedSchedule;
250
250
  }
251
251
  interface BookedSlot {
252
- /** Session ID. */
252
+ /**
253
+ * Session ID. For class bookings, this is the ID of the existing session.
254
+ * For appointment bookings, this field is typically empty during booking creation and gets populated when the booking is confirmed.
255
+ *
256
+ * __Migration Guidance__: Replace usage of this field with `eventId` from the [Time Slots V2 API](https://dev.wix.com/docs/api-reference/business-solutions/bookings/time-slots/time-slots-v2/introduction).
257
+ * You can follow [these sample flows](https://dev.wix.com/docs/api-reference/business-solutions/bookings/end-to-end-booking-flows) for step-by-step guidance about determining availability and creating bookings.
258
+ * @deprecated Session ID. For class bookings, this is the ID of the existing session.
259
+ * For appointment bookings, this field is typically empty during booking creation and gets populated when the booking is confirmed.
260
+ *
261
+ * __Migration Guidance__: Replace usage of this field with `eventId` from the [Time Slots V2 API](https://dev.wix.com/docs/api-reference/business-solutions/bookings/time-slots/time-slots-v2/introduction).
262
+ * You can follow [these sample flows](https://dev.wix.com/docs/api-reference/business-solutions/bookings/end-to-end-booking-flows) for step-by-step guidance about determining availability and creating bookings.
263
+ * @replacedBy event_id
264
+ * @targetRemovalDate 2026-03-31
265
+ */
253
266
  sessionId?: string | null;
254
267
  /** Service ID. */
255
268
  serviceId?: string;
@@ -4102,20 +4115,19 @@ interface BulkConfirmOrDeclineBookingOptions {
4102
4115
  *
4103
4116
  * ### Appointment booking
4104
4117
  *
4105
- * For appointment-based services, specify the relevant `slot` in
4106
- * `bookedEntity.slot`. We recommend specifying the complete
4107
- * `availabilityEntries.slot` returned in [Query Availability](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/availability-calendar/query-availability)
4108
- * in your call's request to avoid failed calls due to unavailability.
4118
+ * For appointment-based services, specify the relevant time slot in `bookedEntity.slot`.
4119
+ *
4120
+ * 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.
4121
+ * Specify the slot's `startDate`, `endDate`, `resource`, and `location` in `booking.bookedEntity.slot`.
4109
4122
  *
4110
4123
  * ### Class session booking
4111
4124
  *
4112
- * For class services, specify the relevant [event ID](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction)
4113
- * as `bookedEntity.slot.eventId`.
4114
- * We recommend retrieving the event ID from [Query Availability's](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/availability-calendar/query-availability)
4115
- * `availabilityEntries.slot.eventId` to avoid failed calls due to unavailability.
4116
- * Specifying an event ID leads to automatic calculations of `slot.startDate`, `slot.endDate`,
4117
- * `slot.timezone`, `slot.resource`, and `slot.location`. All manually specified
4118
- * values are overridden.
4125
+ * For class services, specify the relevant event ID as `bookedEntity.slot.eventId`.
4126
+ *
4127
+ * 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.
4128
+ * Specify the `eventId` from the selected time slot in `booking.bookedEntity.slot.eventId`.
4129
+ *
4130
+ * When you specify `eventId`, Wix Bookings automatically derives `startDate`, `endDate`, `timezone`, `resource`, and `location` based on the event details. Manually specified values are ignored.
4119
4131
  *
4120
4132
  * ### Course booking
4121
4133
  *
@@ -4172,6 +4184,8 @@ interface BulkConfirmOrDeclineBookingOptions {
4172
4184
  * don't match, Create Booking fails. Therefore, we recommend specifying
4173
4185
  * only `booking.contactDetails.contactId` when providing `formSubmission`.
4174
4186
  *
4187
+ * You can follow [this sample flow](https://dev.wix.com/docs/api-reference/business-solutions/bookings/wix-forms-integration#create-a-booking-with-a-filled-out-booking-form) to create bookings with booking form submissions.
4188
+ *
4175
4189
  * ### Admin overwrites
4176
4190
  *
4177
4191
  * There are small but important differences when you specify special