Create a new risk from an incident
POST /v1/incidents/{id}/risks
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The ID of the incident to create a risk for
Example
123Responses
Section titled “ Responses ”Risk created
Register row for Organization Risks (RSKs). A Risk plus the relational data
shown on the risk register: threat objectives, incident associations, tags, and
comment count.
object
Count of comments on this risk (not the comments themselves).
Example
INC-00001The core view of an Organization Risk (RSK).
Relational data — threat objectives, comments, incident associations, and tags —
is exposed on RiskRegisterEntry, not here.
object
A User as returned by the API.
Profile images are not embedded — clients fetch them from
GET /api/v1/{icon} when icon is Some.
object
Relative path to the user’s avatar endpoint, e.g.
"users/{id}/avatar?v={hash}". None when the user has no avatar.
Example
RSK-00001A User as returned by the API.
Profile images are not embedded — clients fetch them from
GET /api/v1/{icon} when icon is Some.
object
Relative path to the user’s avatar endpoint, e.g.
"users/{id}/avatar?v={hash}". None when the user has no avatar.
The status of a risk
A User as returned by the API.
Profile images are not embedded — clients fetch them from
GET /api/v1/{icon} when icon is Some.
object
Relative path to the user’s avatar endpoint, e.g.
"users/{id}/avatar?v={hash}". None when the user has no avatar.
object
A relational struct that has a threat objective type and its relevancy to a risk.
PartialEq, Eq, and Hash are implemented manually to exclude created_date,
which is metadata about when the relation was mutated — not part of the identity.
object
The time that this relation was mutated
The threat objective type
Incident not found