Get Child Departments humanresources.node.children
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 "View Departments" or "View Teams" access permission
The method humanresources.node.children returns the direct child departments and teams of the selected structure element.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the parent department or team. The identifier can be obtained using the humanresources.node.list method. |
|
select |
List of fields of the department or team to return. Available fields:
|
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.children
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":1,"select":["id","name","type","structureId","parentId","description","accessCode","userCount","colorName","xmlId","createdAt","updatedAt"]}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/humanresources.node.children
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":1,"select":["id","name","type","structureId","parentId","description","accessCode","userCount","colorName","xmlId","createdAt","updatedAt"],"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/humanresources.node.children
The SDK does not yet 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.children',
{
id: 1,
select: [
'id',
'name',
'type',
'structureId',
'parentId',
'description',
'accessCode',
'userCount',
'colorName',
'xmlId',
'createdAt',
'updatedAt'
]
}
);
const result = response.getData().result.items;
console.info(result.length);
}
catch (error)
{
console.error(error);
}
The SDK does not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'humanresources.node.children',
[
'id' => 1,
'select' => [
'id',
'name',
'type',
'structureId',
'parentId',
'description',
'accessCode',
'userCount',
'colorName',
'xmlId',
'createdAt',
'updatedAt'
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting children: ' . $e->getMessage();
}
The SDK does not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'humanresources.node.children',
{
id: 1,
select: [
'id',
'name',
'type',
'structureId',
'parentId',
'description',
'accessCode',
'userCount',
'colorName',
'xmlId',
'createdAt',
'updatedAt'
]
},
function(result){
console.info(result.data());
console.log(result);
}
);
The SDK does not yet 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.children',
[
'id' => 1,
'select' => [
'id',
'name',
'type',
'structureId',
'parentId',
'description',
'accessCode',
'userCount',
'colorName',
'xmlId',
'createdAt',
'updatedAt'
]
}
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"items": [
{
"id": 12,
"name": "B2B Sales",
"type": "DEPARTMENT",
"structureId": 1,
"parentId": 1,
"description": "Working with corporate clients",
"accessCode": "DR12",
"userCount": 9,
"colorName": null,
"xmlId": null,
"createdAt": "2026-05-20T10:15:00+02:00",
"updatedAt": "2026-06-01T16:30:00+02:00"
},
{
"id": 18,
"name": "Marketing",
"type": "DEPARTMENT",
"structureId": 1,
"parentId": 1,
"description": "Promotion of products and brand",
"accessCode": "DR18",
"userCount": 6,
"colorName": null,
"xmlId": null,
"createdAt": "2026-05-22T11:40:00+02:00",
"updatedAt": "2026-06-03T10:05:00+02:00"
}
]
},
"time": {
"start": 1780396400,
"finish": 1780396400.428761,
"duration": 0.42876100540161133,
"processing": 0.3972141742706299,
"date_start": "2026-06-02T13:33:20+02:00",
"date_finish": "2026-06-02T13:33:20+02:00",
"operating_reset_at": 1780397000,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object containing the response data |
|
items |
Array of child departments and teams. The composition of the element fields depends on |
|
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": "Required field `id` is not specified",
"field": "id"
}
]
}
}
|
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 |
|
|
Required field |
Add |
|
|
Field |
Ensure that the value of |
|
|
Unsupported field name provided for selection |
Use only values from the description of the |
Access Errors
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Access denied |
The user does not have permission to view the specified 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 |
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
- Get humanresources.node.get
- Create Department humanresources.node.add
- Get a List of Departments humanresources.node.list
- Departments and Teams: Overview of Methods