Notifications

In-app notifications (the "bell") are a per-user feed of events addressed to a specific cabinet user (for example, being assigned to a deal or to a deal task). This is the REST side of the same stream that arrives in real time as the `notification.created` event on the user's personal WebSocket channel: use the socket for the live push and badge, and these endpoints to backfill history on app load, read the unread count, and clear the badge. The feed is scoped to the current user and their active company (`current_company_id`): the list, the counter, and "mark all" return only notifications for the active company; marking a single notification read resolves it by the owning user regardless of company. Notification object: `id` (UUID string), `type` (a snake_case string identifying the notification kind — the platform currently emits `deal_assigned` and `deal_task_assigned`, and the set will grow), `title` (short heading), `body` (string or `null`), `data` (an object whose fields depend on `type` — e.g. `deal_id`/`deal_title` for `deal_assigned`), `read_at` (ISO timestamp when read, or `null` while unread), `created_at`. Important about the list response shape: `GET /v1/notifications` returns the standard Laravel paginator envelope — the array under the `data` key, with the pagination meta fields (`current_page`, `per_page`, `total`, `last_page`, `next_page_url`, etc.) sitting flat at the top level. This differs from most REST groups, where a list comes back as `data:{ items, pagination }`. Query parameters: `filter=unread` (return only unread; any other value or omitting it returns all) and `per_page` (page size, default 20). Note the snake_case `per_page` (not `perPage`).