Create a New Lead crm.lead.add
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:
crmWho can execute the method: any user with permission to create leads
DEPRECATED
The development of this method has been halted. Please use crm.item.add.
The method crm.lead.add creates a new lead.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fields |
Object format:
where:
The list of available fields is described below |
|
params |
Optional array of options ( |
Parameter fields
|
Name |
Description |
||||||||||||||||||||||||||
|
ADDRESS |
Address |
||||||||||||||||||||||||||
|
ADDRESS_2 |
Second line of the address. In some countries, it is customary to split the address into 2 parts |
||||||||||||||||||||||||||
|
ADDRESS_CITY |
City |
||||||||||||||||||||||||||
|
ADDRESS_COUNTRY |
Country |
||||||||||||||||||||||||||
|
ADDRESS_COUNTRY_CODE |
Country code |
||||||||||||||||||||||||||
|
ADDRESS_POSTAL_CODE |
Postal code |
||||||||||||||||||||||||||
|
ADDRESS_PROVINCE |
Province |
||||||||||||||||||||||||||
|
ADDRESS_REGION |
Region |
||||||||||||||||||||||||||
|
ASSIGNED_BY_ID |
Responsible person |
||||||||||||||||||||||||||
|
BIRTHDATE |
Birthdate |
||||||||||||||||||||||||||
|
COMMENTS |
Comments |
||||||||||||||||||||||||||
|
COMPANY_ID |
Link the lead to a company |
||||||||||||||||||||||||||
|
COMPANY_TITLE |
Company name as specified in the corresponding lead field. To link an existing company, pass its id in the COMPANY_ID field |
||||||||||||||||||||||||||
|
CONTACT_ID |
Link the lead to a contact |
||||||||||||||||||||||||||
|
CONTACT_IDS |
List of contacts linked to the lead. Contacts can be added or removed using the group of methods crm.lead.contact.* |
||||||||||||||||||||||||||
|
CURRENCY_ID |
Currency identifier |
||||||||||||||||||||||||||
|
EMAIL |
Email address. Multiple |
||||||||||||||||||||||||||
|
HONORIFIC |
Salutation |
||||||||||||||||||||||||||
|
Messenger. Multiple |
|||||||||||||||||||||||||||
|
LINK |
User ID linked through Open Channels. Multiple |
||||||||||||||||||||||||||
|
LAST_NAME |
Last name |
||||||||||||||||||||||||||
|
NAME |
First name |
||||||||||||||||||||||||||
|
SECOND_NAME |
Middle name |
||||||||||||||||||||||||||
|
OPENED |
Indicator of lead availability for everyone. Acceptable values are |
||||||||||||||||||||||||||
|
OPPORTUNITY |
Amount |
||||||||||||||||||||||||||
|
IS_MANUAL_OPPORTUNITY |
Indicator of manual calculation mode for the amount. Acceptable values are Y or N |
||||||||||||||||||||||||||
|
ORIGINATOR_ID |
Identifier of the data source. Used only for linking to an external source |
||||||||||||||||||||||||||
|
ORIGIN_ID |
Identifier of the item in the data source. Used only for linking to an external source |
||||||||||||||||||||||||||
|
PHONE |
Phone. Multiple |
||||||||||||||||||||||||||
|
POST |
Position |
||||||||||||||||||||||||||
|
SOURCE_DESCRIPTION |
Description of the source |
||||||||||||||||||||||||||
|
SOURCE_ID |
Identifier of the source.
The list of all possible identifiers from the directory can be obtained using the method crm.status.list with the filter |
||||||||||||||||||||||||||
|
STATUS_DESCRIPTION |
Additional information about the stage |
||||||||||||||||||||||||||
|
STATUS_ID |
Identifier of the lead stage. Default stages:
The list of all possible stages from the directory can be obtained using the method crm.status.list with the filter |
||||||||||||||||||||||||||
|
TITLE |
Lead title |
||||||||||||||||||||||||||
|
UTM_CAMPAIGN |
Advertising campaign designation |
||||||||||||||||||||||||||
|
UTM_CONTENT |
Content of the campaign. For example, for contextual ads |
||||||||||||||||||||||||||
|
UTM_MEDIUM |
Type of traffic. CPC (ads), CPM (banners) |
||||||||||||||||||||||||||
|
UTM_SOURCE |
Advertising system. Google Ads, Bing Ads, etc. |
||||||||||||||||||||||||||
|
UTM_TERM |
Search condition of the campaign. For example, keywords for contextual advertising |
||||||||||||||||||||||||||
|
WEB |
Website. Multiple |
||||||||||||||||||||||||||
|
UF_... |
Custom fields. For example, Depending on the portal settings, leads may have a set of custom fields of defined types. 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 adding 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 adding the lead.
Parameter params
|
Name |
Description |
|
REGISTER_SONET_EVENT |
Flag |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"TITLE":"IP 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.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"TITLE":"IP 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.add
try
{
const response = await $b24.callMethod(
'crm.lead.add',
{
fields:
{
TITLE: 'IP 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(`Lead created with ID ${result}`);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'crm.lead.add',
[
'fields' => [
'TITLE' => 'IP 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 = $response
->getResponseData()
->getResult();
echo 'Lead created with ID ' . $result;
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error creating lead: ' . $e->getMessage();
}
BX24.callMethod(
"crm.lead.add",
{
fields:
{
TITLE: "IP 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(`Lead created with ID ${result.data()}`);
}
);
require_once('crest.php');
$result = CRest::call(
'crm.lead.add',
[
'fields' => [
'TITLE' => 'IP 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',
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": 3465,
"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 |
Description |
|
result |
Root element of the response, contains the identifier of the created lead |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 40x, 50x Error
{
"error": "",
"error_description": "Access denied."
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Errors
|
Code |
Error Text |
Description |
|
Empty Value |
Access denied. |
The user does not have permission to add a lead |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
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 |
|
|
|
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 |
Continue Learning
- Delete Lead crm.lead.delete
- Get CRM Lead Fields `crm.lead.fields`
- Add a Lead via Web Form
- Add Lead with Files via Web Form
- Add Duplicate Lead
- Add a CRM Activity to a New Lead or Deal Depending on the CRM Mode