# Set a patient vital threshold (closed)

Canonical page: https://docs.ovok.com/api/slim/threshold/patient/set-a-patient-vital-threshold-closed

`PUT /v1/slim/threshold/patient/{patientId}/vitals/{code}`

Sets one resident's threshold for a single vital code (closed).

> **Closed.** This v1 save route answers 410 Gone and writes nothing. Use `PUT /v2/slim/threshold/patient/{patientId}`.

**Auth:** The access policy must grant `Goal:update` (an admin or super admin who holds no access policy skips this check).
**Scope:** The caller's project (from the token).

## Behaviour

- Every call answers `410` as `application/problem+json`, whatever the body says; the `detail` names the v2 route.
- The `GET` routes of this path are unchanged.

## Example

```bash
curl -X PUT 'https://api.sandbox.ovok.com/v1/slim/threshold/patient/c3499c27-2973-0a7f-807e-fb8676a92dcb/vitals/59408-5' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk' \
  -H 'Content-Type: application/json' \
  -d '{}'
```

```json
{ "status": 410, "detail": "This v1 save route is closed. Use PUT /v2/slim/threshold/patient/{patientId}." }
```

**Who can call it:** a practitioner, a project admin or a System Owner session. See [roles](/access-policies#who-can-call-a-route).