Hand one minimal incident to a responsible operator and keep durable SLA state.
Create a digest-only incident, deliver the returned private link through your own notification channel, and branch on acknowledged, resolved, or overdue state.
Step 1 · Create
curl https://api.scrubmytext.com/v1/escalations/manage -H "Authorization: Bearer smt_live_YOUR_KEY" -H "Content-Type: application/json" -d '{"operation":"create","incident_fingerprint":"sha256:YOUR_64_HEX_DIGEST","severity":"high","response_sla_seconds":900,"resolution_sla_seconds":14400}'Store the escalation_id. Deliver operator_url only to the intended operator; the URL is a bearer secret.
Step 2 · Check
curl https://api.scrubmytext.com/v1/escalations/manage -H "Authorization: Bearer smt_live_YOUR_KEY" -H "Content-Type: application/json" -d '{"operation":"check","control_id":"esc_RETURNED_ID"}'Pause the affected autonomous workflow on response_overdue or resolution_overdue according to your policy. Do not infer delivery from creation alone.
Step 3 · Reconcile the external workflow
The operator link can acknowledge or resolve. The authenticated owner can inspect or cancel; your application remains responsible for the incident narrative and any follow-up action.
Limits
- ScrubMyText does not send email, SMS, chat, or paging notifications in this release.
- Anyone with the link can acknowledge or resolve; verify delivery and authority yourself.
- SLA state is a technical clock, not a contractual guarantee.