--- title: "Changes to Update Risk By Id" method: PUT path: "/projectRisks/{id}" --- # Changes to Update Risk By Id `PUT /projectRisks/{id}` > Every recorded change to this operation, newest first. > 144 revisions in range; 16 not diffed. ## Timeline Changed in 7 of 144 revisions. - **2026-08-26** `3b138b306b5b`: 22 breaking, 10 warning, 36 info - **2026-04-05** `c419b1e72a65`: 1 breaking, 7 warning, 6 info - **2025-09-12** `cfa9ae933c17`: 3 breaking, 20 warning, 16 info - **2025-08-29** `af64a3a9480e`: 1 breaking, 26 info - **2025-08-08** `550d1cb0d011`: 1 breaking, 26 warning - **2025-08-08** `8f39d60f160a`: 1 breaking, 26 info - **2025-01-22** `ed48b7196725`: 50 breaking, 22 warning, 15 info ## Changes - **2026-08-26** `3b138b306b5b`: 22 breaking, 10 warning, 36 info - removed the enum value `Very Low risk` of the request property `current_risk_level` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/ai_lifecycle_phase` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/approval_status` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/assessment_mapping` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/controls_mapping` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/current_risk_level` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/date_of_assessment` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/deadline` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/final_risk_level` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/impact` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/implementation_strategy` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/likelihood` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/likelihood_mitigation` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/mitigation_evidence_document` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/mitigation_plan` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/mitigation_status` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/review_notes` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/risk_approval` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/risk_description` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/risk_level_autocalculated` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/risk_severity` became nullable for the status `200` - the response property `data/allOf[#/components/schemas/ProjectRiskInput]/severity` became nullable for the status `200` - added the new `No risk` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/current_risk_level` response property for the response status `200` - added the new `Very low risk` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/current_risk_level` response property for the response status `200` - added the new `undefined` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/ai_lifecycle_phase` response property for the response status `200` - added the new `undefined` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/current_risk_level` response property for the response status `200` - added the new `undefined` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/likelihood` response property for the response status `200` - added the new `undefined` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/likelihood_mitigation` response property for the response status `200` - added the new `undefined` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/mitigation_status` response property for the response status `200` - added the new `undefined` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/risk_level_autocalculated` response property for the response status `200` - added the new `undefined` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/risk_severity` response property for the response status `200` - added the new `undefined` enum value to the `data/allOf[#/components/schemas/ProjectRiskInput]/severity` response property for the response status `200` - the request property `ai_lifecycle_phase` became nullable - the request property `approval_status` became nullable - the request property `assessment_mapping` became nullable - the request property `controls_mapping` became nullable - the request property `current_risk_level` became nullable - the request property `date_of_assessment` became nullable - the request property `deadline` became nullable - the request property `final_risk_level` became nullable - …28 more - **2026-04-05** `c419b1e72a65`: 1 breaking, 7 warning, 6 info - removed the media type `application/json` for the response with the status `200` - removed the request property `id` - removed the request property `likelihood` - removed the request property `mitigation_status` - removed the request property `project_id` - removed the request property `risk_level` - removed the request property `risk_name` - removed the request property `severity` - api operation id `updateRiskById` was added - the endpoint scheme security `bearerAuth` was added to the API - the endpoint scheme security `JWTAuth` was removed from the API - request body became optional - added the non-success response with the status `401` - added the non-success response with the status `500` - **2025-09-12** `cfa9ae933c17`: 3 breaking, 20 warning, 16 info - request property `likelihood` was restricted to a list of enum values - request property `severity` was restricted to a list of enum values - removed the success response with the status `202` - removed the request property `ai_lifecycle_phase` - removed the request property `approval_status` - removed the request property `assessment_mapping` - removed the request property `controls_mapping` - removed the request property `current_risk_level` - removed the request property `date_of_assessment` - removed the request property `deadline` - removed the request property `final_risk_level` - removed the request property `impact` - removed the request property `implementation_strategy` - removed the request property `likelihood_mitigation` - removed the request property `mitigation_evidence_document` - removed the request property `mitigation_plan` - removed the request property `review_notes` - removed the request property `risk_approval` - removed the request property `risk_category` - removed the request property `risk_description` - removed the request property `risk_level_autocalculated` - removed the request property `risk_owner` - removed the request property `risk_severity` - api tag `Project Risks` added - api tag `projectRisks` removed - added the new optional request property `risk_level` - added the new `high` enum value to the request property `likelihood` - added the new `high` enum value to the request property `severity` - added the new `low` enum value to the request property `likelihood` - added the new `low` enum value to the request property `severity` - added the new `medium` enum value to the request property `likelihood` - added the new `medium` enum value to the request property `severity` - added the new `very_high` enum value to the request property `likelihood` - added the new `very_high` enum value to the request property `severity` - added the new `very_low` enum value to the request property `likelihood` - added the new `very_low` enum value to the request property `severity` - removed the non-success response with the status `404` - removed the non-success response with the status `500` - added the success response with the status `200` - **2025-08-29** `af64a3a9480e`: 1 breaking, 26 info - the `data` response's property type changed from no type to `object` for status `202` - added the optional property `data/ai_lifecycle_phase` to the response with the `202` status - added the optional property `data/approval_status` to the response with the `202` status - added the optional property `data/assessment_mapping` to the response with the `202` status - added the optional property `data/controls_mapping` to the response with the `202` status - added the optional property `data/current_risk_level` to the response with the `202` status - added the optional property `data/date_of_assessment` to the response with the `202` status - added the optional property `data/deadline` to the response with the `202` status - added the optional property `data/final_risk_level` to the response with the `202` status - added the optional property `data/id` to the response with the `202` status - added the optional property `data/impact` to the response with the `202` status - added the optional property `data/implementation_strategy` to the response with the `202` status - added the optional property `data/likelihood` to the response with the `202` status - added the optional property `data/likelihood_mitigation` to the response with the `202` status - added the optional property `data/mitigation_evidence_document` to the response with the `202` status - added the optional property `data/mitigation_plan` to the response with the `202` status - added the optional property `data/mitigation_status` to the response with the `202` status - added the optional property `data/project_id` to the response with the `202` status - added the optional property `data/review_notes` to the response with the `202` status - added the optional property `data/risk_approval` to the response with the `202` status - added the optional property `data/risk_category` to the response with the `202` status - added the optional property `data/risk_description` to the response with the `202` status - added the optional property `data/risk_level_autocalculated` to the response with the `202` status - added the optional property `data/risk_name` to the response with the `202` status - added the optional property `data/risk_owner` to the response with the `202` status - added the optional property `data/risk_severity` to the response with the `202` status - added the optional property `data/severity` to the response with the `202` status - **2025-08-08** `550d1cb0d011`: 1 breaking, 26 warning - the `data` response's property type changed from `object` to no type for status `202` - removed the optional property `data/ai_lifecycle_phase` from the response with the `202` status - removed the optional property `data/approval_status` from the response with the `202` status - removed the optional property `data/assessment_mapping` from the response with the `202` status - removed the optional property `data/controls_mapping` from the response with the `202` status - removed the optional property `data/current_risk_level` from the response with the `202` status - removed the optional property `data/date_of_assessment` from the response with the `202` status - removed the optional property `data/deadline` from the response with the `202` status - removed the optional property `data/final_risk_level` from the response with the `202` status - removed the optional property `data/id` from the response with the `202` status - removed the optional property `data/impact` from the response with the `202` status - removed the optional property `data/implementation_strategy` from the response with the `202` status - removed the optional property `data/likelihood` from the response with the `202` status - removed the optional property `data/likelihood_mitigation` from the response with the `202` status - removed the optional property `data/mitigation_evidence_document` from the response with the `202` status - removed the optional property `data/mitigation_plan` from the response with the `202` status - removed the optional property `data/mitigation_status` from the response with the `202` status - removed the optional property `data/project_id` from the response with the `202` status - removed the optional property `data/review_notes` from the response with the `202` status - removed the optional property `data/risk_approval` from the response with the `202` status - removed the optional property `data/risk_category` from the response with the `202` status - removed the optional property `data/risk_description` from the response with the `202` status - removed the optional property `data/risk_level_autocalculated` from the response with the `202` status - removed the optional property `data/risk_name` from the response with the `202` status - removed the optional property `data/risk_owner` from the response with the `202` status - removed the optional property `data/risk_severity` from the response with the `202` status - removed the optional property `data/severity` from the response with the `202` status - **2025-08-08** `8f39d60f160a`: 1 breaking, 26 info - the `data` response's property type changed from no type to `object` for status `202` - added the optional property `data/ai_lifecycle_phase` to the response with the `202` status - added the optional property `data/approval_status` to the response with the `202` status - added the optional property `data/assessment_mapping` to the response with the `202` status - added the optional property `data/controls_mapping` to the response with the `202` status - added the optional property `data/current_risk_level` to the response with the `202` status - added the optional property `data/date_of_assessment` to the response with the `202` status - added the optional property `data/deadline` to the response with the `202` status - added the optional property `data/final_risk_level` to the response with the `202` status - added the optional property `data/id` to the response with the `202` status - added the optional property `data/impact` to the response with the `202` status - added the optional property `data/implementation_strategy` to the response with the `202` status - added the optional property `data/likelihood` to the response with the `202` status - added the optional property `data/likelihood_mitigation` to the response with the `202` status - added the optional property `data/mitigation_evidence_document` to the response with the `202` status - added the optional property `data/mitigation_plan` to the response with the `202` status - added the optional property `data/mitigation_status` to the response with the `202` status - added the optional property `data/project_id` to the response with the `202` status - added the optional property `data/review_notes` to the response with the `202` status - added the optional property `data/risk_approval` to the response with the `202` status - added the optional property `data/risk_category` to the response with the `202` status - added the optional property `data/risk_description` to the response with the `202` status - added the optional property `data/risk_level_autocalculated` to the response with the `202` status - added the optional property `data/risk_name` to the response with the `202` status - added the optional property `data/risk_owner` to the response with the `202` status - added the optional property `data/risk_severity` to the response with the `202` status - added the optional property `data/severity` to the response with the `202` status - **2025-01-22** `ed48b7196725`: 50 breaking, 22 warning, 15 info - removed the enum value `Almost Certain` of the request property `likelihood` - removed the enum value `Almost Certain` of the request property `likelihood_mitigation` - removed the enum value `Canceled` of the request property `mitigation_status` - removed the enum value `Catastrophic` of the request property `severity` - removed the enum value `Completed` of the request property `mitigation_status` - removed the enum value `Critical` of the request property `risk_severity` - removed the enum value `Data collection & processing` of the request property `ai_lifecycle_phase` - removed the enum value `Decommissioning & retirement` of the request property `ai_lifecycle_phase` - removed the enum value `Deferred` of the request property `mitigation_status` - removed the enum value `Deployment & integration` of the request property `ai_lifecycle_phase` - removed the enum value `High risk` of the request property `current_risk_level` - removed the enum value `High risk` of the request property `risk_level_autocalculated` - removed the enum value `In Progress` of the request property `mitigation_status` - removed the enum value `Likely` of the request property `likelihood` - removed the enum value `Likely` of the request property `likelihood_mitigation` - removed the enum value `Low risk` of the request property `current_risk_level` - removed the enum value `Low risk` of the request property `risk_level_autocalculated` - removed the enum value `Major` of the request property `risk_severity` - removed the enum value `Major` of the request property `severity` - removed the enum value `Medium risk` of the request property `current_risk_level` - removed the enum value `Medium risk` of the request property `risk_level_autocalculated` - removed the enum value `Minor` of the request property `risk_severity` - removed the enum value `Minor` of the request property `severity` - removed the enum value `Model development & training` of the request property `ai_lifecycle_phase` - removed the enum value `Model validation & testing` of the request property `ai_lifecycle_phase` - removed the enum value `Moderate` of the request property `risk_severity` - removed the enum value `Moderate` of the request property `severity` - removed the enum value `Monitoring & maintenance` of the request property `ai_lifecycle_phase` - removed the enum value `Negligible` of the request property `risk_severity` - removed the enum value `Negligible` of the request property `severity` - removed the enum value `No risk` of the request property `risk_level_autocalculated` - removed the enum value `Not Started` of the request property `mitigation_status` - removed the enum value `On Hold` of the request property `mitigation_status` - removed the enum value `Possible` of the request property `likelihood` - removed the enum value `Possible` of the request property `likelihood_mitigation` - removed the enum value `Problem definition & planning` of the request property `ai_lifecycle_phase` - removed the enum value `Rare` of the request property `likelihood` - removed the enum value `Rare` of the request property `likelihood_mitigation` - removed the enum value `Requires review` of the request property `mitigation_status` - removed the enum value `Unlikely` of the request property `likelihood` - …47 more --- [Operation](https://skmtc.dev/verifywise-ai/apis/verifywise-api/docs/projectRisks/:id/put.md) - [API](https://skmtc.dev/verifywise-ai/apis/verifywise-api.md) - [Page](https://skmtc.dev/verifywise-ai/apis/verifywise-api/changes/projectRisks/:id/put)