Callback Before Updating User Information
Function Description
The App business server can use this callback to receive requests from users to update their personal information. Additionally, the business server can modify and intervene in the request.
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 update their personal information through the client.
- App administrators update user information through the REST API.
Timing of the Callback
- Before OpenIM Server prepares to update user information.
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
Parameter | Description |
---|---|
https | Request protocol is HTTPS, method is POST |
https://callbackurl | Callback URL |
CallbackCommand | Fixed value: callbackBeforeUpdateUserInfoExCommand |
contenttype | Fixed value: JSON |
Header
Header Name | Example Value | Mandatory | Type | Description |
---|---|---|---|---|
operationID | 1646445464564 | Required | string | operationID for global link tracing |
Request Packet Example
{
"callbackCommand": "callbackBeforeUpdateUserInfoExCommand",
"userID": "user123",
"nickName": "John Doe",
"faceURL": "http://example.com/path/to/face/image.png",
"ex": "Extra data"
}
Request Packet Field Explanation
Field | Type | Description |
---|---|---|
callbackCommand | string | Callback command, here for before updating user information |
userID | string | The unique identifier of the user |
nickName | StringValue | The nickname of the user |
faceURL | StringValue | URL of the user's avatar |
ex | StringValue | Additional data fields |
Response Packet Example
Allow Update
Allows the user to update their information.
{
"actionCode": 0,
"errCode": 0,
"errMsg": "",
"errDlt": "",
"nextCode": "0",
"nickName": "John Doe Updated",
"faceURL": "http://example.com/new/face/image.png",
"ex": "Updated extra data"
}
Response Packet Field Explanation
Field | Value | Description |
---|---|---|
actionCode | 0 | Indicates if the business system's callback was executed correctly. 0 means the operation was successful. |
errCode | 5001 | Custom error code, ranging between 5000-9999. 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. |
nextCode | 1 | Next step instruction, 1 means to refuse to continue executing, set when actionCode is 0 . |
nickName | StringValue | The nickname of the user. |
faceURL | StringValue | URL of the user's updated avatar. |
ex | StringValue | Updated additional data fields. |