HomeBook an Intro CallCreate a Support TicketStartup Program
Back to All

April 7, 2022 - v2022.6

about 2 years ago by Mike
  • Issue #387: Add better validation errors when a 401 error is caused by unauthorized resource, service or location ids
  • Issue 562: Update documentation for GET /consumer/v1/settings to note that this endpoint is DEPRECATED
  • Issue #567: Update POST /setup/v1/services/{serviceId}/allocations Swagger documentation
  • Issue #598: Update POST /setup/v1/companies to add validation for TimezoneName, which is a required field
  • Issue #992, #1135: Update /consumer/v1/appointments endpoints to unify logic for multi-resource booking and single resource booking
  • Issue #949: Fix response output for POST /consumer/v1/appointments to correctly show input timezone when completeBooking: 'BK' or 'RS' is passed
  • Issue #1013: Update GET /consumer/v1/locations and GET /setup/v1/locations to allow searching by location friendlyId parameter. This will allow searching locations when customers use GUIDs as friendlyIds
  • Issue #1064: Clarify Swagger documentation for PUT /consumer/v1/appointments/{id}/reschedule
  • Issue #1088: Add PUT /setup/v1/resources/{id}/services endpoint to allow updating resource services instead of deleting and posting new ones
  • Issue #1115: Add skipTimePastUnavailability parameter to GET /consumer/v1/availability/..../unavailable to exclude Time Past (TP) blocks in data.
  • Issue #1119: Update PUT /consumer/v1/appointments/{id}/reschedule to allow both resourceId and serviceId to be altered in 1 call
  • Issue #1120: Update POST /consumer/v1/appointments and PUT /consumer/v1/appointments/{id}/reschedule to fix issue where it was incorrectly calculating the remaining group capacity and throwing an invalid validation error
  • Issue #1121: Update POST /setup/v1/resources/{id}/allocations to display startDate/endDate as Date objects, instead of DateTime objects
  • Issue #1122: Update GET /setup/v1/resources/{id}/allocations, GET /setup/v1/resources/allocations/{id}, and PUT /setup/v1/resources/allocations/{id} to display startDate/endDate as Date objects, instead of DateTime objects
  • Issue #1123: Update DELETE /setup/v1/resources/allocations/{id} to display startDate/endDate as Date objects, instead of DateTime objects
  • Issue #1125: Correct issue where UnavailableTime stored procedure was returning resource allocations in UTC time when the resource did not have a timezone set