Block Slots

Calendar and employee availability blocks.

📄️ Get block slot by ID

Returns a single block slot by its primary key.

📄️ Update block slot

Full replacement of an existing block slot. The calendarId / employeeId exclusivity rule applies to the new state.

📄️ Delete block slot

Removes the block. Unlike appointments, a block has no history worth preserving, so this is a physical delete.

📄️ Merge-patch block slot

RFC 7396 merge-patch over `application/merge-patch+json`. Send only the fields you want to change; include a field with value `null` to remove it. Use the `If-Match` header for optimistic concurrency control.

📄️ List block slots

Returns a paginated list of block slots with envelope `{data, totalCount, skip, limit, hasMore}`. Default sort is `startAt:asc`. Limit is capped at 200; skip is clamped to >= 0.

📄️ Create block slot

Creates a block. Exactly one of `calendarId` / `employeeId` must be set; supplying both or neither returns 400. The owning company is derived from the target and must be inside the caller's scope.