Enterprise TruRisk™ Platform Release 10.34 API 

May 2, 2025

Before understanding the API release highlights, learn more about the API server URL to be used in your API requests by referring to the Know Your Qualys API Server URL section. For this API Release Notes, <qualys_base_url> is mentioned in the sample API requests.

We have implemented versioning for APIs. For more information on API versioning, refer to the Introducing API Versioning: A Strategic Upgrade for Enhanced Stability and Control for API Integrations blog.

Qualys Vulnerability Management (VM)

Host List API: Support for Authentication Status in VM Authentication Records

New or Updated API Updated
API Endpoint (deprecation Timeline - September 2025)  /api/4.0/fo/asset/host
API Endpoint
(New Version)

 /api/5.0/fo/asset/host
Method GET
DTD or XSD changes Yes

We have introduced a new tag, VM_AUTH_INSUFFICIENT_PRIVILEGE, in the API response to enhance user experience with VM records. This tag allows you to easily identify hosts with insufficient authentication privileges, leading to more accurate and consistent tracking. Now, when you scan a host with multiple authentication records, you can easily identify any records that lack the necessary privileges, ensuring you have a complete view of your security posture. Previously, the authentication status in the host list API did not provide a comprehensive overview, making it difficult to identify hosts with insufficient privileges during scans. This enhancement streamlines your vulnerability management process and helps you maintain a stronger security framework. 

 This is applicable to only Vulnerability Management (VM).

Sample - Display VM authentication insufficient privilledge status     Sample - Display VM authentication insufficient privilledge status     

API  Request

curl --location 'https://
<qualys_base_url>/api/5.0/fo/asset/host/?action=list&details=All&truncation_limit=0&ids=5811143' \
--header 'X-Requested-With: curl demo 2' \
--header 'Authorization: Basic Encoded username:passwordstring'

API Response

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE HOST_LIST_OUTPUT SYSTEM "https://
<qualys_base_url>/api/5.0/fo/asset/host/dtd/list/output.dtd">
    <HOST_LIST_OUTPUT>
        <RESPONSE>
            <DATETIME>2025-04-21T11:58:09Z</DATETIME>
            <HOST_LIST>
                <HOST>
                    <ID>5811143</ID>
                    <IP>11.11.11.11</IP>
                    <TRACKING_METHOD>DNS</TRACKING_METHOD>
                    <NETWORK_ID>0</NETWORK_ID>
                    <DNS>
                        <![CDATA[w2k3r2-2.vuln.qa.qualys.com]]>
                    </DNS>
                    <DNS_DATA>
                        <HOSTNAME>
                            <![CDATA[w2k3r2-2]]>
                        </HOSTNAME>
                        <DOMAIN>
                            <![CDATA[vuln.qa.qualys.com]]>
                        </DOMAIN>
                        <FQDN>
                            <![CDATA[w2k3r2-2.vuln.qa.qualys.com]]>
                        </FQDN>
                    </DNS_DATA>
                    <OS>
                        <![CDATA[Red Hat Linux 7.3]]>
                    </OS>
                    <FIRST_FOUND_DATE>2024-07-02T09:52:57Z</FIRST_FOUND_DATE>
                    <LAST_VULN_SCAN_DATETIME>2025-04-09T05:33:21Z</LAST_VULN_SCAN_DATETIME>
                    <LAST_VM_SCANNED_DATE>2025-04-09T05:33:21Z</LAST_VM_SCANNED_DATE>
                    <LAST_VM_SCANNED_DURATION>59</LAST_VM_SCANNED_DURATION>
                    <LAST_VM_AUTH_SCANNED_DATE>2025-04-09T05:33:21Z</LAST_VM_AUTH_SCANNED_DATE>
                    <LAST_VM_AUTH_SCANNED_DURATION>59</LAST_VM_AUTH_SCANNED_DURATION>
                    <VM_AUTH_INSUFFICIENT_PRIVILEGE>Yes</VM_AUTH_INSUFFICIENT_PRIVILEGE>
                </HOST>
            </HOST_LIST>
        </RESPONSE>
    </HOST_LIST_OUTPUT>

DTD OutputDTD Output

A DTD for the Host List API has been added.
<platform API server>  /api/5.0/fo/asset/host/dtd/list/output.dtd

