Get patient effective threshold

Method	Path
GET	/v1/slim/threshold/patient/:patientId

Authentication · Access policies

Returns the thresholds in effect for one resident: their own limits where they have them, and the home's limits everywhere else.

Deprecated. Use GET /v2/slim/threshold/patient/{patientId}. This v1 route stays available, unchanged, until every client has moved.

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 Goal:read (admins and super admins skip this check). Scope: The caller's project (from the token).

Behaviour

• Read-only; nothing is created.
• Each metric carries mode: patient (the resident's own limits) or organization (the home's limits, copied in). A few legacy records still read patient-auto; saves can no longer set it.
• Medical limits are read from Signals, which evaluates them, where available. When Signals cannot answer, Ovok's stored copy is returned instead.
• This route does not check that the resident exists; the v2 route does.

Example

curl -X GET 'https://api.sandbox.ovok.com/v1/slim/threshold/patient/3f1c2b7e-8d4a-4c1e-9b2f-6a7d5e4c3b21' \
  -H "Authorization: Bearer ${OVOK_TOKEN}"

Successful response

200 — Patient effective threshold retrieved successfully.

Errors

Status	Meaning
400	Your session has no project.
401	Bearer token is missing, invalid or expired.
403	You are not a practitioner, admin or System Owner, or you lack Goal:read.
502	The home's stored thresholds could not be read.