Schedules
Update a schedule
Partial update — only send the fields you want to change. Unset fields keep their current value. Recomputes and re-materializes future occurrences when recurrence fields change. An edit that would remove upcoming shifts saves nothing and answers 409 confirm_remove_required with the removed days and a confirm_token; once the user agrees, resend the same edit with confirm_remove: true and that confirm_token. Does NOT change the roster: use POST /schedules/{id}/roster for that. Requires the schedules:write scope.
patch/api/v1/schedules/{id}
Request
- Base URL: https://volunteerreminder.com
- URL: https://volunteerreminder.com/api/v1/schedules/{id}
- Auth: HTTP bearer
Path parameters
idstring required
The schedule's numeric id.
Example:42
Request body
Example request
{
"description": "Sunday morning greeters",
"job_name": "Greeter",
"schedule_type": "weekly",
"days_of_week": [
"sunday"
],
"nth_weekday": "tuesday",
"week_of_month": 2,
"day_of_month": 15,
"start_month": 1,
"time": "09:00",
"custom_dates": [
"2026-08-01",
"2026-09-05"
],
"confirm_remove": true,
"confirm_token": "crm_3f2a9c1e5b7d4a608e1f2c3b4a5d6e7f"
}Response
The updated schedule.
Example response
{
"id": 42,
"description": "Sunday morning greeters",
"schedule_type": "weekly",
"days_of_week": [
"sunday"
],
"nth_weekday": "tuesday",
"time": "09:00",
"custom_dates": [
"2026-08-01",
"2026-09-05"
],
"contact_ids": [
101,
102
]
}Changes
No recorded changes to this operation across all 1 revision of this API.