Update Lead crm.lead.update

Scope: crm

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

Method Development Stopped

The method crm.lead.update continues to function, but there is a more relevant alternative crm.item.update.

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

Method Parameters

Warning

It is highly 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`	Lead identifier. The identifier can be obtained using the methods crm.lead.list or crm.lead.add
fields `object`	Object format: `{ field_1: value_1, field_2: value_2, ..., field_n: value_n, }` where: `field_n` — field name `value_n` — new field value The list of available fields is described below. An incorrect field in `fields` will be ignored. Only those fields that need to be changed should be passed in `fields`
params `object`	Optional set of options. (`"paramName"=>"value"[, ...]`). The list of possible fields is described below

Parameter fields

Name
type

Description

ADDRESS
string

Lead 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

State

ADDRESS_REGION
string

Region

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

Company name specified in the corresponding lead field. 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

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

E-mail address. Multiple

HONORIFIC
crm_status

Salutation

IM
crm_multifield

Messenger. Multiple

LINK
crm_multifield

User ID linked through an open channel. Multiple

LAST_NAME
string

Last name

NAME
string

First name

SECOND_NAME
string

Middle name

OPENED
char

Indicator of lead availability for everyone. Acceptable values Y or N

OPPORTUNITY
double

Amount

IS_MANUAL_OPPORTUNITY
char

Indicator of manual calculation mode for the amount. Acceptable values 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. Multiple

POST
string

Position

SOURCE_DESCRIPTION
string

Source description

SOURCE_ID
crm_status

Source identifier.
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	Converted 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

Lead title

UTM_CAMPAIGN
string

Advertising campaign designation

UTM_CONTENT
string

Campaign content. For example, for contextual ads

UTM_MEDIUM
string

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

UTM_SOURCE
string

Advertising system. Google Ads, Facebook Ads, and others

UTM_TERM
string

Search term for the campaign. For example, keywords for contextual advertising

WEB
crm_multifield

Website. Multiple

UF_...

Custom fields. For example, UF_CRM_25534736.

Depending on the account 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 fields, you can execute the method crm.lead.fields and check the format of the incoming values of these fields.

Note

When changing a lead, you cannot explicitly set the indicator for a repeat lead (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 changing the lead.

Parameter params

Name `type`	Description
REGISTER_SONET_EVENT `char`	Register an event for adding the lead in the activity stream. Additionally, a notification will be sent to the person responsible for the lead. Acceptable values `Y` or `N`

Required parameters are marked with *

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":1608,"fields":{"TITLE":"LLC Titov","NAME":"Gleb","SECOND_NAME":"Egorovich","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":"LLC Titov","NAME":"Gleb","SECOND_NAME":"Egorovich","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: "LLC Titov",
        				NAME: "Gleb",
        				SECOND_NAME: "Egorovich",
        				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: "LLC Titov",
                    NAME: "Gleb",
                    SECOND_NAME: "Egorovich",
                    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`	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` is not a positive integer
`Not found`	The 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 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

Create a New Lead

Get Lead by Id

Update Lead crm.lead.update

Method ParametersMethod Parameters

Parameter fieldsParameter fields

Parameter paramsParameter params

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible ErrorsPossible Errors

Statuses and System Error CodesStatuses and System Error Codes