VEverdun
events

Clear the escalation record (compare-and-clear)

Ends the caller's own escalation intent when, and only when, the ownership generation AND the action_token still match: a stale generation (another holder, a re-acquire) is 409 claim_changed / claim_held; a token this alarm has not seen that is not the current one is 409 activity_changed with the current claim and activity, and nothing is cleared. A token that already finished or was replaced by a newer pick (the row remembers the newest 32 of its generation) is already_clear, nothing written. 200 outcomes: cleared, already_clear (a retried or late cancel) and alarm_closed (the close already cleared it). reason is cancelled, panel_closed or completed. 404 while CLAIM_ESCALATION_ENABLED is off.

post/events/{event_id}/claim/acting/cancel

Request

  • Base URL
    https://api.verdun.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://api.verdun.ai/events/{event_id}/claim/acting/cancel
  • Auth
    HTTP bearer

Path parameters

event_idstring required

Request body

generationstring uuid required

claim.generation the console holds.

action_tokenstring required

The token sent with the set this cancels.

reason'cancelled' | 'panel_closed' | 'completed' required

cancelled: the operator backed out. panel_closed: dismissed or navigated away. completed: the action finished.

Response

Successful Response

clearedboolean required

True only when this call cleared the intent

outcome'cleared' | 'already_clear' | 'alarm_closed' required

cleared: this call ended it. already_clear: nothing current (a retried cancel). alarm_closed: the close already cleared it.

Changes

No recorded changes to this operation across all 2 revisions of this API.