Delete alert history
Purpose
This endpoint is used to clear historical Alert entries.
Request data
HTTPS method: DELETE
- Constants and parameters enclosed in curly brackets { } must be replaced with their values.
- Please see the following Request parameters section with the required and optional parameters tables for their values. The generic request format is as follows.
URL request format
https://{baseURL}/geofencing/{versionNumber}/alerts/history?key={Your_API_Key}&adminKey={Your_Admin_Key}&alertType={string}
curl command request format
curl -X DELETE 'https://{baseURL}/geofencing/{versionNumber}/alerts/history?key={Your_API_Key}&adminKey={Your_Admin_Key}&alertType={string}'
Request parameters
The following table describes the parameters that can be used in a request.
- Required parameters must be used or the call will fail.
- Optional parameters may be used.
- The order of request parameters is not important.
Note: There are no optional parameters in this endpoint.
Required parameters | Description |
---|---|
| The base URL for calling the API. |
| Service version. |
| An API Key valid for the requested service. |
| An Admin Key valid for the provided API Key. |
| Type of the Alerts to delete. |
Response data
Response body
1{2 "deleteAllTransitionAlertHistoryBefore": "ISO8601_timestamp",3 "deleteAllTransitionAlertHistoryBeforeStatus": "status",4 "deleteAllDwellAlertHistoryBefore": "ISO8601_timestamp",5 "deleteAllDwellAlertHistoryBeforeStatus": "status",6 "deleteAllObjectCountAlertHistoryBefore": "ISO8601_timestamp",7 "deleteAllObjectCountAlertHistoryBeforeStatus": "status",8 "deleteAllProximityAlertHistoryBefore": "ISO8601_timestamp",9 "deleteAllProximityAlertHistoryBeforeStatus": "status"10}
Response fields
The following table describes all of the fields that can appear in a response.
Optional fields | Description |
---|---|
| Timestamp (ISO 8601 format) marking the moment before the history of Transition Alerts will be deleted. |
| Status of the Transition Alerts deletion process. Live status can be
checked in the current options list. |
| Timestamp (ISO 8601 format) marking the moment before the history of Dwell Alerts will be deleted. |
| Status of the Dwell Alerts deletion process. Live status can be checked
in the current options list. |
| Timestamp (ISO 8601 format) marking the moment before the history of Object Count Alerts will be deleted. |
| Status of the Object Count Alerts deletion process. Live status can be
checked in the current options list. |
| Timestamp (ISO 8601 format) marking the moment before the history of Proximity Alerts will be deleted. |
| Status of the Proximity Alerts deletion process. Live status can be
checked in the current options list. |
Response codes
Code | Meaning & possible causes |
---|---|
| OK: Deletion of history has begun. |
| Forbidden:
|
Examples
Clear historical Transition Alert entries
URL request example
https://api.tomtom.com/geofencing/1/alerts/history?key=PJD7y0G5AFj9Jiok6F0tIK16NiWYotb3&adminKey=FTZYUH7KxeNQohCuRvK8&alertType=TRANSITION
Response body example
1{2 "deleteAllTransitionAlertHistoryBefore": "2020-02-20T08:32:20.843Z",3 "deleteAllTransitionAlertHistoryBeforeStatus": "PROCESSING"4}
Clear all historical Alert entries.
URL request example
https://api.tomtom.com/geofencing/1/alerts/history?key=PJD7y0G5AFj9Jiok6F0tIK16NiWYotb3&adminKey=FTZYUH7KxeNQohCuRvK8&alertType=ALL
Response body example
1{2 "deleteAllTransitionAlertHistoryBefore": "2020-02-20T08:33:07.502Z",3 "deleteAllTransitionAlertHistoryBeforeStatus": "DELETED",4 "deleteAllDwellAlertHistoryBefore": "2020-02-20T08:33:07.502Z",5 "deleteAllDwellAlertHistoryBeforeStatus": "PROCESSING",6 "deleteAllObjectCountAlertHistoryBefore": "2020-02-20T08:33:07.502Z",7 "deleteAllObjectCountAlertHistoryBeforeStatus": "PROCESSING",8 "deleteAllProximityAlertHistoryBefore": "2020-02-20T08:33:07.502Z",9 "deleteAllProximityAlertHistoryBeforeStatus": "PROCESSING"10}