Get the history of a monitoring check
| Name | Data Type | Status | Description |
| auth-id | Integer | Required | Authentication parameter |
| auth-password | String | Required | Authentication parameter |
| id | Integer | Required | The ID of the monitoring check |
| page | Integer | Required | Page number starting from 1. |
| rows-per-page | Integer | Required | Results per page. Can be 10, 20, 30, 50, or 100. |
When the authentication of API user is not correct, any API request will fail with the following status and statusDescription:
{"status":"Failed","statusDescription":"Invalid authentication, incorrect auth-id or auth-password."}
If the entered ID of the monitoring check is invalid, the following status will be returned:
{"status":"Failed","statusDescription":"Invalid id param."}
If there is not added a value for "page", the following status will be returned:
{"status":"Failed","statusDescription":"Missing required parameter 'page'"}
If there is not added a value for "rows-per-page", the following status will be returned:
{"status":"Failed","statusDescription":"Wrong or missing required parameter 'rows-per-page'."}
Note: These are example errors in JSON format, and these are not the only errors that can be displayed.
URL JSON: https://api.cloudns.net/monitoring/get-history.json
POST/GET: auth-id=0&auth-password=password&id=12&page=1&rows-per-page=10
URL XML: https://api.cloudns.net/monitoring/get-history.xml
POST/GET: auth-id=0&auth-password=password&id=12&page=1&rows-per-page=10