---
title: "PATCH /v1/notifications/{id}/read"
method: PATCH
path: "/v1/notifications/{id}/read"
tags: ["Notifications"]
---

# PATCH /v1/notifications/{id}/read

`PATCH /v1/notifications/{id}/read`

## Request

- Base URL: `https://api.arbital.xyz` (the document declares no server; this is the origin it was published from)
- URL: `https://api.arbital.xyz/v1/notifications/{id}/read`
- Auth: HTTP bearer

Idempotently acknowledges currently authorized, unsuppressed activity on one owned notification through the requested activity revision. Hidden activity is not individually acknowledged. Legacy bodyless requests acknowledge the server-observed boundary and return 204. A prior mark-all cutoff remains effective independently.

## Path parameters

- `id` string, uuid, required

## Query parameters

- `contract` '2'

## Request body

- object
  - `through_activity_revision` string, required

## Response `200`

Authorized notification response

- NotificationSingleReadV2
  - `unread_count` string, required
  - `inbox_revision` string, required
  - `read_watermark` string, uuid, required
  - `read_watermark_expires_at_unix_ms` integer, required
  - `read_state` 'read' | 'unread', required

## Other responses

- `204`: Notification marked read
- `401`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `404`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `503`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.

---

[API](https://skmtc.dev/arbital/apis/arbital-api.md) - [All operations](https://skmtc.dev/arbital/apis/arbital-api/llms.txt) - [OpenAPI document](https://skmtc.dev/arbital/apis/arbital-api/revisions/bb0185edf43a?raw)