Asks what the scheduling rules say about a claim, without writing anything. A proposal item gives an employeeId and a shiftId and asks what happens if the employee took the shift, and a reference item gives a shiftClaimId and asks whether that pending claim could be approved. Each item names the actions to decide, and gets one evaluation per action, evaluated with the shift's published times and the employee's published commitments. A reference is evaluated for its claimant and shift as they are now. The operation writes nothing and reserves nothing. A result never authorizes a write: claiming and approving evaluate again when they commit. An employee is evaluated for the shifts GET /api/v1/scheduling/open-shifts would list for them, so a shift that is not open to the employee, or a projected occurrence that has no row yet, fails its item with invalid_shift_id. The one exception is a shift starting on a day the employee has no active employment status: the list leaves it out, and this operation evaluates it and blocks it with EMPLOYEE_NOT_ACTIVE, or with RESTRICTED_REASON when the caller may not see the employee's employment status. A reference is accepted for exactly the claims GET /api/v1/scheduling/shift-claims would show the caller. An employee, shift or claim that does not exist and one the caller may not see fail identically. A blocked outcome is shown to the claimant and the approver alike, and findings and coverage a caller may not see are withheld. Returns 200 when every item was evaluated and 207 when any item failed, including when every item did. A request holds at most 100 items, and proposals and references may be mixed. Evaluating fails with open_shifts_disabled while Open Shifts is off.

OAuth Scopes: scheduling:shifts