This article shares possible use cases your app could support, along with sample flows that could guide each use case. Use this as a starting point as you plan your app's implementation.
Allow business owners to manage schedules within your app.
To manage a calendar:
appId
, we recommend to also pass
name
. Save the ID of the created schedule.scheduleId
, start
, and end
times.appId
.Your app can help business owners keep their external calendar up to date with their Wix calendars.
To synchronize to the external system:
actionEvent
type, create, update, or delete
the corresponding event in the external calendar:
eventAddedOrUpdated
: Create or update the event in the external calendar
if its revision
is higher than that of the event stored in the external
calendar.eventRemoved
: Soft delete the event in the external calendar to avoid
inconsistencies, as a hard delete might cause a mismatch if an updated
event arrives later than a delete event.endDate
of the Wix calendar's event view.endDate
value from the event view as toLocalDate
.fromLocalDate
as needed.Enable business owners to manage their events' participation details through a dashboard. Note that Wix Bookings automatically provides this functionality.
To create a participant dashboard:
fromLocalDate
and toLocalDate
as filters.Your app could extend Wix Bookings functionality by blocking time across multiple Bookings resources.
To block Bookings resources:
name
and the Bookings appId
. Then, save the
returned scheduleId
.start
and end
time, the scheduleId
, and all relevant
resourceId
s. To make the blocked time recurring, also provide a
recurrenceRule
.