@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.
@@ -71,20 +71,19 @@ interface CreateBookingSignature {
71
71
  *
72
72
  * ### Appointment booking
73
73
  *
74
- * For appointment-based services, specify the relevant `slot` in
75
- * `bookedEntity.slot`. We recommend specifying the complete
76
- * `availabilityEntries.slot` returned in [Query Availability](https://dev.wix.com/docs/rest/business-solutions/bookings/time-slots/availability-calendar/query-availability)
77
- * in your call's request to avoid failed calls due to unavailability.
74
+ * For appointment-based services, specify the relevant time slot in `bookedEntity.slot`.
75
+ *
76
+ * 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.
77
+ * Specify the slot's `startDate`, `endDate`, `resource`, and `location` in `booking.bookedEntity.slot`.
78
78
  *
79
79
  * ### Class session booking
80
80
  *
81
- * For class services, specify the relevant [event ID](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction)
82
- * as `bookedEntity.slot.eventId`.
83
- * 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)
84
- * `availabilityEntries.slot.eventId` to avoid failed calls due to unavailability.
85
- * Specifying an event ID leads to automatic calculations of `slot.startDate`, `slot.endDate`,
86
- * `slot.timezone`, `slot.resource`, and `slot.location`. All manually specified
87
- * values are overridden.
81
+ * For class services, specify the relevant event ID as `bookedEntity.slot.eventId`.
82
+ *
83
+ * 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.
84
+ * Specify the `eventId` from the selected time slot in `booking.bookedEntity.slot.eventId`.
85
+ *
86
+ * When you specify `eventId`, Wix Bookings automatically derives `startDate`, `endDate`, `timezone`, `resource`, and `location` based on the event details. Manually specified values are ignored.
88
87
  *
89
88
  * ### Course booking
90
89
  *
@@ -141,6 +140,8 @@ interface CreateBookingSignature {
141
140
  * don't match, Create Booking fails. Therefore, we recommend specifying
142
141
  * only `booking.contactDetails.contactId` when providing `formSubmission`.
143
142
  *
143
+ * 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.
144
+ *
144
145
  * ### Admin overwrites
145
146
  *
146
147
  * There are small but important differences when you specify special