Count Unread Notifications
How many of the caller's notifications are unread (the bell's badge).
API key access
notifications:read scope with an API key (ro_pat_...). A signed-in session uses the caller's role./api/v1/notifications/unread-countAccess token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Header Parameters
Id of the workspace to act on (must be a member).
Response Body
curl -X GET "http://localhost:8000/api/v1/notifications/unread-count" \ -H "X-Workspace-Id: string"{
"unread_count": 0
}Rebuild Knowledge Graph
Queue a replay of this workspace's deterministic knowledge-graph ingestion (admin+): what the rules derived from leads and the timeline (edges, `rules@v1` facts) is deleted and folded again from the start; LLM-extracted facts are kept and nothing is re-extracted. One rebuild per workspace waits at a time: while one is queued or running, it is returned (`created: false`).
List Notifications
The caller's in-app notifications (their own, the workspace's, and the admins' for owners and admins), unread first, then newest first, with the unread count. Written by the core when a mailbox or sending domain auto-pauses or its health drops, a signal rule fires, an export is ready, a research batch finishes, a webhook endpoint is auto-disabled or a privacy export completes. Kept `NOTIFICATIONS_RETENTION_DAYS` (default 90).