How to start a re-test

Start a re-test of a finding to check if the vulnerability is fixed and can no longer be exploited.

Step 1: Start the re-test

You will need the findings and target identifiers to start a re-test. You obtain them, for example, by listing findings and picking the finding you want to re-test.

In this request, the finding identifier is 1 for the target identifier 2oir9t8RKxdr.

Request
curl https://api.probely.com/targets/2oir9t8RKxdr/findings/1/retest/ \
  -X POST \
  -H 'Authorization: JWT <YOUR_API_TOKEN>' \
  -H 'Content-Type: application/json'

The response returns the confirmation the re-test has begun ("status": "queued").

Response
{
  "id": "w2gDAvPoP7ga",
  "target": {
    "id": "2oir9t8RKxdr",
    "name": "",
    "site": {
      "id": "spMJGK2QAB7B",
      "name": "My target",
      "desc": "",
      "url": "https://example.com",
      "host": "example.com",
      ...
    },
    ...
  },
  "status": "queued",
  "started": null,
  "completed": null,
  ...
}

The re-test will start shortly, and you can check when it is finished by polling the finding (using the finding and target identifiers). For that, see the tutorial about How to check a re-test result.

Step 1: Start the re-test​

Step 1: Start the re-test