Skip to main content
PATCH
Mark personal notifications
Write access: a member/administrator with a write-enabled credential, or an authorized signed-in user. Mark selected notifications or all notifications present at the request snapshot as read/unread. Repeated read marks preserve the first read time. Choose ids OR all:true. Choose ids or all:true, never both. read defaults to true; false marks unread. All applies to the request snapshot, leaving later arrivals unread. Repeated read marks preserve the original receipt time. Team API keys cannot mutate personal notifications. MCP clients can use mark_notifications for this operation. Request conventions · API keys · MCP connections

Authorizations

Authorization
string
header
required

Personal or team Mill REST API key

Headers

Origin
string<uri>

The exact configured Mill UI origin. Required for browser mutations carrying session cookies.

Idempotency-Key
string

Reuse the same key and exact request bytes for retries of one logical mutation; different content conflicts.

Required string length: 8 - 128
Pattern: ^[A-Za-z0-9._:-]+$

Body

application/json
ids
string<uuid>[]
Required array length: 1 - 100 elements
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
all
boolean
read
boolean

Response

Successful response. Examples are illustrative; field values vary by record.

Illustrative response shape. Fields can be absent in alternate successful flows; see the operation description and example.

ok
boolean
updated
integer