Create a New Lead crm.lead.add
Scope:
crmWho can execute the method: any user with permission to create leads
Method Development Stopped
The method crm.lead.add continues to function, but there is a more relevant alternative 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 |
State |
||||||||||||||||||||||||||
|
ADDRESS_REGION |
Region |
||||||||||||||||||||||||||
|
ASSIGNED_BY_ID |
Responsible person |
||||||||||||||||||||||||||
|
BIRTHDATE |
Date of birth |
||||||||||||||||||||||||||
|
COMMENTS |
Comments |
||||||||||||||||||||||||||
|
COMPANY_ID |
Link the lead to a company |
||||||||||||||||||||||||||
|
COMPANY_TITLE |
Company name 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 an open channel. Multiple |
||||||||||||||||||||||||||
|
LAST_NAME |
Last name |
||||||||||||||||||||||||||
|
NAME |
First name |
||||||||||||||||||||||||||
|
SECOND_NAME |
Middle name |
||||||||||||||||||||||||||
|
OPENED |
Indicator of lead availability to 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 AdWords, and others |
||||||||||||||||||||||||||
|
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
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
- Delete lead crm.lead.delete
- Get Lead Fields crm.lead.fields
- Add Lead via Web Form
- Add a lead with files via a web form
- Add Repeat Lead
- Add an activity to a new lead or deal depending on the CRM mode