Move Participants to the humanresources.node.member.move Department

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.move transfers users to the specified department or team.

Method Parameters

Required parameters are marked with *

Name
type

Description

nodeId*
integer

Identifier of the target department or team.

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

userIds*
array

Array of user identifiers to be transferred.

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

role
string

Role to be assigned to the transferred participants.

Possible values for department:

  • MEMBER_HEAD — department head
  • MEMBER_DEPUTY_HEAD — deputy head of the department
  • MEMBER_EMPLOYEE — department employee

Possible values for team:

  • MEMBER_TEAM_HEAD — team leader
  • MEMBER_TEAM_DEPUTY_HEAD — deputy team leader
  • MEMBER_TEAM_EMPLOYEE — team member

Default: MEMBER_EMPLOYEE for department and MEMBER_TEAM_EMPLOYEE for team.

Code Examples

How to Use Examples in Documentation

The new API call differs by adding 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":28,"userIds":[12,18],"role":"MEMBER_EMPLOYEE"}' \
        https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/humanresources.node.member.move
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"nodeId":28,"userIds":[12,18],"role":"MEMBER_EMPLOYEE","auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/api/humanresources.node.member.move
        

The SDK does not currently support calls to the /rest/api/ address. Use direct HTTP requests, such as via curl or fetch.

try
        {
            const response = await $b24.callMethod(
                'humanresources.node.member.move',
                {
                    nodeId: 28,
                    userIds: [12, 18],
                    role: 'MEMBER_EMPLOYEE'
                }
            );
        
            const result = response.getData().result;
            console.log('Member move result:', result.success);
        }
        catch (error)
        {
            console.error('Error:', error);
        }
        

The SDK does not currently support calls to the /rest/api/ address. Use direct HTTP requests, such as via curl or fetch.

try {
            $response = $b24Service
                ->core
                ->call(
                    'humanresources.node.member.move',
                    [
                        'nodeId' => 28,
                        'userIds' => [12, 18],
                        'role' => 'MEMBER_EMPLOYEE',
                    ]
                );
        
            $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 calls to the /rest/api/ address. Use direct HTTP requests, such as via curl or fetch.

BX24.callMethod(
            'humanresources.node.member.move',
            {
                nodeId: 28,
                userIds: [12, 18],
                role: 'MEMBER_EMPLOYEE'
            },
            function(result){
                console.info(result.data());
                console.log(result);
            }
        );
        

The SDK does not currently support calls to the /rest/api/ address. Use direct HTTP requests, such as via curl or fetch.

require_once('crest.php');
        
        $result = CRest::call(
            'humanresources.node.member.move',
            [
                'nodeId' => 28,
                'userIds' => [12, 18],
                'role' => 'MEMBER_EMPLOYEE',
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        

Response Handling

HTTP Status: 200

{
            "result": {
                "success": true
            },
            "time": {
                "start": 1780406100,
                "finish": 1780406100.215497,
                "duration": 0.21549701690673828,
                "processing": 0.1711289882659912,
                "date_start": "2026-06-02T16:15:00+02:00",
                "date_finish": "2026-06-02T16:15:00+02:00",
                "operating_reset_at": 1780406700,
                "operating": 0
            }
        }
        

Returned Data

Name
type

Description

result
object

Object containing the operation result.

success
boolean

Value true if users were successfully transferred.

time
time

Information about the request execution time.

Error Handling

HTTP Status: 400

{
            "error": {
                "code": "BITRIX_REST_V3_EXCEPTION_ENTITYNOTFOUNDEXCEPTION",
                "message": "Record with ID = `28` not found."
            }
        }
        

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 a non-empty array of user identifiers.

role

Invalid role #ROLE#. Allowed: #ROLE_LIST#.

Provide a role that is 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.

Ensure the user has permission to add participants to the target 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 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