Platform API
List user requested group applications
Use List a user's group applications to page through join requests submitted by a specified user.
HTTP request
POST {API_ADDRESS}/group/get_user_req_group_applicationListRequest example
curl --request POST "${API_ADDRESS}/group/get_user_req_group_applicationList" \
--header "Content-Type: application/json; charset=utf-8" \
--header "operationID: ${OPERATION_ID}" \
--header "token: ${ADMIN_TOKEN}" \
--data-raw '{
"userID": "user_002",
"groupIDs": [
"group_001"
],
"handleResults": [
0
],
"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_002",
"groupIDs": [
"group_001"
],
"handleResults": [
0
],
"pagination": {
"pageNumber": 1,
"showNumber": 20
}
}| Parameter | Required | Type | Description |
|---|---|---|---|
| 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. |
| userID | Yes | string | OpenIM user ID. |
| groupIDs | No | array | List of OpenIM group IDs. |
| handleResults | No | array | Filter by result. Values follow GroupRequestResult. |
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": {
"total": 1,
"groupRequests": [
{
"userInfo": {
"userID": "user_002",
"nickname": "Jane",
"faceURL": "https://example.com/avatar-jane.png",
"ex": ""
},
"groupInfo": {
"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": ""
},
"handleResult": 0,
"reqMsg": "Example value",
"handleMsg": "",
"reqTime": 1719800000000,
"handleUserID": "",
"handleTime": 0,
"ex": "",
"joinSource": 3,
"inviterUserID": ""
}
]
}
}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.total | int | Total number of matching records. |
| data.groupRequests | array | Submitted requests. Each item follows GroupRequestInfo. |
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.
Related pages
Was this page helpful?