Webhooks
Notification Events
LifeLoop emits notification events — a user-facing notification was triggered (reminders, new messages, cancellations). Shared schema for every notification.* event. Exactly one event fires per eligible notification, regardless of how many recipients it reaches. resourceId's meaning varies by notification type — see each notification.* operation's own description, not this shared text. Fires only when at least one recipient has that notification type enabled in their own settings; a notification with no eligible recipients is silent.
Events
| Event type | Triggered when |
|---|---|
| notification.activity_cancellation | Fired once, regardless of recipient count, when a resident or connection is notified that a group activity they were registered for was cancelled — and at least one recipient has this notification type enabled. |
| notification.registration_reminder | Fired ahead of an upcoming activity a resident or connection is registered for, when at least one recipient has this notification type enabled. |
| notification.new_message | Fired when a resident or connection is notified of a new message, when at least one recipient has this notification type enabled. |
| notification.new_announcement | Fired when a resident or connection is notified of a new announcement, when at least one recipient has this notification type enabled. |
| notification.newsletter_published | Fired when a resident or connection is notified that a newsletter was published, when at least one recipient has this notification type enabled. |
| notification.transportation_reminder | Fired when a resident or connection is sent this LifeLoop notification and at least one recipient has it enabled. |
| notification.transportation_creator_update | Fired when a resident or connection is sent this LifeLoop notification and at least one recipient has it enabled. |
| notification.transportation_comment | Fired when a resident or connection is sent this LifeLoop notification and at least one recipient has it enabled. |
| notification.work_request_creator_update | Fired when a resident or connection is sent this LifeLoop notification and at least one recipient has it enabled. |
| notification.work_request_comment | Fired when a resident or connection is sent this LifeLoop notification and at least one recipient has it enabled. |
What to do after receiving this event
- Check the
X-API-KEYheader. - Read
resourceIdfrom the payload — this is thenotificationId. - Call
Depends on the notification typeto fetch the full object. - Update your local data store.
- Return
HTTP 200.
Note: Notification events signal that LifeLoop would notify a user. Use the event type to decide which related resource to re-read.
Sample payloadnotification.activity_cancellation.json
{
"eventType": "notification.activity_cancellation",
"aggregateType": "notification",
"occurredAt": "2026-06-18T10:30:00Z",
"tenant": "sunrise-001",
"eventId": "f3a91bc2-4d12-4e88-a1c3-8f2901dd7c94",
"resourceId": "ntf-001"
}Fetch the full objectbash
# Re-read the resource relevant to this notification type