Get a List of Departments humanresources.node.list
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.list returns a list of departments or teams.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
type* |
Type of the structure element. Possible values:
|
|
select |
List of fields for the department or team to return. Available fields:
|
|
pagination |
Pagination parameters:
|
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.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"type":"DEPARTMENT","select":["id","name","type","structureId","parentId","description","accessCode","userCount","colorName","xmlId","createdAt","updatedAt"],"pagination":{"page":1,"limit":20,"offset":0}}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/humanresources.node.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"type":"DEPARTMENT","select":["id","name","type","structureId","parentId","description","accessCode","userCount","colorName","xmlId","createdAt","updatedAt"],"pagination":{"page":1,"limit":20,"offset":0},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/humanresources.node.list
The SDK does not yet support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
try
{
const response = await $b24.callMethod(
'humanresources.node.list',
{
type: 'DEPARTMENT',
select: [
'id',
'name',
'type',
'structureId',
'parentId',
'description',
'accessCode',
'userCount',
'colorName',
'xmlId',
'createdAt',
'updatedAt'
],
pagination: {
page: 1,
limit: 20,
offset: 0
}
}
);
const result = response.getData().result;
console.log('Node list:', result);
}
catch (error)
{
console.error('Error:', error);
}
The SDK does not yet support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'humanresources.node.list',
[
'type' => 'DEPARTMENT',
'select' => [
'id',
'name',
'type',
'structureId',
'parentId',
'description',
'accessCode',
'userCount',
'colorName',
'xmlId',
'createdAt',
'updatedAt'
],
'pagination' => [
'page' => 1,
'limit' => 20,
'offset' => 0
]
]
);
$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 address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'humanresources.node.list',
{
type: 'DEPARTMENT',
select: [
'id',
'name',
'type',
'structureId',
'parentId',
'description',
'accessCode',
'userCount',
'colorName',
'xmlId',
'createdAt',
'updatedAt'
],
pagination: {
page: 1,
limit: 20,
offset: 0
}
},
function(result){
console.info(result.data());
console.log(result);
}
);
The SDK does not yet support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
require_once('crest.php');
$result = CRest::call(
'humanresources.node.list',
[
'type' => 'DEPARTMENT',
'select' => [
'id',
'name',
'type',
'structureId',
'parentId',
'description',
'accessCode',
'userCount',
'colorName',
'xmlId',
'createdAt',
'updatedAt'
],
'pagination' => [
'page' => 1,
'limit' => 20,
'offset' => 0
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"items": [
{
"id": 1,
"name": "Sales Department",
"type": "DEPARTMENT",
"structureId": 1,
"parentId": null,
"description": "Main sales department",
"accessCode": "DR1",
"userCount": 18,
"colorName": null,
"xmlId": null,
"createdAt": "2026-05-20T10:15:00+02:00",
"updatedAt": "2026-06-02T10:30:00+02:00"
},
{
"id": 2,
"name": "Marketing Department",
"type": "DEPARTMENT",
"structureId": 1,
"parentId": 1,
"description": "Department responsible for promoting the company's products",
"accessCode": "DR2",
"userCount": 9,
"colorName": null,
"xmlId": "marketing_department",
"createdAt": "2026-05-22T09:00:00+02:00",
"updatedAt": "2026-06-02T11:45:00+02:00"
}
]
},
"time": {
"start": 1780403500,
"finish": 1780403500.248911,
"duration": 0.24891114234924316,
"processing": 0.21900415420532227,
"date_start": "2026-06-02T15:31:40+02:00",
"date_finish": "2026-06-02T15:31:40+02:00",
"operating_reset_at": 1780404100,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object containing the response data |
|
items |
Array of department or team objects. 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_INVALIDPAGINATIONEXCEPTION",
"message": "Cannot recognize pagination parameter `{\"limit\":\"abc\"}`"
}
}
|
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
Pagination Errors
Error Code: BITRIX_REST_V3_EXCEPTION_INVALIDPAGINATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Cannot recognize pagination parameter |
Provide numeric values. |
Request Validation Errors
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Required field |
Provide |
|
|
An invalid value for the structure element type was provided |
Use |
Errors in the select Parameter
Error Code: BITRIX_REST_V3_EXCEPTION_UNKNOWNDTOPROPERTYEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Unknown field |
Provide only fields from the |
Error Code: BITRIX_REST_V3_EXCEPTION_INVALIDSELECTEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Cannot recognize select expression |
Provide |
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 departments and teams |
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
- Find Departments humanresources.node.search
- Departments and Teams: Overview of Methods