Invite User user.add
Scope:
userWho can execute the method: administrator
The method user.add invites a user. This can only be done on behalf of a user with the rights to invite users, typically an administrator. Upon success, a standard invitation will be sent to the account. The result returns the identifier of the new user.
If you need to add an extranet user, you must pass the fields: EXTRANET: Y and SONET_GROUP_ID: [...]. If you need to add an intranet user, it is mandatory to pass: UF_DEPARTMENT: [...].
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
EMAIL* |
User's 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 address |
|
PERSONAL_CITY |
City of residence |
|
PERSONAL_STATE |
State/Region |
|
PERSONAL_ZIP |
Zip 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 '{
"EMAIL": "newuser1@example.com",
"UF_DEPARTMENT": [1]
}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/user.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"EMAIL": "newuser1@example.com",
"UF_DEPARTMENT": [1],
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/user.add
try
{
const response = await $b24.callMethod(
'user.add',
{
'EMAIL': 'newuser1@example.com',
'UF_DEPARTMENT': [1]
}
);
const result = response.getData().result;
console.dir(result);
}
catch( error )
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'user.add',
[
'EMAIL' => 'newuser1@example.com',
'UF_DEPARTMENT' => [1],
]
);
$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 adding user: ' . $e->getMessage();
}
BX24.callMethod(
"user.add",
{
"EMAIL": "newuser1@example.com",
"UF_DEPARTMENT": [1]
},
function(result)
{
if(result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'user.add',
[
'EMAIL' => 'newuser1@example.com',
'UF_DEPARTMENT' => [1]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result":12,
"time":{
"start":1721733827.713938,
"finish":1721733828.286292,
"duration":0.5723540782928467,
"processing":0.5508849620819092,
"date_start":"2024-07-23T11:23:47+00:00",
"date_finish":"2024-07-23T11:23:48+00:00",
"operating":0.5508630275726318
}
}
Returned Data
|
Name |
Description |
|
result |
Identifier of the new user |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "ERROR_ARGUMENT",
"error_description": "wrong_email",
"argument": ""
}
|
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 |
|
|
wrong_email |
The |
|
|
User with this email already exists |
Attempt to register a user with an email that is already taken |
|
|
access_denied |
The user does not have permission to call the method |
|
|
user_count_exceeded |
The number of users has been exceeded |
|
|
Group code not specified |
Group code not specified when adding a user to the extranet |
|
|
Group specified incorrectly |
Incorrect group specified when adding a user |
|
|
no_extranet_field |
The method call did not specify which group the user should belong to |
|
|
Error updating user fields |
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Update User Data user.update
- 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