Skip to content
English
  • There are no suggestions because the search field is empty.

Deprecating bulk_mark_risk_acceptance

The bulk_mark_risk_acceptance will be deprecated and replaced by the bulk_discard endpoint.

  1. The bulk_mark_risk_acceptance endpoint is now bulk_discard. 
  2. Anywhere in the filters or responses where you used to expect risk_accept, you should now expect to use/see discard. So for example, when making API requests, things previously looked like this:

The old endpoint looks liked this.

GET /api/v1/vulnerabilities.json?c[status]=risk_accepted
{
  ...
  status: "risk_accepted",
  discard_reason: "risk_accepted"
  ...
}

The new endpoint looks like this.

GET /api/v1/vulnerabilities.json?c[status]=discarded

{
  ...
  status: "discarded",
  discard_reason: "risk_accepted"
  ...
}

In our explorations for this change we found the endpoint has not been called via the API in a long time and only gets referenced from the UI, we believe the risk to making this change is very low.