Notifications

Mark Notification Read

Mark one notification read for the caller (idempotent: their first `read_at` stays). Read state is per member: a workspace-wide notification stays unread for the other members.

API key access

Needs the notifications:write scope with an API key (ro_pat_...). A signed-in session uses the caller's role.
POST/api/v1/notifications/{notification_id}/read
AuthorizationBearer <token>

Access 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

Path Parameters

notification_idstring
Formatuuid

Header Parameters

X-Workspace-Id?string | null

Id of the workspace to act on (must be a member).

Response Body

curl -X POST "http://localhost:8000/api/v1/notifications/497f6eca-6276-4993-bfeb-53cbbbba6f08/read" \  -H "X-Workspace-Id: string"
{
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "kind": "mailbox_paused",
  "severity": "info",
  "title": "Export ready: reachout-leads-20261019-101500.csv",
  "body": "string",
  "link": "string",
  "resource_type": "string",
  "resource_id": "4d5215ed-38bb-48ed-879a-fdb9ca58522f",
  "lead_id": "9bddab70-98e6-43a9-8f32-c9788b9de0c0",
  "personal": true,
  "read_at": "2019-08-24T14:15:22Z",
  "created_at": "2019-08-24T14:15:22Z"
}
Empty
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string",
      "input": null,
      "ctx": {}
    }
  ]
}