Update User Data user.update
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
userWho can execute the method: administrator
The user.update method updates user data. It can only be executed on behalf of a user with user invitation rights.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
ID* |
User identifier |
|
ACTIVE |
User activity status. Possible values:
|
|
EMAIL |
User e-mail |
|
NAME |
First name |
|
LAST_NAME |
Last name |
|
SECOND_NAME |
Middle name |
|
PERSONAL_GENDER |
Gender |
|
PERSONAL_PROFESSION |
Profession |
|
PERSONAL_WWW |
Personal webpage |
|
PERSONAL_BIRTHDAY |
Date of birth |
|
PERSONAL_PHOTO |
Photo, pass an array with the filename and a string in Base64 |
|
PERSONAL_ICQ |
ICQ |
|
PERSONAL_PHONE |
Personal phone |
|
PERSONAL_FAX |
Fax |
|
PERSONAL_MOBILE |
Personal mobile |
|
PERSONAL_PAGER |
Pager |
|
PERSONAL_STREET |
Street of residence |
|
PERSONAL_CITY |
City of residence |
|
PERSONAL_STATE |
State |
|
PERSONAL_ZIP |
Postal code |
|
PERSONAL_COUNTRY |
Country |
|
PERSONAL_MAILBOX |
Mailbox |
|
PERSONAL_NOTES |
Additional notes |
|
WORK_PHONE |
Company phone |
|
WORK_COMPANY |
Company |
|
WORK_POSITION |
Position |
|
WORK_DEPARTMENT |
Department |
|
WORK_WWW |
Company website |
|
WORK_FAX |
WORK_FAX |
|
WORK_PAGER |
WORK_PAGER |
|
WORK_STREET |
WORK_STREET |
|
WORK_MAILBOX |
WORK_MAILBOX |
|
WORK_CITY |
City of work |
|
WORK_STATE |
WORK_STATE |
|
WORK_ZIP |
WORK_ZIP |
|
WORK_COUNTRY |
WORK_COUNTRY |
|
WORK_PROFILE |
WORK_PROFILE |
|
WORK_LOGO |
WORK_LOGO |
|
WORK_NOTES |
WORK_NOTES |
|
UF_SKYPE_LINK |
Skype chat link |
|
UF_ZOOM |
Zoom |
|
UF_DEPARTMENT |
Departments |
|
UF_INTERESTS |
Interests |
|
UF_SKILLS |
Skills |
|
UF_WEB_SITES |
Other websites |
|
UF_XING |
|
|
UF_LINKEDIN |
|
|
UF_FACEBOOK |
|
|
UF_TWITTER |
|
|
UF_SKYPE |
Skype |
|
UF_DISTRICT |
District |
|
UF_PHONE_INNER |
Internal phone |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"ID": 1,
"NAME": "Administrator",
"LAST_NAME": "SomeLastName"
}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/user.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"ID": 1,
"NAME": "Administrator",
"LAST_NAME": "SomeLastName",
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/user.update
try
{
const response = await $b24.callMethod(
"user.update",
{
"ID": 1,
"NAME": "Administrator",
"LAST_NAME": "SomeLastName"
}
);
const result = response.getData().result;
if(result.error())
{
console.error(result.error());
}
else
{
console.dir(result);
}
}
catch(error)
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'user.update',
[
'ID' => 1,
'NAME' => 'Administrator',
'LAST_NAME' => 'SomeLastName',
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
} else {
echo 'Success: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating user: ' . $e->getMessage();
}
BX24.callMethod(
"user.update",
{
"ID": 1,
"NAME": "Administrator",
"LAST_NAME": "SomeLastName"
},
function(result)
{
if(result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'user.update',
[
'ID' => 1,
'NAME' => 'Administrator',
'LAST_NAME' => 'SomeLastName'
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1721807581.02493,
"finish": 1721807581.20039,
"duration": 0.17546010017395,
"processing": 0.133708000183105,
"date_start": "2024-07-24T07:53:01+00:00",
"date_finish": "2024-07-24T07:53:01+00:00",
"operating": 0.133685827255249
}
}
Returned Data
|
Name |
Description |
|
result |
Success of execution |
|
time |
Information about the execution time of the request |
Error Handling
HTTP status: 400
{
"error": "ERROR_CORE",
"error_description": "access_denied"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Error Message |
Description |
|
|
access_denied |
Invalid user |
|
|
access_denied |
User does not have permission to call the method |
|
|
Invalid user |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Invite User user.add
- Get a List of Users by Filter user.get
- Get Information About the Current User user.current
- Get a List of Users with Search by Personal Data user.search
- Get User Fields user.fields