v1
latestOpenAPI 3.0.32026-07-134103031.5 MBList Target's Findings
Path parameters
Identifier of the target.
Query parameters
Date of when the accepted vulnerability was approved.
For example, "2023-08-09"
A unique Base58 value identifying this object.
Date and time of when the vulnerability was changed, in ISO 8601 UTC format.
For example, "2023-08-09T13:27:43.8208302"
Date and time of when the vulnerability was changed, in ISO 8601 UTC format.
For example, "2023-08-09T13:27:43.8208302"
Fields to exclude from the response.
Date of when the accepted vulnerability expires before changing back to not fixed.
For example, "2023-08-09"
Extra fields to include in response:
- last_found_scan - Add last_found_scan to response under last_found_scan key
A unique Base58 value identifying this object.
Logical operator to apply between labels:
(Defaults to or)
- and - and
- or - or
Date and time of when the vulnerability was last found to filter results, in ISO 8601 UTC format.
For example, "2023-08-09T13:27:43.8208302"
Date and time of when the vulnerability was last found to filter results, in ISO 8601 UTC format.
For example, "2023-08-09T13:27:43.8208302"
Number of results to return per page.
Which field to use when ordering the results.
A page number within the paginated result set.
Some findings we're unsure are valid and need a manual validation step.
- notrequired - not required
- pending - pending review
- rejected - rejected after review
- accepted - accepted after review
A unique Base58 value identifying this object.
A search term.
Severity of the vulnerability finding:
- 10 - low
- 20 - medium
- 30 - high
- 40 - critical
State of the vulnerability finding:
(Read more about the meaning of vulnerability findings states)
- notfixed - Not Fixed
- invalid - Invalid
- accepted - Accepted
- fixed - Fixed
- retesting - Re-testing
Response
Example response
{
"count": 6,
"page_total": 1,
"page": 1,
"length": 10
}