Update Lead crm.lead.update

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: crm

Who can execute the method: a user with permissions to edit CRM leads

DEPRECATED

The development of this method has been halted. Please use crm.item.update.

The method crm.lead.update updates an existing lead.

Method Parameters

Warning

It is strongly recommended to pass the complete set of address fields when updating an address. The specifics of updating address fields are described here.

Required parameters are marked with *

Name
type

Description

id*
integer

The identifier of the lead.

The identifier can be obtained using the methods crm.lead.list or crm.lead.add

fields
object

An object in the following format:

{
            field_1: value_1,
            field_2: value_2,
            ...,
            field_n: value_n,
        }
        

where:

  • field_n — the name of the field
  • value_n — the new value of the field

The list of available fields is described below.

An incorrect field in fields will be ignored.

Only the fields that need to be changed should be passed in fields

params
object

An optional set of options. ("paramName"=>"value"[, ...]). The list of possible fields is described below

Parameter fields

Name
type

Description

ADDRESS
string

The lead's address

ADDRESS_2
string

Second line of the address. In some countries, it is customary to split the address into 2 parts

ADDRESS_CITY
string

City

ADDRESS_COUNTRY
string

Country

ADDRESS_COUNTRY_CODE
string

Country code

ADDRESS_POSTAL_CODE
string

Postal code

ADDRESS_PROVINCE
string

Region

ADDRESS_REGION
string

District

ASSIGNED_BY_ID
user

Responsible person

BIRTHDATE
date

Date of birth

COMMENTS
string

Comments

COMPANY_ID
crm_company

Link the lead to a company

COMPANY_TITLE
string

The name of the company specified in the corresponding field of the lead. To link an existing company, pass its id in the COMPANY_ID field

CONTACT_ID
crm_contact

Link the lead to a contact

CONTACT_IDS
crm_contact

A list of contacts linked to the lead.

Contacts can be added or removed using the group of methods crm.lead.contact.*

CURRENCY_ID
crm_currency

Currency identifier

EMAIL
crm_multifield

Email address. Multiple

HONORIFIC
crm_status

Salutation

IM
crm_multifield

Messenger. Multiple

LINK
crm_multifield

User ID linked through Open Channels. Multiple

LAST_NAME
string

Last name

NAME
string

First name

SECOND_NAME
string

Middle name

OPENED
char

Indicates whether the lead is available to everyone. Acceptable values are Y or N

OPPORTUNITY
double

Amount

IS_MANUAL_OPPORTUNITY
char

Indicates manual mode for calculating the amount. Acceptable values are Y or N

ORIGINATOR_ID
string

Identifier of the data source. Used only for linking to an external source

ORIGIN_ID
string

Identifier of the item in the data source. Used only for linking to an external source

PHONE
crm_multifield

Phone number. Multiple

POST
string

Position

SOURCE_DESCRIPTION
string

Description of the source

SOURCE_ID
crm_status

Identifier of the source.
Default values:

SOURCE_ID

Name

CALL

Call

EMAIL

E-mail

WEB

Website

ADVERTISING

Advertising

PARTNER

Existing client

RECOMMENDATION

By recommendation

TRADE_SHOW

Trade show

WEBFORM

CRM form

CALLBACK

Callback

RC_GENERATOR

Sales generator

STORE

Online store

OTHER

Other

The list of all possible identifiers from the directory can be obtained using the method crm.status.list with the filter filter[ENTITY_ID]=SOURCE

STATUS_DESCRIPTION
string

Additional information about the stage

STATUS_ID
crm_status

Identifier of the lead stage. Default stages:

STATUS_ID

Name

NEW

New

IN_PROCESS

In process

PROCESSED

Processed

JUNK

Junk lead

CONVERTED

Qualified lead

The list of all possible stages from the directory can be obtained using the method crm.status.list with the filter filter[ENTITY_ID]=STATUS

TITLE
string

Title of the lead

UTM_CAMPAIGN
string

Identifier of the advertising campaign

UTM_CONTENT
string

Content of the campaign. For example, for contextual ads

UTM_MEDIUM
string

Type of traffic. CPC (ads), CPM (banners)

UTM_SOURCE
string

Advertising system. Google-Adwords and others

UTM_TERM
string

Search condition of the campaign. For example, keywords for contextual advertising

WEB
crm_multifield

Website. Multiple

UF_...

Custom fields. For example, UF_CRM_25534736.

Depending on the portal settings, leads may have a set of custom fields of specific types.

To change file fields, it is recommended to use the method crm.item.update.

To create, modify, or delete custom fields in leads, use the methods crm.lead.userfield.*

Note

Additionally, to find out the required format of the fields, you can execute the method crm.lead.fields and check the format of the incoming values for these fields.

Note

When modifying a lead, you cannot explicitly set the repeat lead indicator (the IS_RETURN_CUSTOMER field); however, this field automatically takes the value Y if you specify a value for COMPANY_ID or CONTACT_ID when modifying the lead.

Parameter params

Name
type

Description

REGISTER_SONET_EVENT
char

Register an event for adding the lead in the activity stream. A notification will also be sent to the person responsible for the lead. Acceptable values are Y or N

