Create node

POST /v1/humanresources/nodes

Creates a node in the org structure of a Bitrix24 account: a department or a team in the department tree. The node type is set by the type field; fields are passed flat at the JSON root without a fields wrapper.

Request fields (body)

Fields filled in by the system (id, structureId, accessCode, userCount, xmlId, createdAt, updatedAt) must not be passed in the body: a request with any of them is rejected with the READONLY_FIELD error. These fields are returned in the response.

Examples

curl — personal key

curl -X POST "https://vibecode.bitrix24.com/v1/humanresources/nodes" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "DEPARTMENT",
    "name": "Sales department",
    "parentId": 1,
    "description": "Active sales managers",
    "colorName": "blue"
  }'

curl — OAuth application

curl -X POST "https://vibecode.bitrix24.com/v1/humanresources/nodes" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "DEPARTMENT",
    "name": "Sales department",
    "parentId": 1,
    "description": "Active sales managers",
    "colorName": "blue"
  }'

JavaScript — personal key

const res = await fetch('https://vibecode.bitrix24.com/v1/humanresources/nodes', {
  method: 'POST',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    type: 'DEPARTMENT',
    name: 'Sales department',
    parentId: 1,
    description: 'Active sales managers',
    colorName: 'blue',
  }),
})

const { success, data } = await res.json()
console.log('Node ID:', data.id)

JavaScript — OAuth application

const res = await fetch('https://vibecode.bitrix24.com/v1/humanresources/nodes', {
  method: 'POST',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    type: 'DEPARTMENT',
    name: 'Sales department',
    parentId: 1,
    description: 'Active sales managers',
    colorName: 'blue',
  }),
})

const { success, data } = await res.json()

Response fields

Returns the full record of the created node.

Response example

{
  "success": true,
  "data": {
    "id": 39,
    "name": "Sales department",
    "type": "DEPARTMENT",
    "structureId": 1,
    "parentId": 1,
    "description": "Active sales managers",
    "accessCode": "SN39",
    "userCount": 0,
    "colorName": "blue",
    "xmlId": null,
    "createdAt": "2026-06-03T13:06:45.000Z",
    "updatedAt": "2026-06-03T13:06:45.000Z",
    "members": []
  }
}

Error response example

400 — required field name not provided:

{
  "success": false,
  "error": {
    "code": "INVALID_PARAMS",
    "message": "Request object validation failed",
    "validation": [
      {
        "field": "MISSING_NAME",
        "message": "Parameter \"name\" is required."
      }
    ]
  }
}

Errors

The full list of common API errors — Errors.

Known specifics

Initial node setup in a single request. Besides the base fields, you can set the member roster by role (userIds) and communication tools right at creation: create a chat, channel or collab (createChat / createChannel / createCollab) or bind existing ones by identifiers (bindingChatIds / bindingChannelIds / bindingCollabIds). These fields are optional — without them an empty node is created.

Batch creation

POST /v1/humanresources/nodes/batch accepts action: "create" and an items array containing the node fields described above. For example: {"action":"create","items":[{"type":"DEPARTMENT","name":"Sales","parentId":1},{"type":"DEPARTMENT","name":"Support","parentId":1}]}.

The response is HTTP 200 with data.results and data.summary. A successful item contains index (its zero-based position in the original array), success: true and id. A failed item contains the same index, success: false, error and message. summary contains total, succeeded and failed; check each item even with HTTP 200. One failed item does not undo the successful writes of the other items. Each item requires a separate Bitrix24 call. Items are created sequentially to avoid conflicting changes to the shared structure.

Timeouts and other errors with an uncertain outcome also contain details.outcome: "unknown" and details.retryable: false, preserving their own error code. The node may already exist in the Bitrix24 account: check the node list before trying again. Do not automatically retry such an item.

See also

• List nodes
• Get node
• Update node
• Search nodes
• Org structure nodes