SPA 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.
SPA item fields are returned by the crm.smartprocess<entityTypeId>.get and crm.smartprocess<entityTypeId>.list methods and accepted by the crm.smartprocess<entityTypeId>.add and crm.smartprocess<entityTypeId>.update methods. The method name includes the SPA type ID entityTypeId, for example, crm.smartprocess1038.get. Type IDs and settings are returned by the crm.type.list method.
The set of fields depends on the SPA type settings: without pipelines, an item has no categoryId, and without stages, it has no stageId and other stage fields. For such fields, the SPA Object table specifies which type setting is required. The list of fields of a specific type is returned by the crm.smartprocess<entityTypeId>.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 SPA Object table that can be edited, and custom fields. There are no required fields: an item is created even with an empty |
ID of the created item |
|
|
Item |
Success flag |
|
|
Item |
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 "contactId" 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, 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, 2026-11-03. Such a field does not accept a date with time or a date in the 03.11.2026 format. Fields of the datetime type are returned in ISO 8601 format, for example, 2026-11-03T14:47:23+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 and of the lastCommunication object, for example, ["company.title", "=", "Müller GmbH"]. Filtering by fields of employees, stage, pipeline, 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, stageSemanticId, and stageSemantic fields are present in the crm.smartprocess<entityTypeId>.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. The stage group can be retrieved from the semanticId field of the stage object: "select": ["stage.semanticId"].
SPA Object
|
Name |
Description |
|
title |
Item title, up to 255 characters. If the title is not passed on creation, Bitrix24 sets a title in the Can be edited, filtered, and sorted |
|
xmlId |
External code of the item, up to 255 characters. Use it to link the item to a record in an external system. Can be edited, filtered, and sorted |
|
id |
Item ID. Assigned on creation. Read-only. Can be filtered and sorted |
|
createdTime |
Date and time the item was created. Read-only. Can be filtered and sorted |
|
createdById |
ID of the user who created the item. Read-only. Can be filtered and sorted |
|
createdBy |
User who created the item. An object of type employee. Read-only. Requested in |
|
updatedTime |
Date and time the item was last updated. Read-only. Can be filtered and sorted |
|
updatedById |
ID of the user who last updated the item. Read-only. Can be filtered and sorted |
|
updatedBy |
User who last updated the item. An object of type employee. Read-only. Requested in |
|
lastActivityTime |
Date and time of the last activity in the item 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 item. 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 item is available to all users: Can be edited, filtered, and sorted |
|
webformId |
ID of the CRM form through which the item was created. If the item was not created by a form, Read-only. Can be filtered and sorted |
|
webform |
CRM form through which the item was created. An object of type CRM form. Read-only. Requested in |
|
lastCommunication |
Dates of the last communications with the client on the item. An object of type last communication. Read-only. Requested in |
|
entityTypeId |
SPA type ID, for example, Read-only |
|
canRead |
Whether the current user can view the item: Read-only |
|
url |
Relative link to the item card, for example, Read-only |
|
stageId |
Stage ID, for example, Can be edited, filtered, and sorted. Available if stages are enabled in the type settings: |
|
stage |
Item stage. An object of type stage. Read-only. Requested in Available if stages are enabled in the type settings: |
|
movedTime |
Date and time of the last stage change. Read-only. Can be filtered and sorted. Available if stages are enabled in the type settings: |
|
movedById |
ID of the user who last changed the stage. Read-only. Can be filtered and sorted. Available if stages are enabled in the type settings: |
|
movedBy |
User who last changed the stage. An object of type employee. Read-only. Requested in Available if stages are enabled in the type settings: |
|
closed |
Whether the item is closed: Read-only. The field is present in the Available if stages are enabled in the type settings: |
|
stageSemanticId |
Stage group. Possible values:
Read-only. The field is present in the Available if stages are enabled in the type settings: |
|
stageSemantic |
Stage group with its name: Read-only. The field is present in the Available if stages are enabled in the type settings: |
|
beginTime |
Start date. If not passed on creation, Bitrix24 sets the item creation date. Can be edited, filtered, and sorted. Available if start and end dates are enabled in the type settings: |
|
closeTime |
End date. If not passed on creation, Bitrix24 sets the date seven days after the item is created. Can be edited, filtered, and sorted. Available if start and end dates are enabled in the type settings: |
|
categoryId |
Pipeline ID. If not passed on creation, the item is placed in the default pipeline. Type pipelines are returned by the Can be edited, filtered, and sorted. Available if pipelines are enabled in the type settings: |
|
category |
Item pipeline. An object of type pipeline. Read-only. Requested in Available if pipelines are enabled in the type settings: |
|
observersId |
Observer IDs. User IDs are returned by the user.get method. Can be edited and filtered, cannot be sorted. In a filter, Available if observers are enabled in the type settings: |
|
observers |
Observers. An array of objects of type employee. If there are no observers, an empty array. Read-only. Requested in Available if observers are enabled in the type settings: |
|
contactId |
ID of the primary contact, which is the first one in the Read-only. Can be filtered, cannot be sorted. Available if the client link is enabled in the type settings: |
|
contact |
Primary contact. An object of type CRM item. Read-only. Requested in Available if the client link is enabled in the type settings: |
|
contactsId |
IDs of the item contacts. 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. Available if the client link is enabled in the type settings: |
|
contacts |
Item contacts. An array of objects of type CRM item. If there are no contacts, an empty array. Read-only. Requested in Available if the client link is enabled in the type settings: |
|
companyId |
Company ID. Companies are returned by the crm.company.list method. Can be edited, filtered, and sorted. Available if the client link is enabled in the type settings: |
|
company |
Company. An object of type CRM item. Read-only. Requested in Available if the client link is enabled in the type settings: |
|
myCompanyId |
ID of your company, on whose behalf you work with the client. The list of your companies is returned by the crm.mycompany.list method. Can be edited, filtered, and sorted. Available if your company requisites are enabled in the type settings: |
|
myCompany |
Your company. An object of type CRM item. Read-only. Requested in Available if your company requisites are enabled in the type settings: |
|
sourceId |
Source ID, for example, Can be edited, filtered, and sorted. Available if the source field is enabled in the type settings: |
|
source |
Source. An object of type reference list value. Read-only. Requested in Available if the source field is enabled in the type settings: |
|
sourceDescription |
Additional information about the source. Can be edited and filtered, cannot be sorted. Available if the source field is enabled in the type settings: |
|
opportunity |
Item amount, not less than Can be edited, filtered, and sorted. Available if product linking is enabled in the type settings: |
|
taxValue |
Tax amount. Calculated from the product rows. Read-only. Can be filtered and sorted. Available if product linking is enabled in the type settings: |
|
isManualOpportunity |
Amount calculation mode: Can be edited, filtered, and sorted. Available if product linking is enabled in the type settings: |
|
currencyId |
Currency ID, for example, Can be edited, filtered, and sorted. Available if product linking is enabled in the type settings: |
|
currency |
Currency. An object of type currency. Read-only. Requested in Available if product linking is enabled in the type settings: |
|
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 SPA is subordinate to another object type. For each parent type, the SPA has a pair of fields:
related<type code>Id— ID of the parent item, for example,relatedLeadIdfor a lead,relatedSmartInvoiceIdfor an invoice,relatedSmartProcess177Idfor the SPA withentityTypeId = 177related<type code>— the parent item as an object of type CRM item, for example,relatedLead
The field title in the field.list response matches the name of the parent type, for example, "Lead" or "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'.
Each type has its own set of these fields. The current list is returned by the crm.smartprocess<entityTypeId>.field.list method.
Related Objects
A related object is requested in select by the field name without the Id suffix: assignedBy, stage, category. 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, myCompany, 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 or contacts, 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, myCompany, 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, |
Stage Object
Field stage.
|
Name |
Description |
|
id |
Stage ID, for example, |
|
name |
Stage name |
|
sort |
Stage order in the pipeline |
|
color |
Stage color in the |
|
semanticId |
Stage group: |
Pipeline Object
Field category.
|
Name |
Description |
|
id |
Pipeline ID |
|
name |
Pipeline name |
|
sort |
Pipeline sort order |
|
isDefault |
Default pipeline: |
Reference List Value Object
Field 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 |
Custom Fields
Custom SPA fields are named UF_CRM_<type id>_<code>, for example, UF_CRM_3_1628508893. The name contains the type ID id, not entityTypeId: the field in the example belongs to the type with id = 3 and entityTypeId = 174. Both IDs are returned by the crm.type.list method. Custom fields are passed and requested by name in the same way as standard fields. The list of custom fields of the type is returned by the crm.smartprocess<entityTypeId>.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.