We have added resource allocation functionality to the API endpoints and to the availability functionality.

• Add validation for name length on POST/PUT /setup/v1/locations endpoints to prevent
  500 error. Now limits name to 50 chars
• Fix issue with using offset on GET /consumer/v1/locations, GET /setup/v1/locations,
  and GET /setup/v1/locations/{id}/services
• Enforces limits on GET endpoints which return collections, as defined in the endpoint
  documentation. In most cases the limit is 100, with GET /consumer/v1/services being
  an exception.
• Added length validation to phone number input to prevent numbers being truncated by our database. Phone numbers must be a minimum of 7 characters with a maximum of 15 characters. Our API does not validate the spacing or characters used in the phone field. We recommend that you only post the numbers in the phone field and manage the formatting of it within your application. The assumption is that formatting is handled by the consumer of the API.
• Add recurringAvailability parameter to Resources response and input options. Defaults to true when not supplied
• Add fix for Availability bug, which could occasionally occur, when calling with dates spanning from Dec 31 to Jan 1
• Update lastModifiedOn of old appointment and createDate of new appointment when rescheduling

• Add recurringAvailability parameter to Resources response and input options. Defaults to true when not supplied
• Add hotfix for Availability bug, which could occasionally occur, when calling with dates spanning from Dec 31 to Jan 1
• Update lastModifiedOn of old appointment and createDate of new appointment when rescheduling

• Add validation for name length on POST/PUT /setup/v1/locations endpoints to prevent
  500 error. Now limits name to 50 chars
• Fix issue with using offset on GET /consumer/v1/locations, GET /setup/v1/locations,
  and GET /setup/v1/locations/{id}/services
• Enforces limits on GET endpoints which return collections, as defined in the endpoint
  documentation. In most cases the limit is 100, with GET /consumer/v1/services being
  an exception.
• Add length validation to phone number input to prevent numbers being truncated by our
  database

• Fixes booking webhook content where parameters listed did not match those in the documentation
• Send webhook from POST /consumer/v1/appointments when completeBooking=BK
• Prevent POST /consumer/v1/appointments from throwing a 500 error when using resourceIds parameter
• Update Swagger documentation formatting in GET /consumer/v1/appointments/{id}
• Update Swagger documentation PUT /consumer/v1/appointments/{id}/reschedule
• Update Swagger documentation formatting for GET /consumer/v1/availability
• Fixes PUT /appointments/{id}/reschedule endpoint to correctly update resourceId and serviceId when submitted. You now have the ability to swap out resources or services on appointments.

• Fixes PUT /appointments/{id}/reschedule endpoint to correctly update resourceId and serviceId when submitted.  You now have the ability to swap out resources or services on appointments.
• Fixes booking webhook content where parameters listed did not match those in the documentation

• Send webhook from POST /consumer/v1/appointments when completeBooking=BK
• Prevent POST /consumer/v1/appointments from throwing a 500 error when using resourceIds parameter
• Update Swagger documentation formatting in GET /consumer/v1/appointments/{id}
• Update Swagger documentation PUT /consumer/v1/appointments/{id}/reschedule
• Update Swagger documentation formatting for GET /consumer/v1/availability

• Removed maxCapacity and maxGroupSize from Locations input and output models until they can be made useful in the availability calculations
• Updated Swagger docs for POST /setup/v1/locations

Major Change Notification - OnSched API on .Net 5.0

• Fixed an issue with GET /setup/businessUsers/{email}/companies endpoint, which was causing an error with OnSched Dashboard. The bug returned duplicate results after NET5 upgrade.
• Fixed GET /setup/v1/locations/{id}/services endpoint which returned 500 error when trying to associate services to locations via POST.