HomeBook an Intro CallStartup Program
What's New
Back to All

Feb 10, 2022 - v2022.3

about 3 years ago by Mike
  • Issue #251: Include publicHolidayId in list of location.businessHolidays for location responses
  • Issue #286: Fix to POST /setup/v1/locations/bulk which prevents save of any locations if one location contains a validation error
  • Issue #316: Prevent location from having multiple default services. Location may still have 2 defaults if one is company scoped and the other is location scoped
  • Issue #575: Add endpoints to set/update appointment reminder schedule for a location. New endpoints GET/PUT /setup/v1/locations/{id}/appointmentreminders
  • Issue #588: Update BOOKING-138 error message to give more detail about how much capacity was requested and how much capacity currently exists
  • Issue #775: Prevent PUT ​/consumer​/v1​/appointments​/{id}​/book and PUT /consumer/v1/appointments/{id}/reserve from wiping out customer name when set in POST call. Added email validations to email addresses supplied during appointment processing.
  • Issue #764: Fix problem where PUT /consumer/v1/appointments/{id}/reschedule was removing multi-resource booking information
  • Issue #818: Add ResourceEmail to complement the existing resourceId and resourceName in the appointment response payload for consumer appointments endpoints
  • Issue #906: Fix erroneous timezone offset in appointment response payloads when using PUT /consumer/v1/appointments/{id}/book
  • Issue #918: Update POST /setup/v1/locations to default new
  • Issue #942: Update POST /setup/v1/services to prevent 500 error when options object not supplied
  • Issue #945: Prevent email validation in issue #775 if the customer has turned company.disableEmailAndSmsNotifications = true (EMAIL IS OFF)
  • Issue #952: Update PUT /consumer/v1/appointments/{id}/reschedule to properly handle customerBookingsPerDay parameter when rescheduling
  • Issue #965: Update PUT /setup/v1/resources/{id} to allow resource to correctly store notificationType
  • Issue #978: Prevent PUT /consumer/v1/appointments/{id}/book from wiping out value of groupSize parameter when finalizing a booking
  • Issue #969: Validate order of reminders when using POST/PUT /setup/v1/locations/{id}/appointmentreminders