Alerts
Update alert
Update the details of an existing alert.
PUT
Update an existing alert to modify its details, add context, or reflect workflow progression.
Prefer
/alerts. /anomalies is a legacy alias with the same alerts:read and alerts:write scopes.Authorization
Blnk Cloud APIs support any one of the following authentication methods. All of them work with yourCLOUD_API_KEY or OAUTH_ACCESS_TOKEN.
- Bearer token
- X-Blnk-Key header
- X-API-Key header
Path
string
required
Unique identifier of the alert you want to update. Must be a valid alert ID.
Body
string
Updated title for the alert.
string
Updated description of the alert.
string
Updated status of the alert.
Response
string
Unique identifier for the alert.
string
The updated title of the alert, if provided.
string
The updated description of the alert.
string
The type or category of the alert (e.g., “Balance”, “Transaction”, “Identity”).
string
The name or identifier of the user assigned to handle the alert.
array
Array of user identifiers to whom the alert has been escalated.
string
The current status of the alert (e.g., “FLAGGED”).
timestamp
ISO 8601 formatted timestamp of when the alert was created.
timestamp
ISO 8601 formatted timestamp of when the alert was last updated.
array
Array of balance IDs affected by this alert.
array
Array of identity IDs affected by this alert.
array
Array of transaction IDs affected by this alert.