DTD output for the Host List API is as follows:

DTD Output

<!-- QUALYS HOST_OUTPUT DTD FOR LIST ACTION-->
<!ELEMENT HOST_LIST_OUTPUT (REQUEST?,RESPONSE)>
<!ELEMENT REQUEST (DATETIME, USER_LOGIN, RESOURCE, PARAM_LIST?, POST_DATA?)>
<!ELEMENT DATETIME (#PCDATA)>
<!ELEMENT USER_LOGIN (#PCDATA)>
<!ELEMENT RESOURCE (#PCDATA)>
<!ELEMENT PARAM_LIST (PARAM+)>
<!ELEMENT PARAM (KEY, VALUE)>
<!ELEMENT KEY (#PCDATA)>
<!ELEMENT VALUE (#PCDATA)>
<!-- if returned, POST_DATA will be urlencoded -->
<!ELEMENT POST_DATA (#PCDATA)>
<!ELEMENT RESPONSE (DATETIME, (HOST_LIST|ID_SET)?, WARNING?, GLOSSARY?)>
<!ELEMENT HOST_LIST (HOST+)>
<!ELEMENT HOST (ID, ASSET_ID?, IP?, IPV6?, ASSET_RISK_SCORE?, TRURISK_SCORE?, ASSET_CRITICALITY_SCORE?, ARS_FACTORS?,TRURISK_SCORE_FACTORS?, TRACKING_METHOD?, NETWORK_ID?, OS_HOSTNAME?,
                DNS?, DNS_DATA?, CLOUD_PROVIDER?, CLOUD_SERVICE?, CLOUD_RESOURCE_ID?, EC2_INSTANCE_ID?, NETBIOS?, OS?, QG_HOSTID?, LAST_BOOT?, SERIAL_NUMBER?, HARDWARE_UUID?, FIRST_FOUND_DATE?, LAST_ACTIVITY?, AGENT_STATUS?, CLOUD_AGENT_RUNNING_ON?, AGENT_ACTIVATION_TITLE?, AGENT_ACTIVATION_KEY?,TAGS?, METADATA?,
                CLOUD_PROVIDER_TAGS?, LAST_VULN_SCAN_DATETIME?, LAST_VM_SCANNED_DATE?, LAST_VM_SCANNED_DURATION?,
                LAST_VM_AUTH_SCANNED_DATE?, LAST_VM_AUTH_SCANNED_DURATION?,
                LAST_COMPLIANCE_SCAN_DATETIME?, PC_AUTH_SUCCESS_DATE?, LAST_SCAP_SCAN_DATETIME?, VM_AUTH_INSUFFICIENT_PRIVILEGE?, OWNER?, COMMENTS?, USER_DEF?, ASSET_GROUP_IDS?)>
<!ELEMENT ID (#PCDATA)>
<!ELEMENT ASSET_ID (#PCDATA)>
<!ELEMENT IP (#PCDATA)>
<!ELEMENT IPV6 (#PCDATA)>
<!ELEMENT ASSET_RISK_SCORE (#PCDATA)>
<!ELEMENT TRURISK_SCORE (#PCDATA)>
<!ELEMENT ASSET_CRITICALITY_SCORE (#PCDATA)>
<!ELEMENT ARS_FACTORS (ARS_FORMULA, VULN_COUNT*)>
<!ELEMENT ARS_FORMULA (#PCDATA)>
<!ELEMENT TRURISK_SCORE_FACTORS (TRURISK_SCORE_FORMULA, VULN_COUNT*)>
<!ELEMENT TRURISK_SCORE_FORMULA (#PCDATA)>
<!ELEMENT VULN_COUNT (#PCDATA)>
<!ATTLIST VULN_COUNT qds_severity CDATA #REQUIRED>
<!ELEMENT TRACKING_METHOD (#PCDATA)>
<!ELEMENT NETWORK_ID (#PCDATA)>
<!ELEMENT OS_HOSTNAME (#PCDATA)>
<!ELEMENT DNS (#PCDATA)>
<!ELEMENT DNS_DATA (HOSTNAME?, DOMAIN?, FQDN?)>
<!ELEMENT HOSTNAME (#PCDATA)>
<!ELEMENT DOMAIN (#PCDATA)>
<!ELEMENT FQDN (#PCDATA)>
<!ELEMENT EC2_INSTANCE_ID (#PCDATA)>
<!ELEMENT CLOUD_PROVIDER (#PCDATA)>
<!ELEMENT CLOUD_SERVICE (#PCDATA)>
<!ELEMENT CLOUD_RESOURCE_ID (#PCDATA)>
<!ELEMENT NETBIOS (#PCDATA)>
<!ELEMENT OS (#PCDATA)>
<!ELEMENT QG_HOSTID (#PCDATA)>
<!ELEMENT LAST_BOOT (#PCDATA)>
<!ELEMENT SERIAL_NUMBER (#PCDATA)>
<!ELEMENT HARDWARE_UUID (#PCDATA)>
<!ELEMENT FIRST_FOUND_DATE (#PCDATA)>
<!ELEMENT LAST_ACTIVITY (#PCDATA)>
<!ELEMENT AGENT_STATUS (#PCDATA)>
<!ELEMENT CLOUD_AGENT_RUNNING_ON (#PCDATA)>
<!ELEMENT AGENT_ACTIVATION_TITLE (#PCDATA)>
<!ELEMENT AGENT_ACTIVATION_KEY (#PCDATA)>
<!ELEMENT TAGS (TAG*)>
<!ELEMENT TAG (TAG_ID?, NAME?)>
<!ELEMENT TAG_ID (#PCDATA)>
<!ELEMENT NAME (#PCDATA)>
<!ELEMENT LAST_VULN_SCAN_DATETIME (#PCDATA)>
<!ELEMENT LAST_VM_SCANNED_DATE (#PCDATA)>
<!ELEMENT LAST_VM_SCANNED_DURATION (#PCDATA)>
<!ELEMENT LAST_VM_AUTH_SCANNED_DATE (#PCDATA)>
<!ELEMENT LAST_VM_AUTH_SCANNED_DURATION (#PCDATA)>
<!ELEMENT LAST_COMPLIANCE_SCAN_DATETIME (#PCDATA)>
<!ELEMENT PC_AUTH_SUCCESS_DATE (#PCDATA)>
<!ELEMENT LAST_SCAP_SCAN_DATETIME (#PCDATA)>
<!ELEMENT VM_AUTH_INSUFFICIENT_PRIVILEGE (#PCDATA)>
<!ELEMENT OWNER (#PCDATA)>
<!ELEMENT COMMENTS (#PCDATA)>
<!ELEMENT USER_DEF (LABEL_1?, LABEL_2?, LABEL_3?, VALUE_1?, VALUE_2?, VALUE_3?)>
<!ELEMENT LABEL_1 (#PCDATA)>
<!ELEMENT LABEL_2 (#PCDATA)>
<!ELEMENT LABEL_3 (#PCDATA)>
<!ELEMENT VALUE_1 (#PCDATA)>
<!ATTLIST VALUE_1
ud_attr CDATA #REQUIRED>
<!ELEMENT VALUE_2 (#PCDATA)>
<!ATTLIST VALUE_2
ud_attr CDATA #REQUIRED>
<!ELEMENT VALUE_3 (#PCDATA)>
<!ATTLIST VALUE_3
ud_attr CDATA #REQUIRED>
<!ELEMENT METADATA (EC2|GOOGLE|AZURE)+>
<!ELEMENT EC2 (ATTRIBUTE*)>
<!ELEMENT GOOGLE (ATTRIBUTE*)>
<!ELEMENT AZURE (ATTRIBUTE*)>
<!ELEMENT ATTRIBUTE (NAME,LAST_STATUS,VALUE,LAST_SUCCESS_DATE?,LAST_ERROR_DATE?,LAST_ERROR?)>
<!ELEMENT LAST_STATUS (#PCDATA)>
<!ELEMENT LAST_SUCCESS_DATE (#PCDATA)>
<!ELEMENT LAST_ERROR_DATE (#PCDATA)>
<!ELEMENT LAST_ERROR (#PCDATA)>
<!ELEMENT CLOUD_PROVIDER_TAGS (CLOUD_TAG+)>
<!ELEMENT CLOUD_TAG (NAME, VALUE, LAST_SUCCESS_DATE)>
<!ELEMENT ASSET_GROUP_IDS (#PCDATA)>
<!ELEMENT ID_SET ((ID|ID_RANGE)+)>
<!ELEMENT ID_RANGE (#PCDATA)>
<!ELEMENT WARNING (CODE?, TEXT, URL?)>
<!ELEMENT CODE (#PCDATA)>
<!ELEMENT TEXT (#PCDATA)>
<!ELEMENT URL (#PCDATA)>
<!ELEMENT GLOSSARY (USER_DEF?, USER_LIST?, ASSET_GROUP_LIST?)>
<!ELEMENT USER_LIST (USER+)>
<!ELEMENT USER (USER_LOGIN, FIRST_NAME, LAST_NAME)>
<!ELEMENT FIRST_NAME (#PCDATA)>
<!ELEMENT LAST_NAME (#PCDATA)>
<!ELEMENT ASSET_GROUP_LIST (ASSET_GROUP+)>
<!ELEMENT ASSET_GROUP (ID, TITLE)>
<!ELEMENT TITLE (#PCDATA)>
<!-- EOF -->

List Last ‘N’ Scan References for a Schedule API: Updated Number of Search Results for Scheduled Scan

New or Updated API Updated
API Endpoint api/2.0/fo/scan/schedules/runhistory
Method GET
DTD or XSD changes No

With this release, we have updated the schedule_executions_count parameter to increase the number of search results displayed when running a scheduled scan. Previously, the results were limited to 10. Now, you can view up to 50 results, offering greater visibility and helping gain deeper insights.

Input ParametersInput Parameters

Parameter
Name		 Required/
Optional		 Data
Type 		  Description
schedule_executions_count={value} Optional  Integer Specify a schedule execution count. You can specify a value from 1 to 50. When not specified, 3 is taken as the default value.

 The request and the response for the API remain the same.

List Scan Schedules API: Display the Type of Scan Launch

New or Updated API Updated
API Endpoint (deprecation Timeline - October 2025) /api/3.0/fo/schedule/scan
API Endpoint
(New Version)

/api/4.0/fo/schedule/scan
Method GET, POST
DTD or XSD changes Yes

With this release, we have added a new tag, LAUNCH_TYPE, in the API response to display the type of the scheduled scan (now or recurring). This retrieved information is then displayed in TotalCloud (TC).

The tag LAUNCH_TYPE will be included in all types of Cloud Perimeter Scans and Azure Internal Scans.

Sample - List Scan ScheduleSample - List Scan Schedule

API Request

curl --location '<qualys_base_url>/api/4.0/fo/schedule/scan/index.php?action=list&id=1440922&show_cloud_details=1' \
--header 'X-Requested-With: e' \
--header 'Authorization: Basic c2Nhbl9hdDM6UUF0ZW1wMTIzIw=='

API Response

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE SCHEDULE_SCAN_LIST_OUTPUT SYSTEM "https://<qualys_base_url>/api/4.0/fo/schedule/scan/schedule_scan_list_output.dtd">
<SCHEDULE_SCAN_LIST_OUTPUT>
    <RESPONSE>
        <DATETIME>2025-04-17T06:10:18Z</DATETIME>
        <SCHEDULE_SCAN_LIST>
            <SCAN>
                <ID>1440922</ID>
                <ACTIVE>1</ACTIVE>
                <TITLE>
                    <![CDATA[Azure Internal Scan now]]>
                </TITLE>
                <USER_LOGIN>scan_at3</USER_LOGIN>
                <TARGET>
                    <![CDATA[]]>
                </TARGET>
                <NETWORK_ID>
                    <![CDATA[0]]>
                </NETWORK_ID>
                <ISCANNER_NAME>
                    <![CDATA[Azure_Internal_Scanner]]>
                </ISCANNER_NAME>
                <CLOUD_DETAILS>
                    <PROVIDER>AZURE</PROVIDER>
                    <CONNECTOR>
                        <ID>1071626</ID>
                        <UUID>f4597cc6-4854-487a-85e3-15eb1595e40c</UUID>
                        <NAME>
                            <![CDATA[Azure_Connector_p01_scan_at]]>
                        </NAME>
                    </CONNECTOR>
                    <SCAN_TYPE>Cloud Internal</SCAN_TYPE>
                    <CLOUD_TARGET>
                        <PLATFORM>LOCATION</PLATFORM>
                        <REGION>
                            <UUID>080380ed-483e-45d7-8838-c5e637750e54</UUID>
                            <CODE>eastus</CODE>
                            <NAME>
                                <![CDATA[East US]]>
                            </NAME>
                        </REGION>
                    </CLOUD_TARGET>
                </CLOUD_DETAILS>
                <OPTION_PROFILE>
                    <TITLE>
                        <![CDATA[defaultOP_2025-04-11_00-49-54-751]]>
                    </TITLE>
                    <DEFAULT_FLAG>0</DEFAULT_FLAG>
                </OPTION_PROFILE>
                <PROCESSING_PRIORITY>0 - No Priority</PROCESSING_PRIORITY>
                <SCHEDULE>
                    <DAILY frequency_days="1" />
                    <START_DATE_UTC>2025-04-11T04:23:00Z</START_DATE_UTC>
                    <START_HOUR>9</START_HOUR>
                    <START_MINUTE>53</START_MINUTE>
                    <NEXTLAUNCH_UTC>2025-04-17T06:24:35</NEXTLAUNCH_UTC>
                    <TIME_ZONE>
                        <TIME_ZONE_CODE>IN</TIME_ZONE_CODE>
                        <TIME_ZONE_DETAILS>(GMT+0530) India: Asia/Calcutta</TIME_ZONE_DETAILS>
                    </TIME_ZONE>
                    <DST_SELECTED>0</DST_SELECTED>
                    <MAX_OCCURRENCE>1</MAX_OCCURRENCE>
                    <LAUNCH_TYPE>now</LAUNCH_TYPE>
                </SCHEDULE>
            </SCAN>
        </SCHEDULE_SCAN_LIST>
    </RESPONSE>
</SCHEDULE_SCAN_LIST_OUTPUT>


DTD OutputDTD Output

A DTD for the List Scan Schedules API has been added.
<platform API server> /api/4.0/fo/schedule/scan/schedule_scan_list_output.dtd

DTD output for the List Scan Schedules API is as follows:

DTD Output

<!-- QUALYS SCHEDULE_SCAN_LIST_OUTPUT DTD -->
<!ELEMENT SCHEDULE_SCAN_LIST_OUTPUT (REQUEST?,RESPONSE)>
<!ELEMENT REQUEST (DATETIME, USER_LOGIN, RESOURCE, PARAM_LIST?, POST_DATA?)>
<!ELEMENT DATETIME (#PCDATA)>
<!ELEMENT USER_LOGIN (#PCDATA)>
<!ELEMENT RESOURCE (#PCDATA)>
<!ELEMENT PARAM_LIST (PARAM+)>
<!ELEMENT PARAM (KEY, VALUE)>
<!ELEMENT KEY (#PCDATA)>
<!ELEMENT VALUE (#PCDATA)>
<!-- if returned, POST_DATA will be urlencoded -->
<!ELEMENT POST_DATA (#PCDATA)>
<!ELEMENT RESPONSE (DATETIME, SCHEDULE_SCAN_LIST?)>
<!ELEMENT SCHEDULE_SCAN_LIST (SCAN+)>
<!ELEMENT SCAN (ID, SCAN_TYPE?, ACTIVE, TITLE?, CLIENT?, USER_LOGIN, TARGET, NETWORK_ID?, ISCANNER_NAME?, POOL_OF_SCANNERS?, EC2_INSTANCE?, CLOUD_DETAILS?, ASSET_GROUP_TITLE_LIST?, ASSET_TAGS?, EXCLUDE_IP_PER_SCAN?, USER_ENTERED_IPS?, USER_ENTERED_IPv6_IPS?, ELB_DNS?,MANUAL_CLOUD_RESOURCE_IDS?, OPTION_PROFILE?, PROCESSING_PRIORITY?, SCHEDULE, NOTIFICATIONS?)>
<!ELEMENT ID (#PCDATA)>
<!ELEMENT ACTIVE (#PCDATA)>
<!ELEMENT TITLE (#PCDATA)>
<!ELEMENT CLIENT (ID,NAME)>
<!ELEMENT TARGET (#PCDATA)>
<!ELEMENT NETWORK_ID (#PCDATA)>
<!ELEMENT ISCANNER_NAME (#PCDATA)>
<!ELEMENT POOL_OF_SCANNERS (#PCDATA)>
<!ELEMENT EC2_INSTANCE (CONNECTOR_UUID, EC2_ENDPOINT, EC2_ONLY_CLASSIC?)>
<!ELEMENT CONNECTOR_UUID (#PCDATA)>
<!ELEMENT EC2_ENDPOINT (#PCDATA)>
<!ELEMENT EC2_ONLY_CLASSIC (#PCDATA)>
<!ELEMENT CLOUD_DETAILS (PROVIDER, CONNECTOR?, SCAN_TYPE, CLOUD_TARGET?)>
<!ELEMENT PROVIDER (#PCDATA)>
<!ELEMENT CONNECTOR (ID?, UUID, NAME)>
<!ELEMENT UUID (#PCDATA)>
<!ELEMENT NAME (#PCDATA)>
<!ELEMENT SCAN_TYPE (#PCDATA)>
<!ELEMENT CLOUD_TARGET (PLATFORM, REGION?, VPC_SCOPE?, VPC_LIST?, VIRTUAL_NETWORK?)>
<!ELEMENT PLATFORM (#PCDATA)>
<!ELEMENT REGION (UUID?, CODE?, NAME?)>
<!ELEMENT VIRTUAL_NETWORK (ID, NAME?, RESOURCE_GROUP)>
<!ELEMENT RESOURCE_GROUP (NAME)>
<!ELEMENT CODE (#PCDATA)>
<!ELEMENT VPC_SCOPE (#PCDATA)>
<!ELEMENT VPC_LIST (VPC+)>
<!ELEMENT VPC (UUID)>
<!ELEMENT ASSET_GROUP_TITLE_LIST (ASSET_GROUP_TITLE+)>
<!ELEMENT ASSET_GROUP_TITLE (#PCDATA)>
<!ELEMENT ASSET_TAGS (TAG_INCLUDE_SELECTOR, TAG_SET_INCLUDE, TAG_EXCLUDE_SELECTOR?, TAG_SET_EXCLUDE?, USE_IP_NT_RANGE_TAGS?, USE_IP_NT_RANGE_TAGS_INCLUDE, USE_IP_NT_RANGE_TAGS_EXCLUDE?)>
<!ELEMENT TAG_INCLUDE_SELECTOR (#PCDATA)>
<!ELEMENT TAG_SET_INCLUDE (#PCDATA)>
<!ELEMENT TAG_EXCLUDE_SELECTOR (#PCDATA)>
<!ELEMENT TAG_SET_EXCLUDE (#PCDATA)>
<!ELEMENT USE_IP_NT_RANGE_TAGS (#PCDATA)>
<!ELEMENT USE_IP_NT_RANGE_TAGS_INCLUDE (#PCDATA)>
<!ELEMENT USE_IP_NT_RANGE_TAGS_EXCLUDE (#PCDATA)>
<!ELEMENT EXCLUDE_IP_PER_SCAN (#PCDATA)>
<!ELEMENT USER_ENTERED_IPS (RANGE+)>
<!ELEMENT USER_ENTERED_IPv6_IPS (RANGE+)>
<!ELEMENT ELB_DNS (DNS+)>
<!ELEMENT DNS (#PCDATA)>
<!ELEMENT MANUAL_CLOUD_RESOURCE_IDS (CLOUD_RESOURCE_ID+)>
<!ELEMENT CLOUD_RESOURCE_ID (#PCDATA)>
<!ELEMENT RANGE (START, END)>
<!ELEMENT START (#PCDATA)>
<!ELEMENT END (#PCDATA)>
<!ELEMENT OPTION_PROFILE (TITLE, DEFAULT_FLAG?)>
<!ELEMENT DEFAULT_FLAG (#PCDATA)>
<!ELEMENT PROCESSING_PRIORITY (#PCDATA)>
<!ELEMENT SCHEDULE ((DAILY|WEEKLY|MONTHLY), START_DATE_UTC, START_HOUR, START_MINUTE, END_AFTER_HOURS?, END_AFTER_MINUTES?, PAUSE_AFTER_HOURS?, PAUSE_AFTER_MINUTES?, RESUME_IN_DAYS?, RESUME_IN_HOURS?, NEXTLAUNCH_UTC?, TIME_ZONE, DST_SELECTED, MAX_OCCURRENCE?, LAUNCH_TYPE?)>
<!ELEMENT DAILY EMPTY>
<!ATTLIST DAILY
                frequency_days  CDATA #REQUIRED>
<!-- weekdays is comma-separated list of weekdays e.g. 0,1,4,5 -->
<!ELEMENT WEEKLY EMPTY>
<!ATTLIST WEEKLY
                frequency_weeks  CDATA #REQUIRED
                weekdays   CDATA #REQUIRED>
<!-- either day of month, or (day of week and week of month) must be provided -->
<!ELEMENT MONTHLY EMPTY>
<!ATTLIST MONTHLY
                frequency_months  CDATA #REQUIRED
                day_of_month  CDATA  #IMPLIED
                day_of_week  (0|1|2|3|4|5|6)  #IMPLIED
                week_of_month  (1|2|3|4|5)  #IMPLIED>
<!-- start date of the task in UTC -->
<!ELEMENT START_DATE_UTC (#PCDATA)>
<!-- User Selected hour -->
<!ELEMENT START_HOUR (#PCDATA)>
<!-- User Selected Minute -->
<!ELEMENT START_MINUTE (#PCDATA)>
<!ELEMENT END_AFTER_HOURS (#PCDATA)>
<!ELEMENT END_AFTER_MINUTES (#PCDATA)>
<!ELEMENT PAUSE_AFTER_HOURS (#PCDATA)>
<!ELEMENT PAUSE_AFTER_MINUTES (#PCDATA)>
<!ELEMENT RESUME_IN_DAYS (#PCDATA)>
<!ELEMENT RESUME_IN_HOURS (#PCDATA)>
<!ELEMENT NEXTLAUNCH_UTC (#PCDATA)>
<!ELEMENT TIME_ZONE (TIME_ZONE_CODE, TIME_ZONE_DETAILS)>
<!-- timezone code like US-CA -->
<!ELEMENT TIME_ZONE_CODE (#PCDATA)>
<!-- timezone details like (GMT-0800) United States (California): Los Angeles, Sacramento, San Diego, San Francisco-->
<!ELEMENT TIME_ZONE_DETAILS (#PCDATA)>
<!-- Did user select DST? 0-not selected 1-selected -->
<!ELEMENT DST_SELECTED (#PCDATA)>
<!ELEMENT MAX_OCCURRENCE (#PCDATA)>
<!ELEMENT LAUNCH_TYPE (#PCDATA)>
<!-- notifications -->
<!ELEMENT NOTIFICATIONS (BEFORE_LAUNCH?, AFTER_COMPLETE?,LAUNCH_DELAY?, LAUNCH_SKIP?, DEACTIVATE_SCHEDULE?, DISTRIBUTION_GROUPS?)>
<!ELEMENT BEFORE_LAUNCH (TIME, UNIT, MESSAGE)>
<!ELEMENT TIME (#PCDATA)>
<!ELEMENT UNIT (#PCDATA)>
<!ELEMENT MESSAGE (#PCDATA)>
<!ELEMENT AFTER_COMPLETE (MESSAGE)>
<!ELEMENT LAUNCH_DELAY (MESSAGE)>
<!ELEMENT LAUNCH_SKIP (MESSAGE)>
<!ELEMENT DEACTIVATE_SCHEDULE (MESSAGE)>
<!ELEMENT DISTRIBUTION_GROUPS (DISTRIBUTION_GROUP+)>
<!ELEMENT DISTRIBUTION_GROUP (ID, TITLE)>
<!-- EOF -->


Issues Addressed

The following reported and notable customer API issue are fixed in this release:

Component/Category Application
 		 Description
VM - Users API Vulnerability Management When the users deactivated the sub-users using the API and needed to delete a sub-user by referring to the API User Guide, the documentation indicated that the Delete action was supported, but no instructions were provided. Since the API does not support the Delete action, we have now updated the API User Guide accordingly.
VM - Scan API Vulnerability Management When the users tried to execute a schedule scan API /api/2.0/fo/schedule/scan/?action=list, to display the list of schedule scans, an error was encountered. Relevant code changes have been made to fix the issue.
PC - API Policy Compliance When the users were launching the Compliance Scan API (api/2.0/fo/scan/compliance/) they received the error - Internal Error (999). Relevant code changes have been made to fix this issue.