Update status sale.status.update

Scope: sale

Who can execute the method: administrator

This method updates the status of an order or delivery.

Method Parameters

Required parameters are marked with *

Name `type`	Description
id* `sale_status.id`	Symbolic identifier of the status
fields* `object`	Field values for updating the status

Parameter fields

Required parameters are marked with *

Name `type`	Description
type* `string`	Status type: `O` — order status `D` — delivery status
notify `string`	Indicator of whether to send an email notification to the user when the order or delivery transitions to this status. Possible values: `Y` — notify `N` — do not notify
sort `integer`	Sorting
color `string`	HEX color code of the status (e.g., `#FF0000`)
xmlId `string`	External code of the status. Can be used for synchronization with the order or delivery status by identifier in an external system

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" \
        -H "Accept: application/json" \
        -d '{"id":"MS","fields":{"type":"D","notify":"N","sort":100,"color":"#00FF00","xmlId":"updatedXmlId"}}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/sale.status.update

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"id":"MS","fields":{"type":"D","notify":"N","sort":100,"color":"#00FF00","xmlId":"updatedXmlId"},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/sale.status.update

try
        {
        	const response = await $b24.callMethod(
        		'sale.status.update', {
        			id: 'MS',
        			fields: {
        				type: 'D',
        				notify: 'N',
        				sort: 100,
        				color: '#00FF00',
        				xmlId: 'updatedXmlId',
        			}
        		}
        	);
        	
        	const result = response.getData().result;
        	console.info(result);
        }
        catch( error )
        {
        	console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'sale.status.update',
                    [
                        'id' => 'MS',
                        'fields' => [
                            'type'   => 'D',
                            'notify' => 'N',
                            'sort'   => 100,
                            'color'  => '#00FF00',
                            'xmlId'  => 'updatedXmlId',
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            // Your required data processing logic
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error updating sale status: ' . $e->getMessage();
        }

BX24.callMethod(
            'sale.status.update', {
                id: 'MS',
                fields: {
                    type: 'D',
                    notify: 'N',
                    sort: 100,
                    color: '#00FF00',
                    xmlId: 'updatedXmlId',
                }
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error());
                } else {
                    console.info(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call('sale.status.update', [
            'id' => 'MS',
            'fields' => [
                'type' => 'D',
                'notify' => 'N',
                'sort' => 100,
                'color' => '#00FF00',
                'xmlId' => 'updatedXmlId',
            ]
        ]);
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP status: 200

{
            "result": {
                "status": {
                    "color": "#00FF00",
                    "id": "MS",
                    "notify": "N",
                    "sort": 100,
                    "type": "D",
                    "xmlId": "updatedXmlId"
                }
            },
            "time": {
                "start": 1712142575.655577,
                "finish": 1712142575.940234,
                "duration": 0.28465700149536133,
                "processing": 0.02240896224975586,
                "date_start": "2024-04-03T14:09:35+02:00",
                "date_finish": "2024-04-03T14:09:35+02:00"
            }
        }

Returned Data

Name `type`	Description
result `object`	Root element of the response
status `sale_status`	Object with information about the updated status
time `time`	Information about the execution time of the request

Error Handling

HTTP status: 400

{
            "error": 0,
            "error_description": "Required fields: type"
        }

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
`201340400001`	Status with the provided identifier not found
`200040300020`	Insufficient permissions to update the status
`201350000003`	Status type value not provided or the provided value is incorrect
`201350000006`	Error occurs when trying to change the type of certain system statuses: statuses `F` and `N` must always have type `O` (order) statuses `DF` and `DN` must always have type `D` (delivery)
`201350000007`	Error occurs when trying to change the order status type if orders are already attached to this status
`201350000008`	Error occurs when trying to change the delivery status type if deliveries are already attached to this status
`100`	Parameter `id` not specified
`100`	Parameter `fields` not specified or empty
`0`	Required fields of the `fields` structure not provided
`0`	Other errors (e.g., fatal errors)

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

Create Status

Get All Status Field Values by ID

Update status sale.status.update

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