Skip to main content
Documentation

Domain

Scheduling capabilities

7 capabilities, all acting on a slot. A reference to one from another domain is spelled slot_id — never a bare id — and every one of those fields names the capability that produces it, so a model can chain calls without guessing.
CapabilityWhat it doesEffect
scheduling.calendarPOST /api/v1/scheduling/calendarList the booked appointment slots between two dates, earliest firstread-only
scheduling.suggest_slotsPOST /api/v1/scheduling/suggest_slotsRank the best slot for a job across bays, installers and marginread-only
scheduling.stationsPOST /api/v1/scheduling/stationsList the bays and lifts a slot can be scheduled intoread-only
scheduling.time_offPOST /api/v1/scheduling/time_offList who is off and cannot be given a slot in a windowread-only
scheduling.travel_estimatePOST /api/v1/scheduling/travel_estimateEstimate the drive between two mobile jobs before booking a slotread-only
scheduling.overbooked_daysPOST /api/v1/scheduling/overbooked_daysFind the days already booked past the shop's own slot ceilingread-only
scheduling.readinessPOST /api/v1/scheduling/readinessCheck whether this shop can have a slot scheduled at allread-only

← Every domain