Platform API

Get groups info

Use Get groups info to retrieve profile data for a specified list of groups.

HTTP request

POST {API_ADDRESS}/group/get_groups_info

Request example

curl --request POST "${API_ADDRESS}/group/get_groups_info" \
  --header "Content-Type: application/json; charset=utf-8" \
  --header "operationID: ${OPERATION_ID}" \
  --header "token: ${ADMIN_TOKEN}" \
  --data-raw '{
  "groupIDs": [
    "group_001",
    "group_002"
  ]
}'

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

Request body

{
  "groupIDs": [
    "group_001",
    "group_002"
  ]
}

Parameter	Required	Type	Description
groupIDs	Yes	array	List of OpenIM group IDs.

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": {
    "groupInfos": [
      {
        "groupID": "group_001",
        "groupName": "Product Discussion",
        "notification": "Welcome to OpenIM",
        "introduction": "Group for product discussions",
        "faceURL": "https://example.com/group.png",
        "ownerUserID": "user_owner",
        "createTime": 1719800000000,
        "memberCount": 3,
        "ex": "",
        "status": 0,
        "creatorUserID": "user_owner",
        "groupType": 2,
        "needVerification": 0,
        "lookMemberInfo": 0,
        "applyMemberFriend": 0,
        "notificationUpdateTime": 0,
        "notificationUserID": ""
      }
    ]
  }
}

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.groupInfos	array	Matching profiles. Each item follows `GroupInfo`.

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?