Here’s a list of Qualys API error codes along with a description of what each code means. For an API request that had an error, you’ll find the error code and text in the XML response.
|
HTTP Status |
Error Code |
Error Text |
Meaning |
|---|---|---|---|
|
HTTP/1.1 400 Bad Request |
1901 |
Unrecognized parameter(s):... |
The API request contained one or more parameters which are not supported, or are not available to the browsing user. |
|
HTTP/1.1 400 Bad Request |
1903 |
Missing required parameter(s):... |
The API request did not contain one or more parameters which are required. |
|
HTTP/1.1 400 Bad Request |
1904 |
Please specify only one of these parameters:... |
The API request contained 2 or more parameters from a group from which at most one may be specified. |
|
HTTP/1.1 400 Bad Request |
1905 |
parameter ... has invalid |
The API request contained a valid parameter specified with an invalid value. |
|
HTTP/1.1 400 Bad Request |
1907 |
The following combination of key=value pairs is not supported:... |
The API request contained an invalid or unsupported combination of parameters. |
|
HTTP/1.1 400 Bad Request |
1908 |
Request method (GET or POST) is incompatible with specified parameter(s):... |
The API request was made with an unsupported HTTP request method (GET or POST or PUT or DELETE or HEAD). |
|
HTTP/1.1 409 Conflict |
1920 |
The requested operation is blocked by one or more existing Business Objects |
The API request was blocked by other API requests. In practice this should be replaced by one of error code 1960 or 1965 (see below). |
|
HTTP/1.1 409 Conflict |
1960 |
The requested operation is blocked by one or more existing Business Objects |
Too many other API requests currently running (i.e. concurrency limit). |
|
HTTP/1.1 400 Conflict |
1965 |
The requested operation is blocked by one or more existing Business Objects |
Too many other API requests have run recently (i.e. rate limit). |
|
HTTP/1.1 400 Bad Request |
1922 |
Please specify at least one of the following parameters:... |
The API request was missing some required information (but not necessarily a single specific parameter). |
|
HTTP/1.1 202 Accepted |
1981 |
Your request is being processed. Please try this same request again later. |
The API request is for a business operation which is already underway. |
|
HTTP/1.1 400 Bad Request |
999 |
Internal Error |
The API request failed for some reason having to do with the (client) request. In practice this should always be expressed as some other error type, giving more information about what was actually wrong with the request. |
|
HTTP/1.1 501 Internal Error |
999 |
Internal Error |
The API request failed due to a problem with QWEB. |
|
HTTP/1.1 503 Maintenance |
1999 |
We are performing scheduled maintenance on our System. We apologize for any inconvenience. |
The API request failed because the Qualys Cloud Platform is in maintenance mode. |
|
HTTP/1.1 401 Unauthorized |
2000 |
Bad Login/Password |
The API request failed because of an authentication failure. |
|
HTTP/1.1 403 Forbidden |
2002 |
User account is inactive. |
The API request failed because of an authorization failure. |
|
HTTP/1.1 409 Conflict |
2003 |
Registration must be completed before API requests will be served for this account |
The API request failed because nobody has yet accepted the EULA on behalf of the user’s subscription. |
|
HTTP/1.1 409 Conflict |
2011 |
SecureID authentication is required for this account, so API access is blocked. |
The API request failed because SecureID authentication won't work with API calls. |
|
HTTP/1.1 403 Forbidden |
2012 |
User license is not authorized to run this API. |
The API request failed because the user’s subscription does not have API access enabled. |
Note: For msp Users API requests, the server returns HTTP 200 status code in the response irrespective of whether it is successful or an error.