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

Jan 23, 2022 - v2022.2

over 3 years ago by Mike
  • Correctly load environment-specific appsettings.json
  • Fix Issue #217: When calling POST /setup/v1/service the response did not contain either a companyId or locationId
  • Fix Issue #601: When calling POST /setup/v1/resources or POST /setup/v1/services, availability was not correctly set to the business default in some cases
  • Fix Issue #408: When calling PUT /setup/v1/company/{id} now correctly saves Webhook information (bookingWebhookUrl, customerWebhookUrl, reminderWebhookUrl, reminderWebhookUrl)
  • Fix Issue #873: When calling POST /consumer/v1/appointments, the customer name was being incorrectly stored when passing more than 2 names. Now all words after the first will be included in the lastName field
  • Fix Issue #775: Add email validations to PUT /consumer/v1/appointments/{id}/book and PUT /consumer/v1/appointments/{id}/reserve
  • Fix Issue #792: When calling POST /consumer/v1/appointments, PUT /consumer/v1/appointments/{id}/book or PUT /consumer/v1/appointments/{id}/reserve, we will now only create a customer when Location:Defaults:AutoUpdateCustomer parameter is set to true. This has the behaviour in the Portal application and now the API matches this functionality
  • Fix Issue #585: When calling POST /consumer/v1/appointments, the bookingLimit specified by a ServiceAllocation will now correctly override the information stored on Service:BookingLimit or Calendar:BookingsPerSlot values
  • Fix Issue #358: When calling POST /setup/v1/calendars/{id}/block now correctly validates startTime < endTime
  • Fix Issue #890: Where calling GET /consumer/v1/availability/.../unavailable would throw a 500 error when no resources exist on location
  • Fix Issue #882: Fix CustomerBookingsPerDay validation in ResourceAllocation functionality which would cause errors when using PUT /consumer/v1/appoinments/{id}/book or PUT /consumer/v1/appointments/{id}/reserve or PUT /consumer/v1/appointments/{id}/confirm
  • Fix Issue #882: Add validation for CustomerBookingsPerDay to POST /consumer/v1/appointments when completeBooking set to BK or RS
  • Fix Issue #790: When calling POST /setup/v1/services/{id}/allocations without a locationId, the primary location will be assumed if the service is company scoped, the location attached to the service will be assumed if the service is location scoped, or a validation error will be thrown if the locationId passed is not valid for the service