---
name: givegigs-account-notifications
description: Read your account profile and manage contact and notification preferences.
---

# Account & Notifications

Commander can use these session-backed user endpoints. The existing routes verify the signed-in owner and validate changes. Every change still requires a separate confirmation in Valley CMDR.

- `GET /api/user/details` - Read the current account's exposed profile details.
- `GET /api/user/contact-preferences` - Read contact visibility and preferences.
- `PATCH /api/user/contact-preferences` - Update your own contact preferences.
- `GET /api/user/priority-notices` - Read notices delivered to your account.
- `POST /api/user/priority-notices` - Acknowledge one of your notices with `{ "noticeId": "..." }`.
- `GET /api/notifications?limit=20` - List your notifications.
- `GET /api/notifications/count` - Read your unread count.
- `GET /api/notifications/read-all/cutoff` - Read the current read-all cutoff.
- `PATCH /api/notifications/{notificationId}` - Mark your notification read.
- `DELETE /api/notifications/{notificationId}` - Remove your notification.
- `POST /api/notifications/read-all` - Mark your notifications read.
- `GET/PATCH /api/notifications/preferences` - Read or update your own notification settings and thread mutes.

Use the Commander panel's **Browser push notifications** control to enable or disable push on this device. It uses the browser's native permission prompt and sends the generated subscription directly to the existing push endpoint; the token is not sent to Valley. Internal notification processing, unsubscribe tokens, and push delivery endpoints are not model tools. API keys cannot use these session-only account routes.

The route validates fields and ownership; do not provide passwords, session cookies, API keys, or push secrets in chat.