Clear notifications history
Purpose
This endpoint clears the history of sent notifications.
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}/notifications/{versionNumber}/history?key={Your_API_Key}
curl command request format
curl -XDELETE 'https://{baseURL}/notifications/{versionNumber}/history?key={Your_API_Key}'
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 |
---|---|
string | The base URL for calling the API. Value: |
string | Service version. Value: |
string | An API Key valid for the requested service. Value: Your valid |
Response data
Response body
1{2 "deleteAllHistoryMessagesBefore": "ISO8601_timestamp",3 "deleteAllHistoryMessagesBeforeStatus": "status"4}
Response fields
The following table describes all of the fields that can appear in a response.
Primary fields | Description |
---|---|
string | Timestamp (ISO 8601 format) marking the moment before the history will be deleted. |
string | Status of the deletion process. Live status can be checked in the current options list. Value : PROCESSING |
Response codes
Code | Meaning & possible causes |
---|---|
| OK : Deletion of history has begun. |
Example
Request URL
https://api.tomtom.com/notifications/1/history?key={Your_API_Key}
Response body
1{2 "deleteAllHistoryMessagesBefore": "2019-08-12T08:32:20.843Z",3 "deleteAllHistoryMessagesBeforeStatus": "PROCESSING"4}