Remove a Patient’s Signals threshold

Method	Path
DELETE	/v1/signals/patients/:patientId/thresholds/:code

Shared authentication, project scope, and response conventions.

Removes a threshold from Signals so that Signals stops alerting on that code for the Patient. Removing a band always counts as silencing.

Requirement or input	Details
Access policy	signals_silence:update and Patient update
Caller profile	A person profile is required for the audit record.
Reason	Required. Send ?reason= or a JSON body with reason; the query value wins if both are supplied. The reason is trimmed and limited to 1,000 characters.
Success	204 No Content; there is no response body.

curl --request DELETE \
  --url 'https://api.sandbox.ovok.com/v1/signals/patients/3f1c2b7e-8d4a-4c1e-9b2f-6a7d5e4c3b21/thresholds/8867-4?reason=Monitoring%20plan%20changed' \
  --header "Authorization: Bearer ${OVOK_TOKEN}"

Ovok records the removed band on the Patient and clears its cached threshold copy. If the audit write fails, Ovok attempts to recreate the rule; Signals may assign the restored rule a new id and version.

Status	Meaning
403	Missing signals_silence:update, Patient update access, or person profile.
404	Patient is missing, outside the project, unreadable, or has no editable threshold for :code.
409 signals_patient_not_enrolled	Patient is not enrolled in Signals.
409 signals_threshold_not_editable	The existing rule is not an editable absolute band.
409	Another write to this Patient and code is in progress.
422	Missing reason, invalid code, or an unknown query/body field.
503 signals_audit_failed	The removal was restored; retrying is safe.
503 signals_undo_failed	The removal remains but its Ovok audit could not be completed; operator follow-up is required.