Required parameters are marked with *

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"id":1608,"fields":{"TITLE":"IP Titov","NAME":"Gleb","SECOND_NAME":"Yegorovich","LAST_NAME":"Titov","STATUS_ID":"NEW","OPENED":"Y","ASSIGNED_BY_ID":1,"CURRENCY_ID":"USD","OPPORTUNITY":12500,"PHONE":[{"VALUE":"555888","VALUE_TYPE":"WORK"}],"WEB":[{"VALUE":"www.mysite.com","VALUE_TYPE":"WORK"}]},"params":{"REGISTER_SONET_EVENT":"Y"}}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.lead.update
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"id":1608,"fields":{"TITLE":"IP Titov","NAME":"Gleb","SECOND_NAME":"Yegorovich","LAST_NAME":"Titov","STATUS_ID":"NEW","OPENED":"Y","ASSIGNED_BY_ID":1,"CURRENCY_ID":"USD","OPPORTUNITY":12500,"PHONE":[{"VALUE":"555888","VALUE_TYPE":"WORK"}],"WEB":[{"VALUE":"www.mysite.com","VALUE_TYPE":"WORK"}]},"params":{"REGISTER_SONET_EVENT":"Y"},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/crm.lead.update
        
try
        {
        	const response = await $b24.callMethod(
        		"crm.lead.update",
        		{
        			id: 1608,
        			fields:
        			{
        				TITLE: "IP Titov",
        				NAME: "Gleb",
        				SECOND_NAME: "Yegorovich",
        				LAST_NAME: "Titov",
        				STATUS_ID: "NEW",
        				OPENED: "Y",
        				ASSIGNED_BY_ID: 1,
        				CURRENCY_ID: "USD",
        				OPPORTUNITY: 12500,
        				PHONE: [
        					{
        						VALUE: "555888",
        						VALUE_TYPE: "WORK",
        					},
        				],
        				WEB: [
        					{
        						VALUE: "www.mysite.com",
        						VALUE_TYPE: "WORK",
        					}
        				],
        			},
        			params: {
        				REGISTER_SONET_EVENT: "Y",
        			}
        		}
        	);
        	
        	const result = response.getData().result;
        	console.info(result);
        }
        catch( error )
        {
        	console.error(error);
        }
        
try {
            $id = 123; // Example lead ID
            $fields = [
                'TITLE' => 'Updated Lead Title',
                'NAME' => 'John',
                'LAST_NAME' => 'Doe',
                'BIRTHDATE' => (new DateTime('1980-01-01'))->format(DateTime::ATOM),
                'COMPANY_TITLE' => 'Example Company',
                'STATUS_ID' => 'NEW',
                'COMMENTS' => 'Updated comments for the lead.',
                'PHONE' => '1234567890',
                'EMAIL' => 'john.doe@example.com',
            ];
            $params = [
                'REGISTER_SONET_EVENT' => 'Y',
            ];
            $result = $serviceBuilder->getCRMScope()->lead()->update($id, $fields, $params);
            if ($result->isSuccess()) {
                print($result->getCoreResponse()->getResponseData()->getResult()[0]);
            } else {
                print("Update failed.");
            }
        } catch (Throwable $e) {
            print("Error: " . $e->getMessage());
        }
        
BX24.callMethod(
            "crm.lead.update",
            {
                id: 1608,
                fields:
                {
                    TITLE: "IP Titov",
                    NAME: "Gleb",
                    SECOND_NAME: "Yegorovich",
                    LAST_NAME: "Titov",
                    STATUS_ID: "NEW",
                    OPENED: "Y",
                    ASSIGNED_BY_ID: 1,
                    CURRENCY_ID: "USD",
                    OPPORTUNITY: 12500,
                    PHONE: [
                        {
                            VALUE: "555888",
                            VALUE_TYPE: "WORK",
                        },
                    ],
                    WEB: [
                        {
                            VALUE: "www.mysite.com",
                            VALUE_TYPE: "WORK",
                        }
                    ],
                },
                params: {
                    REGISTER_SONET_EVENT: "Y",
                }
            },
            (result) => {
                if (result.error())
                {
                    console.error(result.error());return;
                }
        
                console.info(result.data());
            }
        );
        
$fields = [
            'TITLE' => $sTitle,
            'COMPANY_ID' => 123,
            'PHONE' => [
                [
                    'VALUE' => '555888',
                    'VALUE_TYPE' => 'WORK',
                ],
            ],
        ];
        
        $result = CRest::call(
            'crm.lead.update',
            [
                'id' => 1608,
                'fields' => $fields,
            ],
            [
                'REGISTER_SONET_EVENT' => 'Y',
            ]     
        );
        

Response Handling

HTTP Status: 200

{
            "result": true,
            "time": {
                "start": 1705764932.998683,
                "finish": 1705764937.173995,
                "duration": 4.1753120422363281,
                "processing": 3.3076529502868652,
                "date_start": "2024-01-20T18:35:32+01:00",
                "date_finish": "2024-01-20T18:35:37+01:00",
                "operating_reset_at": 1705765533,
                "operating": 3.3076241016387939
            }
        }
        

Returned Data

Name
type

Description

result
boolean

The root element of the response, contains true in case of success

time
time

Information about the execution time of the request

Error Handling

HTTP Status: 40x, 50x Error

{
            "error": "",
            "error_description": "ID is not defined or invalid."
        }
        

Possible Errors

Error Text

Description

ID is not defined or invalid

The parameter id contains a non-integer number less than or equal to zero

Not found

A lead with the provided id does not exist

Access denied

The user does not have permission to edit the lead

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 permitted for calls 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 HTTPS protocol is required for method calls

503

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it

403

ACCESS_DENIED
REST API is available only on commercial plans

The REST API is only available on commercial plans

403

INVALID_CREDENTIALS
Invalid request credentials

The user associated with the access token or webhook used to call the method lacks the necessary 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 portal administrator has restricted access to this application to specific users only

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 "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