Comp AI · Schema
UpdateRiskDto
ComplianceArtificial IntelligenceSOC 2ISO 27001HIPAAGDPRAudit AutomationSecurity
Properties
| Name | Type | Description |
|---|---|---|
| title | string | Risk title |
| description | string | Detailed description of the risk |
| category | string | Risk category |
| department | string | Department responsible for the risk. Built-in values: none, admin, gov, hr, it, itsm, qms. Custom department names are also accepted. |
| status | string | Current status of the risk |
| likelihood | string | Likelihood of the risk occurring |
| impact | string | Impact if the risk materializes |
| residualLikelihood | string | Residual likelihood after treatment |
| residualImpact | string | Residual impact after treatment |
| treatmentStrategyDescription | string | Description of the treatment strategy |
| treatmentStrategy | string | Risk treatment strategy |
| assigneeId | string | ID of the user assigned to this risk |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/comp-ai/main/json-schema/comp-ai-update-risk-dto-schema.json",
"title": "UpdateRiskDto",
"x-generated": "2026-10-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/comp-ai-openapi.json#/components/schemas/UpdateRiskDto",
"type": "object",
"properties": {
"title": {
"type": "string",
"description": "Risk title"
},
"description": {
"type": "string",
"description": "Detailed description of the risk"
},
"category": {
"type": "string",
"description": "Risk category",
"enum": [
"customer",
"fraud",
"governance",
"operations",
"other",
"people",
"regulatory",
"reporting",
"resilience",
"technology",
"vendor_management"
]
},
"department": {
"type": "string",
"description": "Department responsible for the risk. Built-in values: none, admin, gov, hr, it, itsm, qms. Custom department names are also accepted.",
"maxLength": 64
},
"status": {
"type": "string",
"description": "Current status of the risk",
"enum": [
"open",
"pending",
"closed",
"archived"
],
"default": "open"
},
"likelihood": {
"type": "string",
"description": "Likelihood of the risk occurring",
"enum": [
"very_unlikely",
"unlikely",
"possible",
"likely",
"very_likely"
],
"default": "very_unlikely"
},
"impact": {
"type": "string",
"description": "Impact if the risk materializes",
"enum": [
"insignificant",
"minor",
"moderate",
"major",
"severe"
],
"default": "insignificant"
},
"residualLikelihood": {
"type": "string",
"description": "Residual likelihood after treatment",
"enum": [
"very_unlikely",
"unlikely",
"possible",
"likely",
"very_likely"
],
"default": "very_unlikely"
},
"residualImpact": {
"type": "string",
"description": "Residual impact after treatment",
"enum": [
"insignificant",
"minor",
"moderate",
"major",
"severe"
],
"default": "insignificant"
},
"treatmentStrategyDescription": {
"type": "string",
"description": "Description of the treatment strategy"
},
"treatmentStrategy": {
"type": "string",
"description": "Risk treatment strategy",
"enum": [
"accept",
"avoid",
"mitigate",
"transfer"
],
"default": "accept"
},
"assigneeId": {
"type": "string",
"description": "ID of the user assigned to this risk"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/comp-ai-update-risk-dto"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.