Webhooks

Transportation Request Events

LifeLoop emits transportation request events — a transportation request was created, updated, deleted, or commented on. Webhook event for transportation requests. resourceId is the request id — fetch it via GET /residents/{residentId}/transportation-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 typeTriggered when
transportation_request.createdFired when a transportation request is created.
transportation_request.updatedFired when a transportation request changes: its details, its status (approved, denied, cancelled, completed), or the assigned driver or vehicle.
transportation_request.deletedFired when staff delete a transportation request in LifeLoop.
transportation_request.comment_createdFired when a comment is added to a transportation request, including staff-only comments that the API will not return.

What to do after receiving this event

  1. Check the X-API-KEY header.
  2. Read resourceId from the payload — this is the requestId.
  3. Call GET /api/v1/{tenant}/residents/{residentId}/transportation-requests/{resourceId} to fetch the full object.
  4. Update your local data store.
  5. Return HTTP 200.
← Back to Webhooks Overview
Sample payloadtransportation_request.created.json
{
  "eventType": "transportation_request.created",
  "aggregateType": "transportation_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/transportation-requests/req-001 \
  -H "Authorization: Bearer YOUR_SERVICE_TOKEN" \
  -H "X-Acting-User-Id: ACTING_USER_ID" \
  -H "X-Acting-User-Tenant: sunrise-001"