Add Folder to Site landing.site.addFolder

Scope: landing

Who can execute the method: a user with "edit" access permission for the site

The method landing.site.addFolder creates a folder in the specified site and returns the identifier of the created folder.

Method Parameters

Required parameters are marked with *

Name
type

Description

siteId*
integer

The identifier of the site where the folder needs to be created.

The site identifier can be obtained using the landing.site.getList method or from the result of the landing.site.add method

fields*
object

A set of fields for the folder being created (detailed description)

Parameter fields

Required parameters are marked with *

Name `type`	Description
TITLE* `string`	The name of the folder, maximum length `255` characters
CODE `string`	Symbolic code for the folder in the URL, maximum length `255` characters. If not provided or empty, the code is generated from `TITLE` using transliteration. If the code is empty after transliteration, a random string of length `12` characters is created
PARENT_ID `integer`	The identifier of the parent folder. If the value is `0`, `null`, or empty, the folder is created at the root of the site
ACTIVE `string`	Folder activity flag `Y/N`, default is `N`

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "siteId": 1817,
            "fields": {
              "TITLE": "New Folder",
              "CODE": "new-folder",
              "ACTIVE": "Y",
              "PARENT_ID": 736
            }
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.site.addFolder.json"

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "siteId": 1817,
            "fields": {
              "TITLE": "New Folder",
              "CODE": "new-folder",
              "ACTIVE": "Y",
              "PARENT_ID": 736
            },
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.site.addFolder.json"

try
        {
        	const response = await $b24.callMethod(
        		'landing.site.addFolder',
        		{
        			siteId: 1817,
        			fields: {
        				TITLE: 'New Folder',
        				CODE: 'new-folder',
        				ACTIVE: 'Y',
        				PARENT_ID: 736
        			}
        		}
        	);
        
        	const result = response.getData().result;
        	console.info(result);
        }
        catch (error)
        {
        	console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.site.addFolder',
                    [
                        'siteId' => 1817,
                        'fields' => [
                            'TITLE' => 'New Folder',
                            'CODE' => 'new-folder',
                            'ACTIVE' => 'Y',
                            'PARENT_ID' => 736,
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error adding folder: ' . $e->getMessage();
        }

BX24.callMethod(
            'landing.site.addFolder',
            {
                siteId: 1817,
                fields: {
                    TITLE: 'New Folder',
                    CODE: 'new-folder',
                    ACTIVE: 'Y',
                    PARENT_ID: 736
                }
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'landing.site.addFolder',
            [
                'siteId' => 1817,
                'fields' => [
                    'TITLE' => 'New Folder',
                    'CODE' => 'new-folder',
                    'ACTIVE' => 'Y',
                    'PARENT_ID' => 736,
                ],
            ]
        );
        
        if (isset($result['error']))
        {
            echo 'Error: ' . $result['error_description'];
        }
        else
        {
            echo '<pre>';
            print_r($result['result']);
            echo '</pre>';
        }

Response Handling

HTTP Status: 200

{
            "result": 89,
            "time": {
                "start": 1773169396,
                "finish": 1773169396.875899,
                "duration": 0.875899076461792,
                "processing": 0,
                "date_start": "2026-03-10T22:03:16+01:00",
                "date_finish": "2026-03-10T22:03:16+01:00",
                "operating_reset_at": 1773169996,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `integer`	The identifier of the created folder
time `time`	Information about the execution time of the request

Error Handling

HTTP Status: 400

{
            "error": "ACCESS_DENIED",
            "error_description": "Site not found or access to it is denied."
        }

Name `type`	Description
error `string`	String error code. It may consist of digits, Latin letters, and underscores
error_description `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
`ACCESS_DENIED`	Site not found or access to it is denied
`BX_EMPTY_REQUIRED`	A required field is not filled, such as `TITLE` or `CODE`
`FOLDER_IS_NOT_UNIQUE`	A folder with this name already exists. This error occurs when there is a conflict with `CODE` within the site and the parent folder
`SLASH_IS_NOT_ALLOWED`	The character `/` is present in `fields.CODE`

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 allowed to be called 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 methods must be called using the HTTPS protocol
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is available only on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users
`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 option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning

Add Site

Delete Site

Add Folder to Site landing.site.addFolder

Method ParametersMethod Parameters

Parameter fieldsParameter fields

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning