May 16, 2022 - v2022.8

  • Issue #241: Update Swagger comments for PUT /setup/v1/locations/{id}/settings/scope/{settingsScope} endpoint
  • Issue #321: Fix issue where PUT /setup/v1/locations/{id}/settings/scope/{settingsScope} was incorrectly storing data when altering scopes
  • Issue #447: Add setup endpoints for ServiceGroups
  • Issue #520: Update POST /setup/v1/services to validate MaxCapacity and MaxGroupSize are both either 0 or both are greater than 0. One cannot be set without the other
  • Issue #560: Add consumer endpoints for ResourceGroups
  • Issue #561: Resolve an issue where passing an endDate=9999-12-31 and endTime=2400 in POST /setup/v1/services/allocations threw an error
  • Issue #610: Add validation to POST /setup/v1/locations to prevent names > 50 char
  • Issue #910: Add deprecation notice to locations endpoints notifying customers that we will change the settings: businessId property to settings: locationId. During the transition period both properties will be returned
  • Issue #946: Prevent an appointment with status=IN from being created when POST appointment fails a email/name validation when using completeBooking
  • Issue #954: POST /setup/v1/services/allocations prevent error from occuring when posting with endDate: 9999-12-31 and endTime: 2400
  • Issue #1007: Fix error where GET /consumer/v1/locations would throw a 500 error in certain scoping situations. We have prevented those situations from happening with issue #321, but wanted to exclude the possiblity of a 500 error being thrown
  • Issue #1010: Add validation for TimezoneName to POST/PUT /setup/v1/companies endpoints to enforce IANA names only
  • Issue #1079: Alter POST/PUT /setup/v1/locations to alter availability functionality. When setting is24hours: true, we will set fromTime: 0, toTime: 2400, and isOpen: true irrespective of the values passed in. That is to say, is24Hours: true takes precedence over other availability settings.
  • Issue #1199: Add missing IANA time validation for America/Phoenix
  • Issue #1220: Update POST/PUT /setup/v1/services to remove the validation check durationInterval >= durationMin. A new validation has been added to assure durationMin is evenly divisible into durationMax. GET /consumer/v1/availability has been updated to assure that serviceDuration is between durationMin and durationMax if durationSelect: true
  • Issue #1257: Add deprecation warning for all locations endpoints concerning the following parameters on the settings object: businessId, enabled, familyMembersEnabled, serviceLabel, resourceLabel, resourceAnyLabel, resourceSelection, liveMode, formFlow, availabilityForm, showServiceGroups, showOnSchedLogo, showBusinessLogo, disableAuthorization, hideNavBar, hideLocationNav, hideServiceGroupsNav, hideServicesNav, hideContinueBooking, returnToService, returnToAvailability, hideBreadCrumbNav. These parameters were intended for internal use in our Portal application. They will be removed from the API sometime after Aug 15.