You can call this setPersonInfo operation to modify the name and description of an individual.
QPS limits
You can call this operation up to 20 times per second per account. If the number of calls per second exceeds the limit, throttling is triggered. As a result, your business may be affected. We recommend that you take note of the limit when you call this operation.
Request syntax
POST /green/sface/person/update HTTPS|HTTPRequest headers
This operation uses only common request headers. For more information, see Common request headers.
Request parameters
Parameter | Type | Required | Example | Description |
clientInfo | JSONObject | No | {"userId":"120234234","userNick":"Mike","userType":"others"} | The client information that is serialized from the ClientInfo structure in the JSON format. The information includes the unique machine identifier (UMID) and International Mobile Equipment Identity (IMEI) of the client. For more information, see ClientInfo. |
RequestBody
You must also specify the following parameters in RequestBody to specify individual information.
Parameter | Type | Required | Example | Description |
personId | String | Yes | person1 | The ID of the individual to be operated. |
name | String | No | Tom | Specifies the name of the individual. |
note | String | No | Male | Specifies the description of an individual. |
Response parameters
JSON-formatted data is returned for all requests. For more information about common response parameters, see Common response parameters. The data parameter in the response is used to return business-related data. In general, the value of this parameter is a JSON structure or array.
The data parameter may be empty when an error occurs.
The following table describes the parameters that are returned in the data field.
Parameter | Type | Example | Description |
code | Integer | 200 | The returned HTTP status code. For more information, see Common error codes. |
personId | String | person1 | The ID of the individual. |
Examples
Sample requests
POST /green/sface/person/update HTTP/1.1
Common request headers
{
"personId": "person1",
"name": "Tom",
"note": "Male"
}Sample success responses
{
"msg": "OK",
"code": 200,
"requestId": "36D384DA-8023-4E84-BCFD-0C5581352C16",
"data": {
"code": 200,
"personId": "person1"
}
}Error codes
For a list of error codes, see Service error codes.