Preview recurring requests (dry run)

Answer what POST /requests/recurring would do with this payload without creating anything: the number of occurrences, the summed workday duration and its split by fiscal year, whether the member's allowance covers the whole series, and the per-occurrence conflicts.

Input: identical to POST /requests/recurring. files is accepted and ignored. reason, admin_approval_option, ignoreMaximumAbsence and representative_member_ids are validated exactly as on create.

Duration: duration.workday_absence_duration follows the same days-vs-minutes rule as workday_absence_duration on GET /requests and is the sum over all occurrences; preview and created series always agree. per_year splits that sum by fiscal year.

Allowance: is_allowance_sufficient is one verdict for the whole series, matching the all-or-nothing behaviour of POST /requests/recurring: false means creating the series fails with the allowance error and leaves nothing behind. Leave types that do not deduct return true.

Conflicts: conflicts lists occurrences overlapping the member's existing requests, department_limit_conflicts the occurrences on which a department's maximum absent limit is already reached, representative_overlaps the occurrences on which the member is someone else's representative (pending or accepted), and representative_unavailable the occurrences on which a passed representative is absent.

Rejection: when the payload would be rejected with 400 by POST /requests/recurring, the response is still 200 with rejection set and can_create: false. Match on rejection.code: neither until nor count given (RECURRENCE_END_REQUIRED), day/month/pos/weekDays not matching repeat (RECURRENCE_RULE_INVALID), a series reaching more than 365 days into the future (RECURRENCE_WINDOW_EXCEEDED), fewer than two occurrences (RECURRENCE_TOO_FEW_OCCURRENCES), an hour-based leave type without a valid start_time/end_time (HOUR_LEAVE_TYPE_REQUIRES_TIME_RANGE), a half_day on a full-day-only leave type (HALF_DAY_NOT_ALLOWED_FOR_FULL_DAY_LEAVE_TYPE), or an occurrence outside the member's employment period (OUTSIDE_EMPLOYMENT_PERIOD). After that the rules the create endpoint applies to every occurrence follow, in its order: a leave type disabled for the member (LEAVE_TYPE_DISABLED), a missing or too long reason (REASON_REQUIRED, REASON_TOO_LONG), an occurrence outside the bookable fiscal-year window (OUTSIDE_FISCAL_YEAR_WINDOW) or too far in the past for the caller's role (PAST_DATE_NOT_ALLOWED), an occurrence on which a non-admin is someone else's accepted representative (REPRESENTATIVE_CONFLICT), a leave type needing approval while the member has no approver (NO_APPROVER_SET), and the representative requirement (REPRESENTATIVES_INVALID, REQUIRED_REPRESENTATIVES_COUNT_NOT_MET). A workspace without the Essentials plan, or a non-admin passing admin_approval_option: approve_request_immediately, gets the same 403 as the create endpoint.

Verdict: can_create is true only when rejection is null, conflicts is empty, department_limit_conflicts is empty (or the caller is an admin passing ignoreMaximumAbsence) and the allowance covers the series. representative_unavailable is informational.

Side effects: no request, approver, notification, webhook or calendar sync entry is created. Safe to repeat; each call evaluates the data as it is at that moment.