Create a Folder in the Root of the Storage disk.storage.addfolder
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:
diskWho can execute the method: user with "Add" access permission for the required storage
The method disk.storage.addfolder creates a folder in the root of the storage.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the storage. The identifier can be obtained using the method disk.storage.getlist |
|
data* |
Array with the field |
|
rights |
Array of access permissions for the folder in the format
User categories:
The list of available |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":1357,"data":{"NAME":"New Folder"},"rights":[{"TASK_ID":71,"ACCESS_CODE":"U1271"}]}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/disk.storage.addfolder
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":1357,"data":{"NAME":"New Folder"},"rights":[{"TASK_ID":71,"ACCESS_CODE":"U1271"}],"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/disk.storage.addfolder
try
{
const response = await $b24.callMethod(
'disk.storage.addfolder',
{
id: 1357,
data: {
NAME: 'New Folder',
},
rights: [
{
TASK_ID: 71,
ACCESS_CODE: 'U1271'
}
]
}
);
const result = response.getData().result;
console.log('Created folder with ID:', result);
processResult(result);
}
catch( error )
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'disk.storage.addfolder',
[
'id' => 1357,
'data' => [
'NAME' => 'New Folder'
],
'rights' => [
[
'TASK_ID' => 71,
'ACCESS_CODE' => 'U1271'
]
]
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error adding folder: ' . $e->getMessage();
}
BX24.callMethod(
"disk.storage.addfolder",
{
id: 1357,
data: {
NAME: 'New Folder'
},
rights: [
{
TASK_ID: 71,
ACCESS_CODE: 'U1271'
}
]
},
function (result)
{
if (result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'disk.storage.addfolder',
[
'id' => 1357,
'data' => [
'NAME' => 'New Folder'
],
'rights' => [
[
'TASK_ID' => 71,
'ACCESS_CODE' => 'U1271'
]
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": {
"ID": 9031,
"NAME": "New Folder",
"CODE": null,
"STORAGE_ID": "1357",
"TYPE": "folder",
"REAL_OBJECT_ID": 9031,
"PARENT_ID": "8875",
"DELETED_TYPE": 0,
"CREATE_TIME": "2026-01-28T17:23:11+02:00",
"UPDATE_TIME": "2026-01-28T17:23:11+02:00",
"DELETE_TIME": null,
"CREATED_BY": "1269",
"UPDATED_BY": "1269",
"DELETED_BY": null,
"DETAIL_URL": "https://test.bitrix24.com/company/personal/user/1269/disk/path/New Folder"
},
"time": {
"start": 1769610191,
"finish": 1769610191.803601,
"duration": 0.8036010265350342,
"processing": 0,
"date_start": "2026-01-28T17:23:11+02:00",
"date_finish": "2026-01-28T17:23:11+02:00",
"operating_reset_at": 1769610791,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Array with data about the created folder |
|
ID |
Identifier of the folder |
|
NAME |
Name of the folder |
|
CODE |
Symbolic code of the folder |
|
STORAGE_ID |
Identifier of the storage where the folder is located |
|
TYPE |
Type of the object |
|
REAL_OBJECT_ID |
Identifier of the object |
|
PARENT_ID |
Identifier of the parent folder |
|
DELETED_TYPE |
Deletion status of the object. Possible values:
|
|
CREATE_TIME |
Date and time of folder creation |
|
UPDATE_TIME |
Date and time of the last update of the folder |
|
DELETE_TIME |
Date and time of moving the folder to the trash |
|
CREATED_BY |
Identifier of the user who created the folder |
|
UPDATED_BY |
Identifier of the user who made the last change |
|
DELETED_BY |
Identifier of the user who deleted the folder |
|
DETAIL_URL |
Link to open the folder in the interface |
|
time |
Information about the execution time of the request |
Error Handling
HTTP status: 400
{
"error":"ERROR_ARGUMENT",
"error_description":"Invalid value of parameter {Parameter #1}"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Description |
Value |
|
|
Invalid value of parameter |
Required field |
|
|
A folder with this name already exists |
A folder with this name already exists |
|
|
Could not find entity with id |
Storage with the specified |
|
|
Access denied |
Insufficient permissions to create the folder |
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 a list of files and folders in the root of the storage disk.storage.getchildren
- Get Description of Storage Fields disk.storage.getfields
- Get Application Storage Description disk.storage.getforapp
- Get a List of Available Storages disk.storage.getlist
- Get Storage Types disk.storage.gettypes
- Get Storage Description disk.storage.get
- Rename Application Storage disk.storage.rename
- Upload a New File to the Root of the Storage disk.storage.uploadfile