Lead Fields in REST 3.0
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
These fields belong to REST 3.0 methods. The call specifics and response format of the new API version are described in the REST 3.0 overview.
Lead fields are returned by the crm.lead.get and crm.lead.list methods and accepted by the crm.lead.add and crm.lead.update methods. The list of fields with their attributes is returned by the crm.lead.field.list method.
Some fields exist in two forms: as an ID and as a related object, for example, assignedById and assignedBy. The ID can be passed when writing data, while the related object can only be requested in select.
Which Fields the Methods Accept and Return
|
Method |
Accepts |
Returns |
|
Fields of the Lead Object table that can be edited, and custom fields. The required field is |
ID of the created lead |
|
|
Lead |
Success flag |
|
|
Lead |
Without |
|
|
|
Without |
The add and update methods do not accept fields marked "read-only" and return the BITRIX_REST_V3_EXCEPTION_VALIDATION_DTOVALIDATIONEXCEPTION error with the message 'Field "hasPhone" is read-only.' Related objects, for example, company and stage, are also read-only: to write data, pass the ID — companyId, stageId.
The method validates fields with values from reference lists when writing data. If the value is not in the reference list, the method returns the error 'Field value is not one of the possible values'. For the stage, salutation, source, and currency, the error message lists the allowed values.
Boolean fields accept and return true or false. The values Y, N, 1, and 0 are not accepted: the method returns the error 'This request requires data type "bool" in field "opened"'.
Fields of the date type accept and return a date in the YYYY-MM-DD format, for example, 1990-05-15. Such a field does not accept a date with time or a date in the 15.05.1990 format. Fields of the datetime type are returned in ISO 8601 format, for example, 2026-11-03T14:48:48+03:00. In a filter by a datetime field, also pass a date with time: the method does not accept the value 2026-11-03.
You can filter and sort only by the fields whose description says so. For other fields, the list method returns an error stating that the field 'requires attribute "Filterable"' or '"Sortable"'. Dot notation lets you filter by fields of linked CRM items, of phone, email, website, and messenger values, and of the lastCommunication and utm objects, for example, ["company.title", "=", "Müller GmbH"] or ["im.valueTypeId", "=", "IMOL"]. Filtering by fields of employees, stage, and source, for example, assignedBy.id or stage.semanticId, is not supported: the method returns the BITRIX_REST_V3_EXCEPTION_INVALIDFILTEREXCEPTION error. The filter format is described on the crm.<type>.list page and in the REST API 3.0 Overview article.
The closed and taxValue fields are present in the crm.lead.field.list response, but the get and list methods do not accept them. For such a field in select, filter, or order, the method returns the BITRIX_REST_V3_EXCEPTION_UNKNOWNDTOPROPERTYEXCEPTION error.
Lead Object
|
Name |
Description |
|
title |
Lead title, up to 255 characters. Required for creating a lead. Can be edited, filtered, and sorted |
|
honorificId |
Salutation ID, for example, Can be edited, filtered, and sorted |
|
honorific |
Salutation. An object of type reference list value. Read-only. Requested in |
|
name |
First name, up to 50 characters. Can be edited, filtered, and sorted |
|
secondName |
Middle name, up to 50 characters. Can be edited, filtered, and sorted |
|
lastName |
Last name, up to 50 characters. Can be edited, filtered, and sorted |
|
post |
Position, up to 255 characters. Can be edited, filtered, and sorted |
|
companyTitle |
Name of the client's company, up to 255 characters. This is text in the lead card, not a link to a CRM company — the link is set by the Can be edited, filtered, and sorted |
|
birthdayTime |
Date of birth. Can be edited, filtered, and sorted |
|
statusDescription |
Additional information about the lead stage. Can be edited, filtered, and sorted |
|
id |
Lead ID. Assigned on creation. Read-only. Can be filtered and sorted |
|
createdTime |
Date and time the lead was created. Read-only. Can be filtered and sorted |
|
createdById |
ID of the user who created the lead. Read-only. Can be filtered and sorted |
|
createdBy |
User who created the lead. An object of type employee. Read-only. Requested in |
|
updatedTime |
Date and time the lead was last updated. Read-only. Can be filtered and sorted |
|
updatedById |
ID of the user who last updated the lead. Read-only. Can be filtered and sorted |
|
updatedBy |
User who last updated the lead. An object of type employee. Read-only. Requested in |
|
lastActivityTime |
Date and time of the last activity in the lead timeline. Read-only. Can be filtered and sorted |
|
lastActivityById |
ID of the author of the last activity in the timeline. Read-only. Can be filtered and sorted |
|
lastActivityBy |
Author of the last activity in the timeline. An object of type employee. Read-only. Requested in |
|
assignedById |
ID of the person responsible for the lead. User IDs are returned by the user.get method. If the user does not exist, the method returns the error 'Field value is not one of the possible values'. Can be edited, filtered, and sorted |
|
assignedBy |
Responsible person. An object of type employee. Read-only. Requested in |
|
opened |
Whether the lead is available to all users: Can be edited, filtered, and sorted |
|
comments |
Comment on the lead. Supports BB codes, for example, Can be edited. Cannot be filtered or sorted |
|
originatorId |
ID of the external system the lead came from. Use together with Can be edited, filtered, and sorted |
|
originId |
Lead ID in the external system. Can be edited, filtered, and sorted |
|
webformId |
ID of the CRM form through which the lead was created. If the lead was not created by a form, Read-only. Can be filtered and sorted |
|
webform |
CRM form through which the lead was created. An object of type CRM form. Read-only. Requested in |
|
lastCommunication |
Dates of the last communications with the client on the lead. An object of type last communication. Read-only. Requested in |
|
entityTypeId |
Object type ID. For a lead, Read-only |
|
canRead |
Whether the current user can view the lead: Read-only |
|
url |
Relative link to the lead card, for example, Read-only |
|
stageId |
Lead stage ID, for example, Can be edited, filtered, and sorted |
|
stage |
Lead stage. An object of type stage. Read-only. Requested in |
|
movedTime |
Date and time of the last stage change. Read-only. Can be filtered and sorted |
|
movedById |
ID of the user who last changed the stage. Read-only. Can be filtered and sorted |
|
movedBy |
User who last changed the stage. An object of type employee. Read-only. Requested in |
|
closed |
Whether the lead is closed. Read-only. The field is present in the |
|
stageSemanticId |
Stage group. Possible values:
Read-only. Can be filtered and sorted |
|
stageSemantic |
Stage group with its name. An object of type stage group. Read-only. Requested in |
|
observersId |
Observer IDs. User IDs are returned by the user.get method. Can be edited and filtered, cannot be sorted. In a filter, |
|
observers |
Observers. An array of objects of type employee. If there are no observers, an empty array. Read-only. Requested in |
|
contactId |
ID of the primary contact, which is the first one in the Read-only. Can be filtered, cannot be sorted |
|
contact |
Primary contact. An object of type CRM item. Read-only. Requested in |
|
contactsId |
IDs of the contacts the lead is linked to. Contacts are returned by the crm.contact.list method. The passed array replaces the current list of contacts. Can be edited and filtered, cannot be sorted |
|
contacts |
Lead contacts. An array of objects of type CRM item. If there are no contacts, an empty array. Read-only. Requested in |
|
companyId |
ID of the CRM company the lead is linked to. Companies are returned by the crm.company.list method. Can be edited, filtered, and sorted |
|
company |
Company. An object of type CRM item. Read-only. Requested in |
|
sourceId |
Source ID, for example, Can be edited, filtered, and sorted |
|
source |
Source. An object of type reference list value. Read-only. Requested in |
|
sourceDescription |
Additional information about the source. Can be edited and filtered, cannot be sorted |
|
opportunity |
Lead amount, not less than Can be edited, filtered, and sorted |
|
taxValue |
Tax amount. Read-only. The field is present in the |
|
isManualOpportunity |
Amount calculation mode: Can be edited, filtered, and sorted |
|
currencyId |
Currency ID, for example, Can be edited, filtered, and sorted |
|
currency |
Currency. An object of type currency. Read-only. Requested in |
|
phone |
Phone numbers. An array of objects of type multiple field value. Phone types are returned by the crm.dictionary.phonetype.list method. Can be edited: the passed array replaces all phone numbers of the lead, for example, |
|
email |
Email addresses. An array of objects of type multiple field value. Email types are returned by the crm.dictionary.emailtype.list method. Can be edited: the passed array replaces all email addresses of the lead. Can be filtered by object fields using dot notation, cannot be sorted |
|
web |
Websites. An array of objects of type multiple field value. Website types are returned by the crm.dictionary.webtype.list method. Can be edited: the passed array replaces all websites of the lead. Can be filtered by object fields using dot notation, cannot be sorted |
|
im |
Messengers and open channels. An array of objects of type multiple field value. Messenger types are returned by the crm.dictionary.imtype.list method. Can be edited: the passed array replaces all values of this field. Can be filtered by object fields using dot notation, for example, |
|
hasPhone |
Whether the lead has at least one phone number: Read-only. Cannot be filtered or sorted |
|
hasEmail |
Whether the lead has at least one email address: Read-only. Cannot be filtered or sorted |
|
hasWeb |
Whether the lead has at least one website: Read-only. Cannot be filtered or sorted |
|
hasIm |
Whether the lead has at least one value in the Read-only. Cannot be filtered or sorted |
|
utm |
UTM tags of the lead. An object of type UTM tags. If there are no tags, Can be edited: pass an object with the tags you need, for example, |
|
trackingSourceId |
ID of the end-to-end analytics source. Can be edited and filtered, cannot be sorted |
|
related<type code>Id |
ID of the parent item of another object type, for example, Can be edited and filtered, cannot be sorted |
|
related<type code> |
Parent item of another object type, for example, Read-only. Requested in |
Fields Linking to Other Types
The related<type code>Id and related<type code> fields appear when Bitrix24 has a link configured in which the lead is subordinate to another object type, for example, an SPA. For each parent type, the lead has a pair of fields:
related<type code>Id— ID of the parent item, for example,relatedSmartProcess177Idfor the SPA withentityTypeId = 177related<type code>— the parent item as an object of type CRM item, for example,relatedSmartProcess177
The field title in the crm.lead.field.list response matches the name of the parent type, for example, "Equipment purchase". The method checks that an item with the passed ID exists. If there is no such item, the method returns the error 'Field value is not one of the possible values'.
The set of these fields depends on the links configured in Bitrix24. The current list is returned by the crm.lead.field.list method.
Related Objects
A related object is requested in select by the field name without the Id suffix: assignedBy, stage, honorific. The whole object name returns all of its fields, and a dot-notation path returns only the selected ones, for example, ["stage.name", "assignedBy.firstName"]. The path supports one level of nesting.
A linked CRM item — contact, company, related<type code> — returns only id when requested by its whole name. Request the other item fields using dot notation, for example, ["company.title", "company.url"].
If a link is not set, the object is returned as null, and an array of objects, for example, observers, contacts, or phone, is returned as an empty array.
Employee Object
Fields createdBy, updatedBy, lastActivityBy, assignedBy, movedBy, observers.
|
Name |
Description |
|
id |
User ID |
|
firstName |
First name |
|
lastName |
Last name |
|
personalGender |
Gender: |
|
url |
Relative link to the user profile, for example, |
|
personalPhoto |
Link to the user photo. If there is no photo, |
CRM Item Object
Fields contact, contacts, company, related<type code>.
|
Name |
Description |
|
id |
Item ID |
|
entityTypeId |
Object type ID, for example, |
|
canRead |
Whether the current user can view the item |
|
title |
Item title. For a contact, the last name, first name, and middle name |
|
url |
Relative link to the item card, for example, |
Phone Numbers, Email, Websites, and Messengers
Fields phone, email, web, im. When writing data, pass valueTypeId and value, both are required. If the value type is not in the reference list, the method returns the error 'Field value is not one of the possible values'.
|
Name |
Description |
|
id |
Value ID. Assigned when writing data; when the list is replaced, the values receive new IDs |
|
valueTypeId |
Value type, for example, |
|
valueType |
Value type with its name: |
|
value |
Value: phone number, email address, website address, or messenger ID |
Stage Object
Field stage.
|
Name |
Description |
|
id |
Stage ID, for example, |
|
name |
Stage name |
|
sort |
Stage order |
|
color |
Stage color in the |
|
semanticId |
Stage group: |
Stage Group Object
Field stageSemantic. The reference list of groups is returned by the crm.dictionary.stagesemantic.list method.
|
Name |
Description |
|
id |
Group ID: |
|
name |
Group name, for example, |
Reference List Value Object
Fields honorific and source.
|
Name |
Description |
|
id |
Value ID, for example, |
|
name |
Value name, for example, |
|
sort |
Sort order |
CRM Form Object
Field webform.
|
Name |
Description |
|
id |
CRM form ID |
|
name |
CRM form name |
Last Communication Object
Field lastCommunication. If there has been no communication of a given kind, the corresponding field is null.
|
Name |
Description |
|
communicationTime |
Date and time of the last communication of any kind |
|
callTime |
Date and time of the last call |
|
emailTime |
Date and time of the last email |
|
imolTime |
Date and time of the last message in an open channel |
|
webformTime |
Date and time the CRM form was last submitted |
Currency Object
Field currency.
|
Name |
Description |
|
id |
Currency code, for example, |
|
fullName |
Currency name |
|
formatString |
Amount display template. The |
|
decPoint |
Decimal separator |
|
thousandsSep |
Thousands separator. May be returned as an HTML entity, for example, |
|
decimals |
Number of decimal places |
|
hideZero |
Whether to hide insignificant trailing zeros in the fractional part |
|
amount |
Exchange rate relative to the base currency |
|
amountCount |
Number of currency units the exchange rate applies to |
|
base |
Base currency: |
|
sort |
Sort order |
|
numericCode |
Numeric currency code, for example, |
|
languageId |
Language for which the name and format are set |
|
createdTime |
Date and time the currency was created |
|
updatedTime |
Date and time the currency was updated |
|
createdById |
ID of the user who created the currency |
|
updatedById |
ID of the user who updated the currency |
UTM Tags Object
Field utm. Each tag is a string of up to 255 characters. Tags that were not passed are returned as null.
|
Name |
Description |
|
source |
Ad platform, the |
|
medium |
Traffic type, the |
|
campaign |
Ad campaign, the |
|
content |
Ad content, the |
|
term |
Keyword, the |
Custom Fields
Custom lead fields are named UF_CRM_<code>, for example, UF_CRM_1687961618. They are passed and requested by name in the same way as standard fields. The list of custom fields is returned by the crm.lead.field.custom.list method.
Each custom field has a paired UF_CRM_…_data field, which is read-only and requested in select. It contains the value in several representations:
value— the value in the same format as in the field itselfrawValue— the value in the storage format, for example,100.5|EURfor a "Money" fieldformattedValue— the value for display to the user:100.50 €for money, the employee name for a "Link to employee" field, the option text for a listextra— additional data: for money,amount,currencyId, andcurrencyFullName; for an employee, the fields of the employee object. For a string, date, and list,null
For a multiple custom field, UF_CRM_…_data is an array of such objects.