Delete Historical Message Logs
Delete the historical message log files for all conversations of the specified day and hour under the App saved on the server.
- The message log files saved on the server are retained for only 3 days. After 3 days, the server automatically deletes these log files.
- If you actively delete them through this API, the log files will be permanently deleted within 10 minutes after the deletion interface returns success. Once deleted, the historical message log files can no longer be retrieved from the server.
This function only deletes the historical message log files saved on the server. If the App has enabled the Cloud Storage for One-to-One and Group Messages feature, deleting the historical message logs will not affect the historical messages saved on the server.
Request Method
POST: https://Data Center Domain/message/history/delete.json
Rate Limit: 100 requests per second
Signature Rule: All server-side API requests must undergo rule verification. For details, see API Request Signature.
Body Parameters
The HTTP request body data format is application/x-www-form-urlencoded, and the following HTTP form parameters are supported:
| Parameter | Type | Required | Description |
|---|---|---|---|
| date | String | Yes | Specifies the time, accurate to the day and hour, in the format YYYYMMDDHH. For example, 2014010101 indicates that the data from 1:00 AM to 2:00 AM on January 1, 2014, should be deleted. After the success response, the message log files will be permanently deleted within the next 10 minutes.Note: The value of date is related to the data center to which the App belongs. If your App uses the Singapore Data Center, the time (date) used to retrieve the message logs and the message time (dateTime) in the logs are both in UTC time. If you still need to download data based on Beijing time, please convert it yourself. For example, to download the log for 9:00 AM Beijing time on 2019120109, you need to input 2019120101. |
Request Example
POST /message/history/delete.json HTTP/1.1
Host: api.rong-api.com
App-Key: uwd1c0sxdlx2
Timestamp: 1408710653491
Nonce: 14314
Signature: 45beb7cc7307889a8e711219a47b7cf6a5b000e8
Content-Type: application/x-www-form-urlencoded
date=2014010101
Response
The HTTP response body contains a JSON object with the following structure:
| Return Value | Return Type | Description |
|---|---|---|
| code | Number | Return code, 200 indicates success. |
Response Example
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
{"code":200}