Skip to main content
POST
Override alert checklist closure controls
Requires the dedicated alerts:close-override scope. The effective policy must permit privileged overrides, at least one required item must remain unresolved, and the request must contain a meaningful reason. This endpoint records the override. Send the subsequent alert status update separately. Reopening the alert or changing a checklist item clears the active override, so a later closure requires a new authorization and reason.

Authorizations

Authorization
string
header
required

API key authentication. Use format: Bearer cbr_live_your_key

Path Parameters

id
string
required
Minimum string length: 1

Body

application/json
reason
string
required
Required string length: 10 - 4000
acknowledgeIncomplete
enum<boolean>
required
Available options:
true

Response

Default Response

id
string
required
alertId
string
required
policyVersionIds
string[]
required
policyFingerprint
string
required
policySnapshot
object
required
selectionTrace
object[]
required
alertCategoryValueAtInstantiation
string
required
enforcementMode
enum<string>
required
Available options:
OFF,
WARN,
BLOCK
overrideMode
enum<string>
required
Available options:
DISALLOWED,
PRIVILEGED_WITH_REASON
allowAlertSpecificItems
boolean
required
requiredCount
integer
required
Required range: x >= 0
completedCount
integer
required
Required range: x >= 0
waivedCount
integer
required
Required range: x >= 0
items
AlertChecklistItem · object[]
required
instantiatedAt
string<date-time>
required
createdAt
string<date-time>
required
updatedAt
string<date-time>
required
closureOverriddenAt
string<date-time> | null
closureOverriddenById
string | null
closureOverriddenBy
AlertChecklistUser · object | null
closureOverrideReason
string | null
completedAt
string<date-time> | null