Skip to main content

Overview

Updates the status of one or more alerts. Allows analysts to change the alert state (e.g., Open, In Review, Completed) and optionally add an observation note. Supports auditing for traceability.
Authorization Required: Include a valid Bearer Token in the Authorization header.

Endpoint Details

POST /api/utm-alerts/status

Method: POST
Content-Type: application/json
Authentication: Bearer Token required
Response: HTTP 200 OK (no body)

Request Body

array
required
Array of alert UUIDs to update
integer
required
New status code for the alerts (see status codes below)
string
Optional observation note about the status change
boolean
default:"false"
Whether to add a “False positive” tag to the alerts

Status Codes Reference

OPEN

Value: 2
Alert is open and pending review

IN_REVIEW

Value: 3
Alert is currently being reviewed

COMPLETED

Value: 5
Alert has been resolved/completed

JSON Schema


Request & Response Examples

Additional Code Examples


Response Details

Successful Update

The API returns HTTP 200 OK with no response body when the status is successfully updated.

Status Codes

OK
Status updated successfully
Bad Request
Invalid request payload or malformed JSON
Unauthorized
Missing or invalid Bearer token
Not Found
One or more alerts not found
Internal Server Error
Internal server error during update

Usage Examples

Mark Alert as False Positive

Move Alert to Review

Bulk Status Update


Security Considerations

Security Notes:
  • Requires Bearer token authentication
  • All status changes are audited using ApplicationEventService for traceability
  • Users without proper permissions will receive 401 Unauthorized
  • Alert IDs must be valid UUIDs that exist in the system

Best Practices

Follow a logical status progression:
  1. OPEN (2) - Initial alert state
  2. IN_REVIEW (3) - Under investigation
  3. COMPLETED (5) - Resolved or closed
Always include meaningful statusObservation notes:
  • Document the reason for status change
  • Include investigation findings
  • Reference any related tickets or incidents
When marking alerts as false positives:
  • Set status to 5 (COMPLETED)
  • Set addFalsePositiveTag to true
  • Include detailed reasoning in statusObservation

OpenAPI Specification