Escalations

One-tap acknowledge (token)

The phone path. No session and no account: the token from the page link IS the proof, exactly like a magic link. It is hashed at rest and ACK-ONLY — it cannot read the escalation, resolve it, or reach any other row, so a forwarded link costs at most a wrongly-attributed acknowledgement. Idempotent; dies once the escalation is resolved.

post/escalations/v1/ack

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/escalations/v1/ack
  • Auth: none declared

Request body

tokenstring required

Response

Acknowledged (or an idempotent replay).

escalation_idstring uuid
status'acknowledged' | 'resolved'
acknowledged_atstring date-time nullable
changedboolean

False on an idempotent replay — the ORIGINAL acknowledgement is reported.

reasonstring

Shown on the confirm page so the human sees what they just took ownership of.

Changes

No recorded changes to this operation across all 1 revision of this API.