Update Severity

Modify the severity level of a finding

PATCH /api/findings/{id}/severity

{
  "severity": "high"
}

{
  "success": true,
  "data": {
    "finding_id": "123e4567-e89b-12d3-a456-426614174000",
    "old_severity": "medium",
    "new_severity": "high",
    "event": {
      "id": "987e6543-e89b-12d3-a456-426614174999",
      "finding_id": "123e4567-e89b-12d3-a456-426614174000",
      "user_id": "555e5555-e89b-12d3-a456-426614175555",
      "event_type": "severity_change",
      "old_value": "medium",
      "new_value": "high",
      "comment": null,
      "metadata": null,
      "created_at": "2026-03-12T14:30:00Z"
    }
  }
}

Update the severity classification of a security finding. This operation creates a finding event to track the change history.

This endpoint requires authentication. The change will be recorded with the authenticated user’s ID.

Path Parameters

id · string · required

The unique UUID of the finding to update

Request Body

severity · string · required

The new severity level for the finding. Must be one of:

• critical - Requires immediate attention
• high - Significant risk, prioritize remediation
• medium - Moderate risk
• low - Minor risk or informational

{
  "severity": "high"
}

Response

Returns the updated finding information and the event that was created to track this change.

data · object

Show Response Properties

finding_id · string

UUID of the finding that was updated

old_severity · string

The previous severity level before the update

new_severity · string

The new severity level after the update

event · object

The finding event created to track this change

Show Event Properties

id · string

Unique identifier for the event

finding_id · string

UUID of the associated finding

user_id · string

UUID of the user who made the change

event_type · string

Always severity_change for this operation

old_value · string

Previous severity value

new_value · string

New severity value

comment · string

Optional comment about the change

metadata · object

Additional structured data about the event

created_at · string

ISO 8601 timestamp when the event was created

{
  "success": true,
  "data": {
    "finding_id": "123e4567-e89b-12d3-a456-426614174000",
    "old_severity": "medium",
    "new_severity": "high",
    "event": {
      "id": "987e6543-e89b-12d3-a456-426614174999",
      "finding_id": "123e4567-e89b-12d3-a456-426614174000",
      "user_id": "555e5555-e89b-12d3-a456-426614175555",
      "event_type": "severity_change",
      "old_value": "medium",
      "new_value": "high",
      "comment": null,
      "metadata": null,
      "created_at": "2026-03-12T14:30:00Z"
    }
  }
}

Error Responses

404 Not Found

Returned when the specified finding does not exist.

{
  "success": false,
  "code": 404,
  "message": "Finding '123e4567-e89b-12d3-a456-426614174000' not found"
}

500 Internal Server Error

Returned when the update fails or the event cannot be recorded.

{
  "success": false,
  "code": 500,
  "message": "Failed to update severity: database connection error"
}

{
  "success": false,
  "code": 500,
  "message": "Severity updated but failed to record event: database error"
}

If the severity is updated successfully but the event recording fails, the finding will still have the new severity value. The error message will indicate this partial success.