Retrieve Finding Retest Status

[POST] /qps/rest/3.0/retestStatus/was/finding/{id}

Retrieves the retest status for a finding. You can use the retest status to automate the scanning and retesting processes. The API returns one of these statuses: NO_RETEST, UNDER_RETEST, RETESTED, CANCELING, and CANCELED.

Permissions required -  You must have the WAS module enabled. You must have the "API access" and "Access WAS module" permissions. You must have the View permission.

Input ParametersInput Parameters

The API supports POST method. The Input parameters are id or uniqueId. We support optional filters that are available for the Search Finding API.

Parameter

Mandatory

/Optional

Data Type

Description

id

Optional

integer

ID of the finding (WebAppVuln or WebAppSensitiveContent).

uniqueId

Optional

value

The 36-bit unique id assigned to the finding.

Sample - Retrieve retest status for a findingSample - Retrieve retest status for a finding

Let us retrieve the retest status of a finding with ID 2730074.

API request

curl -u "USERNAME:PASSWORD" -H "content-type: text/xml" -X "POST" "<qualys_base_url>/qps/rest/3.0/retestStatus/was/finding/2730074"      
    

XML response

<?xml version="1.0" encoding="UTF-8"?>
<ServiceResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="<qualys_base_url>/qps/xsd/3.0/was/finding.xsd">
    <responseCode>SUCCESS</responseCode>
    <count>1</count>
    <data>
        <Finding>
            <id>2774812</id>
            <uniqueId>af45db08-80c6-4527-a48a-9759450b21a2</uniqueId>
            <retest>
                <retestStatus>RETESTED</retestStatus>
                <retestedDate>2020-10-30T09:03:11Z</retestedDate>
                <findingStatus>Finding has been detected</findingStatus>
                <reason>Finding was confirmed</reason>
            </retest>
        </Finding>
    </data>
</ServiceResponse>