GET
Notifications feed

Overview

The in-app notification feed shown on the Notifications screen. Every event that wakes the device with a push (a new mutual match, new chat messages, a listing going live, tenancy status changes) also writes a persistent notification row for the recipient, so the feed and the push stay in sync. Each item carries a read flag. The client groups unread items under “New” and read items under “Earlier” (matching the Figma). unreadCount powers the bell badge on the home header.
Notifications are written best-effort alongside the domain write — a match/message is never rolled back if the feed write fails. Conversely, the global notification mute suppresses push delivery only; in-app notifications are still recorded so the user sees them when they open the app.

Notification types

Authentication

Bearer <accessToken> required on every route. requireAuth + requireOnboarded applied.

GET /me/notifications — list

Newest-first, cursor-paginated by createdAt.

Query parameters

Response — 200 OK


POST /me/notifications/:id/read — mark one read

Idempotent. Returns { "updated": boolean } (false if it was already read or not found). 200 OK.

POST /me/notifications/read-all — mark all read

Returns { "count": <number marked> }. 200 OK.

DELETE /me/notifications/:id — delete one

Idempotent. Returns { "removed": boolean }. 200 OK.

DELETE /me/notifications — clear all

Deletes every notification for the user. Returns { "count": <number removed> }. 200 OK.

Error responses

See also

curl