Discussions

Hi Daylite Team,

We're investigating an issue reported by a mutual customer regarding our Daylite integration and would like to better understand the expected behavior of the Daylite API.

The customer observed the following:

Some Daylite appointments correctly block availability in our scheduling application, while others do not.
The issue appears to affect recurring appointments, particularly occurrences that have been modified individually (for example, a single occurrence whose date or time has been changed).
The customer also noticed that changing the appointment's Category (e.g. from "Ask to Book" to "Consulting") caused the appointment to start being recognized by our integration.
Based on your API documentation, we understand that recurring events have certain limitations. However, we'd appreciate clarification on the following:

1. Recurring appointments
   Are modified ("orphaned") occurrences of recurring appointments returned through the Daylite API?
   If not, is this a known limitation?
2. Appointment Categories
   Does the Daylite API expose all appointment categories equally?
   Is there any scenario where an appointment's category affects whether it is returned by the API or marked as Busy?
3. Busy status
   Should all Daylite appointments marked as Busy be returned consistently through the API, regardless of their category?
   Are there any appointment types or categories that are intentionally excluded?
4. Best practice
   Is there anything we should be aware of when consuming Daylite appointments for availability/conflict checking?
   We're trying to determine whether the behavior observed by the customer is an expected limitation of the API or whether there may be something else we should investigate on our side.

Any clarification would be greatly appreciated.

Sincerely,