Mark a notification as read
PATCH/api/v1/notifications/:notification_id/read
Mark a single notification as read and return the updated record.
- Idempotent: marking an already-read notification is a no-op that still returns the current state.
- 404 if the notification does not exist or belongs to another user (tenant-enumeration safety).
- Scope required:
org:read. - Rate-limit tier:
user_mutation(300/hour).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.