Platform API

Get sorted conversation list

Use Get sorted conversation list to retrieve a user's ordered conversation summaries together with total unread state. Supply conversationIDs to restrict the result, or omit it to page through the user's conversations.

HTTP request

POST {API_ADDRESS}/conversation/get_sorted_conversation_list

Request example

curl --request POST "${API_ADDRESS}/conversation/get_sorted_conversation_list" \
  --header "Content-Type: application/json; charset=utf-8" \
  --header "operationID: ${OPERATION_ID}" \
  --header "token: ${ADMIN_TOKEN}" \
  --data-raw '{
  "userID": "user_001",
  "conversationIDs": [
    "si_user_001_user_002"
  ],
  "pagination": {
    "pageNumber": 1,
    "showNumber": 20
  }
}'

Keep administrator tokens on trusted backend services only. Client applications should use user tokens issued by your backend.

Request body

{
  "userID": "user_001",
  "conversationIDs": [
    "si_user_001_user_002"
  ],
  "pagination": {
    "pageNumber": 1,
    "showNumber": 20
  }
}

Parameter	Required	Type	Description
userID	Yes	string	OpenIM user ID.
conversationIDs	No	array	Conversation IDs to include. Omit this field to read the user's conversations by page.
pagination	Yes	object	Pagination settings.
pagination.pageNumber	Yes	int	Page number, starting from 1.
pagination.showNumber	Yes	int	Number of records to return per page.

Response

OpenIM usually returns 200 OK when the request reaches the service. Use errCode in the JSON response to determine business success; errCode === 0 means the operation succeeded.

{
  "errCode": 0,
  "errMsg": "",
  "errDlt": "",
  "data": {
    "conversationTotal": 2,
    "unreadTotal": 3,
    "conversationElems": [
      {
        "conversationID": "si_user_001_user_002",
        "recvMsgOpt": 0,
        "unreadCount": 2,
        "IsPinned": false,
        "msgInfo": {
          "serverMsgID": "server_msg_001",
          "clientMsgID": "client_msg_001",
          "sessionType": 1,
          "sendID": "user_002",
          "recvID": "user_001",
          "senderName": "Jane",
          "faceURL": "https://example.com/avatar-jane.png",
          "groupID": "",
          "groupName": "",
          "groupFaceURL": "",
          "groupType": 0,
          "groupMemberCount": 0,
          "LatestMsgRecvTime": 1719800000000,
          "msgFrom": 100,
          "contentType": 101,
          "content": "{\"content\":\"hello\"}",
          "ex": ""
        }
      }
    ]
  }
}

Response fields

Field	Type	Description
errCode	int	Business error code. `0` means success.
errMsg	string	Short error message.
errDlt	string	Detailed error information for troubleshooting.
data	object	Endpoint-specific response data.
data.conversationTotal	int	Total number of matching conversations.
data.unreadTotal	int	Total unread message count across the matching conversations.
data.conversationElems	array	Ordered summaries containing conversation ID, receive option, unread count, pinned state, and latest-message summary.

Error response

When a request fails, OpenIM returns the same error envelope. See Error codes for the full handling model.

{
  "errCode": 1004,
  "errMsg": "RecordNotFoundError",
  "errDlt": ": [1004]RecordNotFoundError"
}

Scenario	Possible cause	Recommended action
Authentication failed	`token` is missing, expired, or not an administrator token.	Issue a new administrator token and keep it on the backend.
Traceability is weak	`operationID` is missing or reused across many requests.	Generate a unique `operationID` for every request and log it with the response.
Validation failed	The request body has an invalid type, missing field, or unsupported enum value.	Compare the payload with the request table and retry after correcting the fields.

Permissions and limits

Call this endpoint from a trusted backend service.
Log operationID, the endpoint path, and the response error fields for troubleshooting.
Treat write operations as state-changing. If a retry follows an uncertain failure, check the resource state first.

Was this page helpful?