Sign in
Risks

Update risk

Partially updates a risk. Only provided fields will be updated. Supports both API key authentication (X-API-Key header) and session authentication (Bearer token or cookies).

patch/v1/risks/{id}

Path parameters

idstring required
Example:rsk_abc123def456

Risk ID

Request body

titlestring

Risk title

descriptionstring

Detailed description of the risk

category'customer' | 'fraud' | 'governance' | 'operations' | 'other' | 'people' | 'regulatory' | 'reporting' | 'resilience' | 'technology' | 'vendor_management'

Risk category

department'none' | 'admin' | 'gov' | 'hr' | 'it' | 'itsm' | 'qms'

Department responsible for the risk

status'open' | 'pending' | 'closed' | 'archived'

Current status of the risk

likelihood'very_unlikely' | 'unlikely' | 'possible' | 'likely' | 'very_likely'

Likelihood of the risk occurring

impact'insignificant' | 'minor' | 'moderate' | 'major' | 'severe'

Impact if the risk materializes

residualLikelihood'very_unlikely' | 'unlikely' | 'possible' | 'likely' | 'very_likely'

Residual likelihood after treatment

residualImpact'insignificant' | 'minor' | 'moderate' | 'major' | 'severe'

Residual impact after treatment

treatmentStrategyDescriptionstring

Description of the treatment strategy

treatmentStrategy'accept' | 'avoid' | 'mitigate' | 'transfer'

Risk treatment strategy

assigneeIdstring

ID of the user assigned to this risk

Example request

{
  "title": "Data breach vulnerability in user authentication system",
  "description": "Weak password requirements could lead to unauthorized access to user accounts",
  "category": "technology",
  "department": "it",
  "status": "open",
  "likelihood": "possible",
  "impact": "major",
  "residualLikelihood": "unlikely",
  "residualImpact": "minor",
  "treatmentStrategyDescription": "Implement multi-factor authentication and strengthen password requirements",
  "treatmentStrategy": "mitigate",
  "assigneeId": "mem_abc123def456"
}

Response

Risk updated successfully

idstring

Risk ID

titlestring

Risk title

descriptionstring

Risk description

category'customer' | 'governance' | 'operations' | 'other' | 'people' | 'regulatory' | 'reporting' | 'resilience' | 'technology' | 'vendor_management'
department'none' | 'admin' | 'gov' | 'hr' | 'it' | 'itsm' | 'qms' nullable
status'open' | 'pending' | 'closed' | 'archived'
likelihood'very_unlikely' | 'unlikely' | 'possible' | 'likely' | 'very_likely'
impact'insignificant' | 'minor' | 'moderate' | 'major' | 'severe'
residualLikelihood'very_unlikely' | 'unlikely' | 'possible' | 'likely' | 'very_likely'
residualImpact'insignificant' | 'minor' | 'moderate' | 'major' | 'severe'
treatmentStrategyDescriptionstring nullable
treatmentStrategy'accept' | 'avoid' | 'mitigate' | 'transfer'
organizationIdstring
assigneeIdstring nullable

ID of the user assigned to this risk

createdAtstring date-time

When the risk was created

updatedAtstring date-time

When the risk was last updated

authType'api-key' | 'session'

How the request was authenticated

Example response

{
  "id": "rsk_abc123def456",
  "title": "Data breach vulnerability in user authentication system",
  "description": "Weak password requirements could lead to unauthorized access to user accounts",
  "category": "technology",
  "department": "it",
  "status": "open",
  "likelihood": "possible",
  "impact": "major",
  "residualLikelihood": "unlikely",
  "residualImpact": "minor",
  "treatmentStrategyDescription": "Implement multi-factor authentication and strengthen password requirements",
  "treatmentStrategy": "mitigate",
  "organizationId": "org_abc123def456",
  "assigneeId": "mem_abc123def456",
  "authenticatedUser": {
    "id": "usr_def456ghi789",
    "email": "user@example.com"
  }
}

Changes