Take over a site another operator holds
Site-level Take over, one confirm. Body {expected_operator_id, expected_focus_id?} names the hold the console showed. If it is still that holder's valid hold, in one transaction it is released (taken_over) and the caller's hold is created IN THE SAME LINEAGE, so every held alarm stays held, now for the caller, with no gap; the displaced operator's live claims at the site then move to the caller. 200 with the caller's new hold record (also when the caller already holds it, which writes nothing). Otherwise nothing moves: 409 claim_changed with hold = the valid hold at the site now (or null). Open to every central-staff claim participant, owners included; a taker without review_label_alarms can act on the alarms but not label them. 403 out of scope or not central staff. 404 while SITE_HOLD_ENABLED is off.
Request
- Base URLhttps://api.verdun.ai (the document declares no server; this is the origin it was published from)
- URLhttps://api.verdun.ai/focus/{hold_id}/take-over
- AuthHTTP bearer
Path parameters
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 2 revisions of this API.