API Request | Schedules GET (multiple) add DateTStamp param

[rinse-dental]

Hello - I would like to request an update to Schedules GET (multiple) API. Please add DateTStamp as an optional param that, when used, follows the same behavior used in the Appointments GET (multiple) API.

DateTStamp: String in "yyyy-MM-dd HH:mm:ss" format. Only include schedules with a DateTStamp altered after the specified date and time. This provides a good way for you to keep a synchronized copy of schedules.

Thank you.

[justine]

Hello - I would like to request an update to Schedules GET (multiple) API. Please add DateTStamp as an optional param that, when used, follows the same behavior used in the Appointments GET (multiple) API.

DateTStamp: String in "yyyy-MM-dd HH:mm:ss" format. Only include schedules with a DateTStamp altered after the specified date and time. This provides a good way for you to keep a synchronized copy of schedules.

Thank you.

Hello rinse-dental,

I have added looking into this to our API development list. However, the schedules GET endpoint already contains robust date filtering. Have you considered setting up a schedules database event?

Thanks!

[rinse-dental]

I have added looking into this to our API development list. However, the schedules GET endpoint already contains robust date filtering. Have you considered setting up a schedules database event?

Thank you for asking. Yes, I use the schedules database event now though I'm realizing now that DateTStamp won't solve my problem. My issue is, when you add/remove ops from a schedule (e.g. blockout), it does not fire a database event.

Is it possible to request a scheduleop database event? Or perhaps there is a better solution to see/hear when and ops are added/removed from a blockout?