Bulk Update Target's Findings
POST/targets/:target_id/findings/bulk/update/
Request
Path Parameters
Identifier of the target.
- application/json
- application/x-www-form-urlencoded
- multipart/form-data
Body
required
Array [
]
notfixed- Not Fixedinvalid- Invalidaccepted- Acceptedfixed- Fixed10- low20- medium30- high40- criticalnotrequired- not requiredpending- pending reviewrejected- rejected after reviewaccepted- accepted after review
List of object IDs.
labels
object[]
Labels of the vulnerability finding.
Possible values: <= 255 characters
Name of the label.
The maximum length is 255 characters.
Possible values: Value must match regular expression ^[a-zA-Z0-9#_-]*$
Color of the label, in RGB hexadecimal format prefixed with "#".
For example, "#00FF00" for green.
Definition of the vulnerability.
User who is assigned to fix the vulnerability.
Possible values: [notfixed, invalid, accepted, fixed]
State of the vulnerability finding:
(Read more about the meaning of vulnerability findings states)
Possible values: >= -2147483648 and <= 2147483647, [10, 20, 30, 40]
Severity of the vulnerability finding:
Date and time of when the vulnerability was last found, in ISO 8601 UTC format. For example, "2023-08-09T13:27:43.8208302"
If true, this is a newly found vulnerability. If false, this vulnerability has been found in previous scans.
Possible values: [notrequired, pending, rejected, accepted, ``]
Some findings we're unsure are valid and need a manual validation step.
User's reason for finding's review.
Comment on the object.
Possible values: <= 4096 characters
Reason for changing the Finding state to 'invalid' or 'accepted'.
Expiration date of the acceptance. Required if the account setting 'Require expiration date on acceptance' is set.
Name of the person or entity approving the acceptance. Required if the account setting 'Require approval name on acceptance' is set.
Date of the approval of the acceptance. Required if the account setting 'Require approval date on acceptance' is set.
Body
required
Array [
]
notfixed- Not Fixedinvalid- Invalidaccepted- Acceptedfixed- Fixed10- low20- medium30- high40- criticalnotrequired- not requiredpending- pending reviewrejected- rejected after reviewaccepted- accepted after review
List of object IDs.
labels
object[]
Labels of the vulnerability finding.
Possible values: <= 255 characters
Name of the label.
The maximum length is 255 characters.
Possible values: Value must match regular expression ^[a-zA-Z0-9#_-]*$
Color of the label, in RGB hexadecimal format prefixed with "#".
For example, "#00FF00" for green.
Definition of the vulnerability.
User who is assigned to fix the vulnerability.
Possible values: [notfixed, invalid, accepted, fixed]
State of the vulnerability finding:
(Read more about the meaning of vulnerability findings states)
Possible values: >= -2147483648 and <= 2147483647, [10, 20, 30, 40]
Severity of the vulnerability finding:
Date and time of when the vulnerability was last found, in ISO 8601 UTC format. For example, "2023-08-09T13:27:43.8208302"
If true, this is a newly found vulnerability. If false, this vulnerability has been found in previous scans.
Possible values: [notrequired, pending, rejected, accepted, ``]
Some findings we're unsure are valid and need a manual validation step.
User's reason for finding's review.
Comment on the object.
Possible values: <= 4096 characters
Reason for changing the Finding state to 'invalid' or 'accepted'.
Expiration date of the acceptance. Required if the account setting 'Require expiration date on acceptance' is set.
Name of the person or entity approving the acceptance. Required if the account setting 'Require approval name on acceptance' is set.
Date of the approval of the acceptance. Required if the account setting 'Require approval date on acceptance' is set.
Body
required
Array [
]
notfixed- Not Fixedinvalid- Invalidaccepted- Acceptedfixed- Fixed10- low20- medium30- high40- criticalnotrequired- not requiredpending- pending reviewrejected- rejected after reviewaccepted- accepted after review
List of object IDs.
labels
object[]
Labels of the vulnerability finding.
Possible values: <= 255 characters
Name of the label.
The maximum length is 255 characters.
Possible values: Value must match regular expression ^[a-zA-Z0-9#_-]*$
Color of the label, in RGB hexadecimal format prefixed with "#".
For example, "#00FF00" for green.
Definition of the vulnerability.
User who is assigned to fix the vulnerability.
Possible values: [notfixed, invalid, accepted, fixed]
State of the vulnerability finding:
(Read more about the meaning of vulnerability findings states)
Possible values: >= -2147483648 and <= 2147483647, [10, 20, 30, 40]
Severity of the vulnerability finding:
Date and time of when the vulnerability was last found, in ISO 8601 UTC format. For example, "2023-08-09T13:27:43.8208302"
If true, this is a newly found vulnerability. If false, this vulnerability has been found in previous scans.
Possible values: [notrequired, pending, rejected, accepted, ``]
Some findings we're unsure are valid and need a manual validation step.
User's reason for finding's review.
Comment on the object.
Possible values: <= 4096 characters
Reason for changing the Finding state to 'invalid' or 'accepted'.
Expiration date of the acceptance. Required if the account setting 'Require expiration date on acceptance' is set.
Name of the person or entity approving the acceptance. Required if the account setting 'Require approval name on acceptance' is set.
Date of the approval of the acceptance. Required if the account setting 'Require approval date on acceptance' is set.
Responses
- 200
- 400
- 401
- 404
- 500
- application/json
- Schema
- Example (from schema)
Schema
List of object IDs.
{
"ids": [
"string"
]
}
- application/json
- Schema
- Example (from schema)
Schema
{
"<field name>": [
"Errors related to field <field name>."
],
"non_field_errors": [
"Errors not related to any field specific field."
]
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "Incorrect authentication credentials."
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "Not found."
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "Unexpected error while handling your request."
}