Webhooks

Work Request Events

LifeLoop emits work request events — a work request was created, updated, deleted, or commented on. Webhook event for work requests. resourceId is the work request id — fetch it via GET /residents/{residentId}/work-requests/{resourceId} as the resident (a connection can fetch it only if a connection created it). These events are planned (v2.0 Priority-2 contract draft) and not yet delivered.

Events

Event type	Triggered when
work_request.created	Fired when a work request is created for a resident.
work_request.updated	Fired when a work request for a resident changes: its details, its status, its schedule, or the assigned crew.
work_request.deleted	Fired when staff delete a work request in LifeLoop.
work_request.comment_created	Fired when a comment is added to a work request for a resident, including staff-only comments that the API will not return.

What to do after receiving this event

Check the X-API-KEY header.
Read resourceId from the payload — this is the requestId.
Call GET /api/v1/{tenant}/residents/{residentId}/work-requests/{resourceId} to fetch the full object.
Update your local data store.
Return HTTP 200.

← Back to Webhooks Overview

Sample payloadwork_request.created.json

{
  "eventType": "work_request.created",
  "aggregateType": "work_request",
  "occurredAt": "2026-06-18T10:30:00Z",
  "tenant": "sunrise-001",
  "eventId": "f3a91bc2-4d12-4e88-a1c3-8f2901dd7c94",
  "resourceId": "req-001"
}

Fetch the full objectbash

curl https://api.lifeloop.com/api/v1/sunrise-001/residents/res-001/work-requests/req-001 \
  -H "Authorization: Bearer YOUR_SERVICE_TOKEN" \
  -H "X-Acting-User-Id: ACTING_USER_ID" \
  -H "X-Acting-User-Tenant: sunrise-001"