Getting a list of all status codes for a domain or subdomain¶
Note
The user must have at least READ permissions during the selected time period.
Note
Domains and subdomains for which a user has no permissions are skipped.
Note
At least one attribute domains or subDomains must be defined in the body.
Sends a POST request to the endpoint /statistics/http-status-codes/{startTime}/{finishTime}.
Description¶
The Get-Status-Codes-For-A-Domain request allows the user to request a list of all status codes for one or more domains or subdomains for the selected time period.
Requirements¶
Values of the request: Start Date {startTime}; End Date {finishTime}
Objects: StatisticsVO
Request¶
To get a list of all status codes for one or more domains or subdomains, the start time and end time as unix timestamp need to be added to the path of the request.
For a detailed specification of which information is required to get a statistic, the following attributes need to be defined in the body:
| Attributes | Description | Values |
|---|---|---|
domains |
An array with the names of the domains.NoteTo include a domain with all its subdomains, the attribute subDomains must be empty. |
string |
subDomains |
An array with the names of the subdomains.NoteTo include only specific subdomains, the attribute Domains can be empty. |
string |
As a result, the user gets a statistics object for each analysis category for the selected domains or subdomains.
The object provides the following information:
| Attributes | Description | Values |
|---|---|---|
status_code |
The HTTP status codes. | integer |
value |
The total number of requests for the status code. | integer |
Example¶
Example request body:
Responses¶
The following responses are available:
| STATUS CODE | DESCRIPTION |
|---|---|
| 201 | The request has succeeded and a new object has been created. |
| 400 | The request was unsuccessful. The request was invalid or information is missing. |
| 401 | The request has not succeeded because the user authentication was incorrect. |
| 403 | The request has not succeeded because the user does not have the right permissions. |