Update the Composition of Participants in humanresources.node.member.set

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: humanresources

Who can execute the method: a user with the "Add Employees to Department" or "Add Participants to Team" access permission.

The method humanresources.node.member.set updates the composition of participants in a department or team by roles.

Method Parameters

Required parameters are marked with *

Name
type

Description

nodeId*
integer

Identifier of the department or team.

The identifier can be obtained using the humanresources.node.list method.

userIds*
object

An object containing lists of user identifiers in the format {"User_Role": [User_Identifier]}. Description of the object structure

The method adds new participants, updates roles of existing ones, and removes users from the department who are not present in the input userIds object.

User identifiers can be obtained using the user.get method.

Parameter userIds

Name `type`	Description
MEMBER_HEAD `array`	Identifiers of department heads.
MEMBER_DEPUTY_HEAD `array`	Identifiers of deputy department heads.
MEMBER_EMPLOYEE `array`	Identifiers of department employees.
MEMBER_TEAM_HEAD `array`	Identifiers of team leaders.
MEMBER_TEAM_DEPUTY_HEAD `array`	Identifiers of deputy team leaders.
MEMBER_TEAM_EMPLOYEE `array`	Identifiers of team participants.

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.set

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"nodeId":15,"userIds":{"MEMBER_HEAD":[7],"MEMBER_DEPUTY_HEAD":[12],"MEMBER_EMPLOYEE":[18,25,31]}}' \
        https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/humanresources.node.member.set

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"nodeId":15,"userIds":{"MEMBER_HEAD":[7],"MEMBER_DEPUTY_HEAD":[12],"MEMBER_EMPLOYEE":[18,25,31]},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/api/humanresources.node.member.set

The SDK does not yet support calls to the /rest/api/ address. Use direct HTTP requests, for example, via curl or fetch.

try
        {
            const response = await $b24.callMethod(
                'humanresources.node.member.set',
                {
                    nodeId: 15,
                    userIds: {
                        MEMBER_HEAD: [7],
                        MEMBER_DEPUTY_HEAD: [12],
                        MEMBER_EMPLOYEE: [18, 25, 31]
                    }
                }
            );
        
            const result = response.getData().result;
            console.log('Member set result:', result.success);
        }
        catch (error)
        {
            console.error('Error:', error);
        }

The SDK does not yet support calls to the /rest/api/ address. Use direct HTTP requests, for example, via curl or fetch.

try {
            $response = $b24Service
                ->core
                ->call(
                    'humanresources.node.member.set',
                    [
                        'nodeId' => 15,
                        'userIds' => [
                            'MEMBER_HEAD' => [7],
                            'MEMBER_DEPUTY_HEAD' => [12],
                            'MEMBER_EMPLOYEE' => [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 yet support calls to the /rest/api/ address. Use direct HTTP requests, for example, via curl or fetch.

BX24.callMethod(
            'humanresources.node.member.set',
            {
                nodeId: 15,
                userIds: {
                    MEMBER_HEAD: [7],
                    MEMBER_DEPUTY_HEAD: [12],
                    MEMBER_EMPLOYEE: [18, 25, 31]
                }
            },
            function(result){
                console.info(result.data());
                console.log(result);
            }
        );

The SDK does not yet support calls to the /rest/api/ address. Use direct HTTP requests, for example, via curl or fetch.

require_once('crest.php');
        
        $result = CRest::call(
            'humanresources.node.member.set',
            [
                'nodeId' => 15,
                'userIds' => [
                    'MEMBER_HEAD' => [7],
                    'MEMBER_DEPUTY_HEAD' => [12],
                    'MEMBER_EMPLOYEE' => [18, 25, 31]
                ]
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP Status: 200

{
            "result": {
                "success": true
            },
            "time": {
                "start": 1780405900,
                "finish": 1780405900.242662,
                "duration": 0.2426619529724121,
                "processing": 0.19870305061340332,
                "date_start": "2026-06-02T16:11:40+02:00",
                "date_finish": "2026-06-02T16:11:40+02:00",
                "operating_reset_at": 1780406500,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `object`	Object containing the result of the operation.
success `boolean`	Value `true` if the composition of participants was successfully updated.
time `time`	Information about the execution time of the request.

Error Handling

HTTP Status: 400

{
            "error": {
                "code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION",
                "message": "Error during request object validation",
                "validation": [
                    {
                        "message": "Invalid roles: MEMBER_OWNER. Allowed: MEMBER_HEAD, MEMBER_DEPUTY_HEAD, MEMBER_EMPLOYEE.",
                        "field": "userIds"
                    }
                ]
            }
        }

Name `type`	Description
error.code `string`	String error code. Use it to identify the type of exception
error.message `string`	Text description of the error
error.validation `array`	Array with error details. Present only in data validation errors `BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION`
error.validation[].field `string`	Name of the field where the validation error occurred
error.validation[].message `string`	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
`nodeId`	Parameter `"nodeId"` is required.	Provide the identifier of the department or team.
`userIds`	Parameter `"userIds"` is required and must be a non-empty array.	Provide an object with non-empty user lists by roles.
`userIds`	Invalid roles: `#ROLE#`. Allowed: `#ROLE_LIST#`.	Provide only roles that are supported for the selected type of department or team.

Access Errors

Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION

Field	Error Description	How to Fix
`-`	Access denied.	Check that the user has permission to modify the composition of participants in this department or team.

Error Code: BITRIX_REST_V3_EXCEPTION_INSUFFICIENTSCOPEEXCEPTION

Field	Error Description	How to Fix
`-`	Insufficient permissions: required scope is missing.	Check the `humanresources` scope.

Data Not Found Errors

Error Code: BITRIX_REST_V3_EXCEPTION_ENTITYNOTFOUNDEXCEPTION

Field	Error Description	How to Fix
`nodeId`	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 Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`405`	`ERROR_BATCH_METHOD_NOT_ALLOWED` Method is not allowed for batch usage	The current method is not permitted for calls using batch
`400`	`ERROR_BATCH_LENGTH_EXCEEDED` Max batch length exceeded	The maximum length of parameters passed to the batch method has been exceeded
`401`	`NO_AUTH_FOUND` Wrong authorization data	Invalid access token or webhook code
`400`	`INVALID_REQUEST` Https required	The HTTPS protocol is required for method calls
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is only available on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user associated with the access token or webhook used to call the method lacks the necessary permissions
`404`	`ERROR_MANIFEST_IS_NOT_AVAILABLE` Manifest is not available	The manifest is not available
`403`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires higher privileges than those provided by the webhook token
`401`	`expired_token` The access token provided has expired	The provided access token has expired
`403`	`user_access_error` The user does not have access to the application	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
`500`	`PORTAL_DELETED` Portal was deleted	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

Move Participants

Update the Composition of Participants in humanresources.node.member.set

Method ParametersMethod Parameters

Parameter userIdsParameter userIds

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Request Validation ErrorsRequest Validation Errors

Access ErrorsAccess Errors

Data Not Found ErrorsData Not Found Errors

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning

Method Parameters

Parameter userIds

Code Examples

Response Handling

Returned Data

Error Handling

Possible Error Codes

Request Validation Errors

Access Errors

Data Not Found Errors

Statuses and System Error Codes

Continue Learning