Sick Leave Handling

When a candidate reports sick in Seamlr, the integration supports two scenarios.

Gig Worker Sick Leave

When a gig worker reports sick, Seamlr notifies the provider and creates a replacement shift.

Webhook from Seamlr

Event: candidate.sick_leave

{
  "event": "candidate.sick_leave",
  "providerId": "550e8400-e29b-41d4-a716-446655440000",
  "content": {
    "shiftId": "6ba7b810-9dad-11d1-80b4-00c04fd430c8",
    "candidateId": "6ba7b811-9dad-11d1-80b4-00c04fd430c8",
    "reportedAt": "2024-01-15T06:00:00Z",
    "action": "keep_shift_create_replacement"
  },
  "traceId": "6ba7b812-9dad-11d1-80b4-00c04fd430c8"
}

Provider Actions

1. Keep original shift marked as “sick” (for payroll/reporting)

2. Seamlr creates a new searchable replacement shift

---

Permanent Staff Sick Leave

When permanent staff reports sick via the provider system, the provider requests Seamlr to find a replacement.

Webhook from Provider

Event: shift.sick_leave_replacement

{
  "event": "shift.sick_leave_replacement",
  "providerId": "550e8400-e29b-41d4-a716-446655440000",
  "content": {
    "shiftId": "6ba7b810-9dad-11d1-80b4-00c04fd430c8",
    "originalCandidateId": "6ba7b811-9dad-11d1-80b4-00c04fd430c8",
    "reportedAt": "2024-01-15T06:00:00Z"
  },
  "traceId": "6ba7b812-9dad-11d1-80b4-00c04fd430c8"
}

Flow

1. Permanent employee reports sick via provider system

2. Provider sends webhook to Seamlr requesting replacement

3. Original shift remains in provider for sick reporting (cannot be deleted)

4. Seamlr creates searchable replacement shift

Compliance Note

Sick leave handling ensures compliance with labor reporting requirements. The original shift must be preserved for accurate sick leave tracking.

Field Reference

Field	Type	Description
shiftId	string (UUID)	The affected shift
candidateId / originalCandidateId	string (UUID)	The sick candidate
reportedAt	string (ISO 8601)	When sickness was reported
action	string	Action to take (gig worker only)