A schedule entry is a booked block of time on the dispatch calendar. Create and update entries, search across them, and check any entry for booking conflicts.
Create a booking with POST /schedules, then read, update, or remove it through /schedules/{id}. Before you commit to a slot, GET /schedules/{id}/conflicts reports overlaps with other bookings so you can resolve double-booking.
GET /schedules lists entries, and GET /schedules/search narrows the calendar to a window, a technician, or a query.
All schedule endpoints check the user_schedule RBAC resource. Use user_schedule:read to list and retrieve entries; user_schedule:update is required to create, modify, or delete them. The schedule resource name is not the same thing and will not grant access to these endpoints.
Non-admin callers are automatically scoped to entries they own or are assigned to. Passing a user_id filter to view another user's entries has no effect unless the caller holds an admin role with user_schedule:update.
Every endpoint links through to its full parameters, request and response schemas, and code samples.
GET/api/v1/schedulesAlgaPSAList schedule entriesPOST/api/v1/schedulesAlgaPSACreate schedule entryGET/api/v1/schedules/{id}AlgaPSAGet schedule entryPUT/api/v1/schedules/{id}AlgaPSAUpdate schedule entryDELETE/api/v1/schedules/{id}AlgaPSADelete schedule entryGET/api/v1/schedules/{id}/conflictsAlgaPSAGet schedule conflictsGET/api/v1/schedules/searchAlgaPSASearch schedules