Remove Participants from the Department humanresources.node.member.remove
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:
humanresourcesWho can execute the method: a user with the "Remove employees from the department" or "Remove participants from the team" access permission.
The method humanresources.node.member.remove removes users from the specified department or team.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
nodeId* |
Identifier of the department or team. The identifier can be obtained using the humanresources.node.list method. |
|
userIds* |
Array of user identifiers to be removed. User identifiers can be obtained using the user.get method. |
Code Examples
How to Use Examples in Documentation
The new API call differs by the addition of the /api/ parameter in the request:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/humanresources.node.member.move
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"nodeId":15,"userIds":[18,25,31]}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/humanresources.node.member.remove
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"nodeId":15,"userIds":[18,25,31],"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/humanresources.node.member.remove
The SDK does not currently support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
try
{
const response = await $b24.callMethod(
'humanresources.node.member.remove',
{
nodeId: 15,
userIds: [18, 25, 31]
}
);
const result = response.getData().result;
console.log('Removed:', result.removed);
console.log('Failed:', result.failed);
}
catch (error)
{
console.error('Error:', error);
}
The SDK does not currently support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'humanresources.node.member.remove',
[
'nodeId' => 15,
'userIds' => [18, 25, 31],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error: ' . $e->getMessage();
}
The SDK does not currently support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'humanresources.node.member.remove',
{
nodeId: 15,
userIds: [18, 25, 31]
},
function(result){
console.info(result.data());
console.log(result);
}
);
The SDK does not currently support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
require_once('crest.php');
$result = CRest::call(
'humanresources.node.member.remove',
[
'nodeId' => 15,
'userIds' => [18, 25, 31],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"removed": [
18,
25
],
"failed": [
{
"userId": 31,
"reason": "Not found in this node"
}
]
},
"time": {
"start": 1780406400,
"finish": 1780406400.207548,
"duration": 0.2075481414794922,
"processing": 0.16550898551940918,
"date_start": "2026-06-02T16:20:00+02:00",
"date_finish": "2026-06-02T16:20:00+02:00",
"operating_reset_at": 1780407000,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object containing the operation result |
|
removed |
Array of user identifiers that were successfully removed |
|
failed |
Array of users that could not be removed |
|
failed[] |
Object describing the removal error |
|
userId |
Identifier of the user that could not be removed |
|
reason |
Reason why the user was not removed |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION",
"message": "Error validating the request object",
"validation": [
{
"message": "Parameter \"userIds\" is required and must be a non-empty array.",
"field": "userIds"
}
]
}
}
|
Name |
Description |
|
error.code |
String error code. Use it to identify the type of exception |
|
error.message |
Text description of the error |
|
error.validation |
Array with error details. Present only in data validation errors |
|
error.validation[].field |
Name of the field where the validation error occurred |
|
error.validation[].message |
Description of the error related to the specified field |
Possible Error Codes
Request Validation Errors
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Parameter |
Provide the identifier of the department or team. |
|
|
Parameter |
Provide a non-empty array of user identifiers. |
Access Errors
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Access denied |
Ensure the user has permission to remove participants from this department or team. |
Error Code: BITRIX_REST_V3_EXCEPTION_INSUFFICIENTSCOPEEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Insufficient access rights: required scope is missing |
Check the |
Data Not Found Errors
Error Code: BITRIX_REST_V3_EXCEPTION_ENTITYNOTFOUNDEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Record with the specified identifier not found |
Provide the identifier of an existing department or team. |
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
- Add Participants to humanresources.node.member.add
- Move Participants to the humanresources.node.member.move Department
- Participants of Departments and Teams: Overview of Methods