Skip to main content

Callback After Single Chat Message Read Report

Function Description​

The App business server can use this callback to real-time monitor the read actions of users' single chat messages.

Precautions​

  • To enable the callback, it is necessary to configure the callback URL and activate the corresponding switch for this callback protocol. Configuration methods can be found in the Callback Explanation document.
  • The direction of the callback is an HTTP/HTTPS POST request initiated by OpenIM Server to the App backend.
  • After receiving the callback request, the App business server must verify whether the command parameter in the request URL is its SDKNAME parameter.
  • The APP business server must respond to this request within the timeout period.

Scenarios That May Trigger This Callback​

  • App users report single chat messages as read through the client.
  • App administrators set single chat messages as read through the REST API interface.

Timing of the Callback​

  • After the single chat message read report is successfully submitted.

Interface Description​

Request URL Example​

In the following example, the callback URL configured by the App is https://callbackurl.

https://callbackurl?command=$CallbackCommand&contenttype=json

Request Parameter Description​

ParameterDescription
httpsRequest protocol is HTTPS, method is POST
https://callbackurlCallback URL
CallbackCommandFixed value: callbackSingleMsgReadCommand
contenttypeFixed value: JSON
Header NameExample ValueMandatoryTypeDescription
operationID1646445464564RequiredstringoperationID for global link tracing

Request Packet Example​

{
  "callbackCommand": "callbackSingleMsgReadCommand",
  "sendID": "user123",
  "receiveID": "user456"
}

Request Packet Field Explanation​

FieldTypeDescription
callbackCommandstringCallback command, here for single chat message read callback
conversationIDstringConversation ID
userIDstringThe user who receives the message
ContentTypeint32Message Type
Seqs[]int64Read Message Sequence

Response Packet Example​

Successful Response​

Successfully received and processed the request for a user's read single chat message.

{
    "actionCode": 0,
    "errCode": 0,
    "errMsg": "Success",
    "errDlt": "",
    "nextCode": 0
}

Response Packet Field Explanation​

FieldValueDescription
actionCode0Indicates if the business system's callback was executed correctly. 0 means the operation was successful.
errCode20001Custom error code, ranging between 20001-29999. Set when actionCode is not 0; set when nextCode is not 1.
errMsg"An error message"Simple error message corresponding to the custom error code.
errDlt"Detailed error information"Detailed error information corresponding to the custom error code.
nextCode1Next step instruction, 1 means to refuse to continue executing, set when actionCode is 0.