Update a calendar
Changes the settings you name.
The merged calendar is validated, not your patch. A change that is fine on its own can still produce an invalid calendar, such as dropping every weekly window, or a slot duration longer than the shortest window it has to fit in. That is refused, and errors says why.
_id and locationId are not patchable, so a calendar cannot be moved between sub-accounts.
Changing hours does not move appointments that are already booked outside them. They stay, and the seat they hold stays taken.
Cookie-auth callers must send the x-csrf-token header.
Required API key scope: projects:write.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Path Parameters
The calendar id.
1Query Parameters
The sub-account this calendar belongs to. It is the only thing that identifies the tenant here, and access is re-checked against it on every call.
Body
The settings to change.
A calendar to create, or the parts of one to change. On an update the MERGED calendar is validated, not the patch.
"Consultations"
Required on create.
"America/Chicago"
x >= 1x >= 1x >= 0x >= 1x >= 0x >= 1