> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkato.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Mark notification read

> Mark one of the authorized member’s notifications read.

Mark one of the authorized member’s notifications read.

Use an OAuth access token issued to `kato-raycast`. Developer keys cannot call this endpoint. See [Raycast authentication](/api-reference/raycast/overview).

Required scopes: `notifications:write`.

Unavailable notifications return `404`. An already read notification remains read.

## Parameters

<ParamField path="notificationId" type="string" required>
  Notification ID addressed to the authorized member.
</ParamField>

## Response

**200** — Returns the resource under `data`. Example IDs and values are illustrative.

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": {
      "id": "notification_example",
      "isRead": true
    }
  }
  ```
</ResponseExample>

<RequestExample>
  ```bash Request theme={null}
  curl --fail-with-body --silent --show-error \
    "https://api.getkato.io/v1/raycast/notifications/$KATO_NOTIFICATION_ID/read" \
    -H "Authorization: Bearer $KATO_RAYCAST_ACCESS_TOKEN" \
    -X POST
  ```
</RequestExample>

Set path-ID environment variables to values returned by your workspace before running the request.

This request changes workspace data. A timeout does not prove that the write failed; inspect the result before retrying.


## Related topics

- [All endpoints](/api-reference/endpoints.md)
- [Mark all notifications read](/api-reference/raycast/notifications-read-all.md)
- [Mark notification unread](/api-reference/raycast/notifications-unread.md)
- [Dismiss a read notification](/api-reference/raycast/notifications-dismiss.md)
- [List notifications](/api-reference/raycast/notifications.md)