curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"id":1366,"newName":"Bitrix REST API","auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/disk.storage.rename

try
        {
            const response = await $b24.callMethod(
                'disk.storage.rename',
                {
                    id: 1366,
                    newName: 'Bitrix REST API'
                }
            );
            
            const result = response.getData().result;
            console.log('Renamed storage:', result);
            
            processResult(result);
        }
        catch( error )
        {
            console.error('Error:', error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'disk.storage.rename',
                    [
                        'id' => 1366,
                        'newName' => 'Bitrix REST API'
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error renaming storage: ' . $e->getMessage();
        }

BX24.callMethod(
            "disk.storage.rename",
            {
                id: 1366,
                newName: 'Bitrix REST API'
            },
            function (result)
            {
                if (result.error())
                    console.error(result.error());
                else
                    console.dir(result.data());
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'disk.storage.rename',
            [
                'id' => 1366,
                'newName' => 'Bitrix REST API'
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP Status: 200

{
            "result": {
                "ID": "1366",
                "NAME": "Bitrix REST API",
                "CODE": null,
                "MODULE_ID": "disk",
                "ENTITY_TYPE": "restapp",
                "ENTITY_ID": "3",
                "ROOT_OBJECT_ID": "8910"
            },
            "time": {
                "start": 1770048169,
                "finish": 1770048169.935598,
                "duration": 0.9355978965759277,
                "processing": 0,
                "date_start": "2026-02-02T14:02:49+01:00",
                "date_finish": "2026-02-02T14:02:49+01:00",
                "operating_reset_at": 1770048769,
                "operating": 0.11735081672668457
            }
        }

Returned Data

Name `type`	Description
result `array`	Array with the description of the storage fields
ID `integer`	Identifier of the storage
NAME `string`	Name of the storage
CODE `string`	Symbolic code of the storage
MODULE_ID `string`	Identifier of the module to which the storage belongs
ENTITY_TYPE `string`	Type of the object associated with the storage
ENTITY_ID `string`	Identifier of the object associated with the storage
ROOT_OBJECT_ID `integer`	Identifier of the root folder of the storage
time `time`	Information about the execution time of the request

Error Handling

HTTP Status: 400

{
            "error":"ERROR_NOT_FOUND",
            "error_description":"Could not find entity with id `X`"
        }

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	Value
`ERROR_NOT_FOUND`	Could not find entity with id `X`	Storage with the specified `id` not found
—	Access denied (invalid type of storage)	Storage not associated with the application
`ACCESS_DENIED`	Access denied	Insufficient permissions to rename the storage

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

Get Storage Description

Upload File to Storage

Rename Application Storage disk.storage.rename

Method ParametersMethod Parameters

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

Method Parameters

Code Examples

Response Handling

Returned Data

Error Handling

Possible Error Codes

Statuses and System Error Codes

Continue Learning