Breaking change - Deleting targets
When deleting a target, we previously would respond with HTTP 204 No Content with the response body of the string "Target has been deleted successfully.".
When deleting a target, we previously would respond with HTTP 204 No Content with the response body of the string "Target has been deleted successfully.".
Issues and occurrences endpoint
Issues endpoint
The protocol property has been added to issue occurrences. This field captures the transport layer protocol that was in use when the security issue was detected. The protocol field helps provide more context about how vulnerabilities were discovered.
we’ve added two new endpoints to the Intruder API which will allow users to add and delete tags for a target. With this release, you will be able to fully manage your targets using the Intruder API.
The new license endpoints allow users to answer the following questions using the Intruder API:
The list target endpoint now contains whether a target has an authentication or API schema added. Additional endpoints have been added to help users manage their authentications and API schemas.
This endpoint allows API users to query detailed scanner output for an Occurrence.
The list targets endpoint now also contains the tags associated with each target.