Notifications Journey
A member manages their notification preferences (shown in Account Page) and views their notification feed (shown in Home Dashboard banner).
Sequence Diagram
API Reference
| Step | Service | Method | Path | Auth | Response |
|---|---|---|---|---|---|
| Get token | Keycloak | POST | /realms/olly/protocol/openid-connect/token | None | access_token |
| Get preferences | notifications | GET | /preferences/{partyLocator} | Member JWT | 200 or 404 |
| Update preferences | notifications | PUT | /preferences/{partyLocator} | Member JWT | 200 |
| List notifications | notifications | GET | /notifications/list | Member JWT | 200 {notifications:[...]} |
| Notification log | notifications | GET | /log/list | Member JWT | 200 {log:[...]} |
Notes
GET /preferences/{partyLocator}returns 404 if the party has never set preferences — the test skips in this case (requires seeder to have run).- Preference field names are camelCase:
email,sms,push,claimsUpdates,billingAlerts,enrollmentReminders. GET /preferences(without party locator) also exists and returns preferences for the authenticated user's own party.