Skip to main content

Leave request

Represents a vacation, leave, or sick-day request: employee (employeeId), absence class (type, e.g. vacation vs sick), finer reason (absenceReason), date range, duration in days or hours, workflow state (status), half-day flags, notes, and approval trail (approvedById, approvedAt). The sample shows vacation (type: vacation); sick leave typically uses values such as sick and reasons that match policy and the target connector.

Full JSON example​

{
  "id": "lr_1Ab4Cd7Ef0Gh3",
  "channel": "demoipaas",
  "createdAt": "2026-02-01T11:00:00+00:00",
  "updatedAt": "2026-02-05T14:30:00+00:00",
  "employeeId": "emp_4Hy7Jk0Lm3No6",
  "employeeNumber": "EMP-01482",
  "type": "vacation",
  "absenceReason": "annual_leave",
  "startDate": "2026-03-10",
  "endDate": "2026-03-14",
  "durationDays": 5,
  "durationHours": null,
  "status": "approved",
  "halfDayStart": false,
  "halfDayEnd": false,
  "notes": "Approvato da HR; copertura turni concordata.",
  "approvedById": "emp_9Qr2St5Uv8Wx1",
  "approvedAt": "2026-02-05T14:30:00+00:00"
}

Remarkable notes​

  • Allowed values for type, absenceReason, and status depend on the HR workflow and mapping to the destination (draft, pending, approved, rejected, cancelled).
  • durationDays may be recalculated when holidays fall inside the range or when only durationHours is used.
  • Medical certificates or legally protected absences may require extra fields (e.g. case numbers, attachments) beyond the sample.