Notification API Reference

Overview

Notification API endpoints live under apps/zooly-app/app/api/notifications/. All user-facing endpoints require cookie-based authentication via resolveAccountId. All endpoints support CORS based on ALLOWED_DOMAINS_CORS.

---

List Notifications

Returns recent notifications and unread count for the authenticated user.

Endpoint: GET /api/notifications/list

Auth: Required (cookie-based)

Query Parameters:

Response (200):

Errors: 401 — not authenticated

Implementation: apps/zooly-app/app/api/notifications/list/route.ts

---

Mark Notifications as Read

Marks one or all notifications as read for the authenticated user.

Endpoint: POST /api/notifications/mark-read

Auth: Required (cookie-based)

Request Body — one of:

Response (200): { success: true }

Errors:

• 400 — neither notificationId nor all provided
• 404 — notification not found or does not belong to the authenticated user

Implementation: apps/zooly-app/app/api/notifications/mark-read/route.ts

---

Process Email Notifications (Cron)

Picks up unsent notification emails, resolves recipient email via Cognito, and sends via SendGrid.

Endpoint: GET /api/notifications/process-emails

Auth: None (designed for cron scheduler)

Behavior:

1. Fetches up to 20 notifications where emailSent = false
2. For each notification, looks up the account's ownerUserId and calls Cognito AdminGetUser to get the email
3. Sends email via sendNotificationEmail() from @zooly/app-srv
4. On success, calls markEmailSent(notificationId) to prevent re-sending
5. Failed sends are logged but do not block processing of remaining notifications

Response (200):

Implementation: apps/zooly-app/app/api/notifications/process-emails/route.ts

---

Related Documentation

• Notification System Overview — architecture and adding new notification types
• Offers API Reference — offer endpoints that create notifications