# Acknowledge notification

Canonical page: https://docs.ovok.com/api/slim/notifications/acknowledge-notification

`PATCH /v1/slim/notifications/{id}/ack`

Acknowledges one notification stored as a CommunicationRequest (out-of-bed, device alarm, attention press) by setting its status to `completed`. For a medical notification, use `POST /v1/slim/notifications/medical/{episodeId}/ack` instead.

**Auth:** Bearer token. The caller must be a practitioner, an admin, a super admin, or hold the "System Owner" access policy. The access policy must grant `Patient:read` (an admin or super admin who holds no access policy skips this check). No `CommunicationRequest:update` grant is needed.
**Scope:** The CommunicationRequest is read with your own credentials and must belong to your project (from the token). Sub-projects are not included.

## Behaviour

- After those checks pass, Ovok writes the status change with its own credentials.
- Acknowledging an already completed notification succeeds and changes nothing.
- If the notification is updated at the same moment (for example by a new reading on the same episode), Ovok re-reads it and retries, keeping the newer content, up to three times.
- The notification leaves the active lists and bells. The device's alert state in the live views is cleared.
- Acknowledging a running out-of-bed episode stops that episode from raising the alert again. A new bed exit raises a new alert.
- Answers 200 with the updated row, in the same shape as the list rows.
- A 409 means the notification kept changing and all three attempts lost the race. Re-read it and call again.

## Example

```bash
curl -X PATCH 'https://api.sandbox.ovok.com/v1/slim/notifications/c3499c27-2973-0a7f-807e-fb8676a92dcb/ack' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk'
```