Fields of Main CRM Objects
Attention! A more complete list of fields can be found on the pages of methods that return the description of object fields. Such methods are named crm.object_name.fields.
The field description is returned by the method crm.deal.fields
|
Name |
Description |
Read |
Write |
|
ID |
Deal identifier |
Yes |
No |
|
TITLE |
Title |
Yes |
Yes |
|
TYPE_ID |
Type of deal. Used only for linking to external sources. |
Yes |
Yes |
|
CATEGORY_ID |
Identifier of the direction. Immutable. If this field is not provided when creating a deal, the deal will be created in the general direction. |
Yes |
Yes |
|
STAGE_ID |
Identifier of the stage. Possible values:
|
Yes |
Yes |
|
STAGE_SEMANTIC_ID |
Name. Read-only. In a sense, summarizes the values of the deal identifier
|
Yes |
No |
|
IS_NEW |
Flag for a new deal (deals in the first stage) |
Yes |
No |
|
IS_RECURRING |
Flag for a recurring deal template. If set to |
Yes |
Yes |
|
IS_RETURN_CUSTOMER |
Indicator of a repeat lead |
Yes |
Yes |
|
IS_REPEATED_APPROACH |
Repeated approach |
Yes |
Yes |
|
PROBABILITY |
Probability |
Yes |
Yes |
|
CURRENCY_ID |
Identifier of the deal currency |
Yes |
Yes |
|
OPPORTUNITY |
Amount |
Yes |
Yes |
|
IS_MANUAL_OPPORTUNITY |
Indicator of manual opportunity calculation |
Yes |
Yes |
|
TAX_VALUE |
Tax rate |
Yes |
Yes |
|
COMPANY_ID |
Identifier of the linked company |
Yes |
Yes |
|
CONTACT_ID |
Identifier of the linked contact. Deprecated. Kept for compatibility |
Yes |
Yes |
|
CONTACT_IDS |
Identifier of the linked contact. Multiple. When using crm.deal.update and crm.deal.add, an array of contacts can be submitted. In the methods crm.deal.list and crm.deal.get, this field does not exist, and crm.deal.contact.items.get should be used to get the list of contacts. To clear the field, use crm.deal.contact.items.delete, to replace the value use crm.deal.contact.items.set |
Yes |
Yes |
|
QUOTE_ID |
Identifier of the quote. Read-only. Deprecated. Use the method crm.quote.list with a filter by deal |
Yes |
No |
|
BEGINDATE |
Start date |
Yes |
Yes |
|
CLOSEDATE |
End date |
Yes |
Yes |
|
OPENED |
Available to everyone |
Yes |
Yes |
|
CLOSED |
Whether the deal is closed |
Yes |
Yes |
|
COMMENTS |
Comments |
Yes |
Yes |
|
ASSIGNED_BY_ID |
Linked to user by ID |
Yes |
Yes |
|
CREATED_BY_ID |
Created by user |
Yes |
No |
|
MODIFY_BY_ID |
Identifier of the author of the last change |
Yes |
No |
|
MOVED_BY_ID |
Identifier of the author who moved the item to the current stage |
Yes |
No |
|
DATE_CREATE |
Creation date |
Yes |
No |
|
DATE_MODIFY |
Modification date |
Yes |
No |
|
MOVED_TIME |
Date of moving the item to the current stage |
Yes |
No |
|
SOURCE_ID |
Identifier of the source. Defines the source of the deal (callback, advertisement, e-mail, etc.). A list of possible identifiers can be obtained using the method crm.status.list with the filter |
Yes |
Yes |
|
SOURCE_DESCRIPTION |
Additional information about the source. Text field |
Yes |
Yes |
|
ADDITIONAL_INFO |
Additional information |
Yes |
Yes |
|
LEAD_ID |
Identifier of the linked lead |
Yes |
No |
|
LOCATION_ID |
Client's location. Service field, not recommended for use |
Yes |
Yes |
|
ORIGINATOR_ID |
Identifier of the data source. Used only for linking to external sources |
Yes |
Yes |
|
ORIGIN_ID |
Identifier of the item in the data source. Used only for linking to external sources |
Yes |
Yes |
|
UTM_SOURCE |
Advertising system (Google-Adwords, etc.) |
Yes |
Yes |
|
UTM_MEDIUM |
Type of traffic: CPC (ads), CPM (banners) |
Yes |
Yes |
|
UTM_CAMPAIGN |
Designation of the advertising campaign |
Yes |
Yes |
|
UTM_CONTENT |
Content of the campaign. For example, for contextual ads |
Yes |
Yes |
|
UTM_TERM |
Search condition of the campaign. For example, keywords for contextual advertising |
Yes |
Yes |
|
PARENT_ID_xxx |
Relationship fields. If there are SPAs related to contacts on the account, then for each such SPA there is a field that stores the relationship between this SPA and the contact. The field itself stores the identifier of the item of that SPA. For example, the field |
Yes |
Yes |
|
LAST_ACTIVITY_BY |
Identifier of the user responsible for the last activity in this lead (for example, who created a new deal in the lead) |
Yes |
Yes |
|
LAST_ACTIVITY_TIME |
Time of the last activity |
Yes |
Yes |
|
UF_CRM_xxx |
Yes |
Yes |
The field description is returned by the method crm.lead.fields
|
Name |
Description |
Read |
Write |
|
ID |
Integer identifier of the lead |
Yes |
No |
|
TITLE |
Title of the lead |
Yes |
Yes |
|
HONORIFIC |
Form of address. Status from the directory. A list of possible identifiers can be obtained using the method crm.status.list with the filter |
Yes |
Yes |
|
NAME |
Contact's first name |
Yes |
Yes |
|
SECOND_NAME |
Contact's middle name |
Yes |
Yes |
|
LAST_NAME |
Contact's last name |
Yes |
Yes |
|
BIRTHDATE |
Date of birth |
Yes |
Yes |
|
COMPANY_TITLE |
Title of the company linked to the lead |
Yes |
Yes |
|
SOURCE_ID |
Identifier of the source. Status from the directory. A list of possible identifiers can be obtained using the method crm.status.list with the filter |
Yes |
Yes |
|
SOURCE_DESCRIPTION |
Description of the source |
Yes |
Yes |
|
STATUS_ID |
Identifier of the lead stage. Status from the directory. A list of possible identifiers can be obtained using the method crm.status.list with the filter |
Yes |
Yes |
|
STATUS_DESCRIPTION |
Additional information about the stage |
Yes |
Yes |
|
STATUS_SEMANTIC_ID |
Status. Possible values:
|
Yes |
No |
|
POST |
Position |
Yes |
Yes |
|
ADDRESS |
Contact's address |
Yes |
Yes |
|
ADDRESS_2 |
Second line of the address. In some countries, it is customary to split the address into 2 parts |
Yes |
Yes |
|
ADDRESS_CITY |
City |
Yes |
Yes |
|
ADDRESS_POSTAL_CODE |
Postal code |
Yes |
Yes |
|
ADDRESS_REGION |
Region |
Yes |
Yes |
|
ADDRESS_PROVINCE |
Province |
Yes |
Yes |
|
ADDRESS_COUNTRY |
Country |
Yes |
Yes |
|
ADDRESS_COUNTRY_CODE |
Country code |
Yes |
Yes |
|
ADDRESS_LOC_ADDR_ID |
Identifier of the address from the location module |
Yes |
Yes |
|
CURRENCY_ID |
Identifier of the currency |
Yes |
Yes |
|
OPPORTUNITY |
Estimated amount |
Yes |
Yes |
|
IS_MANUAL_OPPORTUNITY |
Indicator of manual calculation of the amount. Allowed values |
Yes |
Yes |
|
OPENED |
Available to everyone. Allowed values |
Yes |
Yes |
|
COMMENTS |
Comments |
Yes |
Yes |
|
HAS_PHONE |
Indicator of the phone field being filled. Allowed values |
Yes |
No |
|
HAS_EMAIL |
Indicator of the e-mail field being filled. Allowed values |
Yes |
No |
|
HAS_IMOL |
Indicator of the presence of a linked open line. Allowed values |
Yes |
No |
|
ASSIGNED_BY_ID |
Identifier of the user responsible for the lead |
Yes |
Yes |
|
CREATED_BY_ID |
Identifier of the user who created the lead |
Yes |
No |
|
MODIFY_BY_ID |
Identifier of the author of the last change |
Yes |
No |
|
MOVED_BY_ID |
Identifier of the author who moved the item to the current stage |
Yes |
No |
|
DATE_CREATE |
Creation date |
Yes |
No |
|
DATE_MODIFY |
Modification date |
Yes |
No |
|
MOVED_TIME |
Date of moving the item to the current stage |
Yes |
No |
|
COMPANY_ID |
Linking the lead to a company (Field Client->Company) |
Yes |
Yes |
|
CONTACT_ID |
Linking the lead to a contact. Deprecated field, currently not used. Kept for backward compatibility |
Yes |
Yes |
|
CONTACT_IDS |
Identifier of the linked contact. Multiple. When using crm.lead.update and crm.lead.add, an array of contacts can be submitted |
Yes |
Yes |
|
IS_RETURN_CUSTOMER |
Indicator of a repeat lead. Allowed values |
Yes |
No |
|
DATE_CLOSED |
Closing date |
Yes |
No |
|
ORIGINATOR_ID |
Identifier of the data source. Used only for linking to external sources |
Yes |
Yes |
|
ORIGIN_ID |
Identifier of the item in the data source. Used only for linking to external sources |
Yes |
Yes |
|
UTM_SOURCE |
Advertising system (Google-Adwords, etc.) |
Yes |
Yes |
|
UTM_MEDIUM |
Type of traffic: CPC (ads), CPM (banners) |
Yes |
Yes |
|
UTM_CAMPAIGN |
Designation of the advertising campaign |
Yes |
Yes |
|
UTM_CONTENT |
Content of the campaign. For example, for contextual ads |
Yes |
Yes |
|
UTM_TERM |
Search condition of the campaign. For example, keywords for contextual advertising |
Yes |
Yes |
|
LAST_ACTIVITY_TIME |
Time of the last activity |
Yes |
No |
|
LAST_ACTIVITY_BY |
Identifier of the user responsible for the last activity in this lead (for example, who created a new deal in the lead) |
Yes |
No |
|
PHONE |
Contact's phone. Multiple |
Yes |
Yes |
|
EMAIL |
E-mail address. Multiple |
Yes |
Yes |
|
WEB |
URLs of the lead. Multiple |
Yes |
Yes |
|
Messengers. Multiple |
Yes |
Yes |
|
|
LINK |
Links. Multiple. Service |
Yes |
Yes |
|
UF_CRM_xxx |
Yes |
Yes |
The field description is returned by the method crm.company.fields
|
Name |
Description |
Read |
Write |
|
ID |
Identifier of the company |
Yes |
No |
|
TITLE |
Name. Required |
Yes |
Yes |
|
COMPANY_TYPE |
Type of company |
Yes |
Yes |
|
LOGO |
Logo |
Yes |
Yes |
|
ADDRESS |
Address of the company |
Yes |
Yes |
|
ADDRESS_2 |
Second line of the address. In some countries, it is customary to split the address into 2 parts |
Yes |
Yes |
|
ADDRESS_CITY |
City |
Yes |
Yes |
|
ADDRESS_POSTAL_CODE |
Postal code |
Yes |
Yes |
|
ADDRESS_REGION |
Region |
Yes |
Yes |
|
ADDRESS_PROVINCE |
Province |
Yes |
Yes |
|
ADDRESS_COUNTRY |
Country |
Yes |
Yes |
|
ADDRESS_COUNTRY_CODE |
Country code |
Yes |
Yes |
|
ADDRESS_LOC_ADDR_ID |
Identifier of the location address |
Yes |
Yes |
|
ADDRESS_LEGAL |
Legal address |
Yes |
Yes |
|
REG_ADDRESS |
Legal address of the company. Deprecated, used for compatibility |
Yes |
Yes |
|
REG_ADDRESS_2 |
Second line of the legal address. In some countries, it is customary to split the address into 2 parts. |
Yes |
Yes |
|
REG_ADDRESS_CITY |
City of the legal address. Deprecated, used for compatibility |
Yes |
Yes |
|
REG_ADDRESS_POSTAL_CODE |
Postal code of the legal address. Deprecated, used for compatibility |
Yes |
Yes |
|
REG_ADDRESS_REGION |
Region of the legal address. Deprecated, used for compatibility |
Yes |
Yes |
|
REG_ADDRESS_PROVINCE |
Province of the legal address. Deprecated, used for compatibility |
Yes |
Yes |
|
REG_ADDRESS_COUNTRY |
Country of the legal address. Deprecated, used for compatibility |
Yes |
Yes |
|
REG_ADDRESS_COUNTRY_CODE |
Country code of the legal address. Deprecated, used for compatibility |
Yes |
Yes |
|
REG_ADDRESS_LOC_ADDR_ID |
Legal address identifier of the location address. Deprecated, used for compatibility |
Yes |
Yes |
|
BANKING_DETAILS |
Banking details |
Yes |
Yes |
|
INDUSTRY |
Industry |
Yes |
Yes |
|
EMPLOYEES |
Number of employees |
Yes |
Yes |
|
CURRENCY_ID |
Currency |
Yes |
Yes |
|
REVENUE |
Annual revenue |
Yes |
Yes |
|
OPENED |
Available to everyone |
Yes |
Yes |
|
COMMENTS |
Comments |
Yes |
Yes |
|
HAS_PHONE |
Check for the phone field being filled |
Yes |
No |
|
HAS_EMAIL |
Check for the e-mail field being filled |
Yes |
No |
|
HAS_IMOL |
Is there an open line |
Yes |
No |
|
IS_MY_COMPANY |
My company |
Yes |
Yes |
|
ASSIGNED_BY_ID |
Linked to user by ID |
Yes |
Yes |
|
CREATED_BY_ID |
Who created the company |
Yes |
No |
|
MODIFY_BY_ID |
Identifier of the author of the last change |
Yes |
No |
|
DATE_CREATE |
Creation date |
Yes |
No |
|
DATE_MODIFY |
Modification date |
Yes |
No |
|
CONTACT_ID |
Contact. Used only for linking to external sources. |
Yes |
Yes |
|
LEAD_ID |
Identifier of the lead associated with the company |
Yes |
No |
|
ORIGINATOR_ID |
Identifier of the data source. Used only for linking to external sources |
Yes |
Yes |
|
ORIGIN_ID |
Identifier of the item in the data source. Used only for linking to external sources |
Yes |
Yes |
|
ORIGIN_VERSION |
Original version. Used to protect data from accidental overwriting by an external system. If the data was imported and not changed in the external system, such data can be edited in CRM without fear that the next export will overwrite the data |
Yes |
Yes |
|
UTM_SOURCE |
Advertising system (Google-Adwords, etc.) |
Yes |
Yes |
|
UTM_MEDIUM |
Type of traffic: CPC (ads), CPM (banners) |
Yes |
Yes |
|
UTM_CAMPAIGN |
Designation of the advertising campaign |
Yes |
Yes |
|
UTM_CONTENT |
Content of the campaign. For example, for contextual ads |
Yes |
Yes |
|
UTM_TERM |
Search condition of the campaign. For example, keywords for contextual advertising |
Yes |
Yes |
|
PARENT_ID_xxx |
Relationship fields. If there are SPAs related to contacts on the account, for each such SPA there is a field that stores the relationship between this SPA and the contact. The field itself stores the identifier of the item of that SPA. For example, the field |
Yes |
Yes |
|
LAST_ACTIVITY_TIME |
Time of the last activity. |
Yes |
No |
|
LAST_ACTIVITY_BY |
Identifier of the user responsible for the last activity in this lead (for example, who created a new deal in the lead) |
Yes |
No |
|
PHONE |
Phone of the company. Multiple |
Yes |
Yes |
|
EMAIL |
E-mail address. Multiple |
Yes |
Yes |
|
WEB |
URLs of the company. Multiple |
Yes |
Yes |
|
Messengers. Multiple |
Yes |
Yes |
|
|
LINK |
Links. Multiple. Service |
Yes |
Yes |
|
UF_CRM_xxx |
Yes |
Yes |
The field description is returned by the method crm.contact.fields
|
Name |
Description |
Read |
Write |
|
ID |
Identifier of the contact |
Yes |
No |
|
HONORIFIC |
Addressing. Values from the directory can be obtained using the method crm.status.list with the filter by |
Yes |
Yes |
|
NAME |
First name |
Yes |
Yes |
|
SECOND_NAME |
Middle name |
Yes |
Yes |
|
LAST_NAME |
Last name |
Yes |
Yes |
|
PHOTO |
Photo |
Yes |
Yes |
|
BIRTHDATE |
Date of birth |
Yes |
Yes |
|
TYPE_ID |
Type of contact. Values from the directory can be obtained using the method crm.status.list with the filter by |
Yes |
Yes |
|
SOURCE_ID |
Source. Values from the directory can be obtained using the method crm.status.list with the filter by |
Yes |
Yes |
|
SOURCE_DESCRIPTION |
Additional information about the source |
Yes |
Yes |
|
POST |
Position |
Yes |
Yes |
|
Deprecated fields Address fields in the contact are deprecated and are only used in compatibility mode. To work with the address, use requisites. |
|||
|
ADDRESS |
Address (deprecated) |
Yes |
Yes |
|
ADDRESS_2 |
Second line of the address (deprecated) |
Yes |
Yes |
|
ADDRESS_CITY |
City (deprecated) |
Yes |
Yes |
|
ADDRESS_POSTAL_CODE |
Postal code (deprecated) |
Yes |
Yes |
|
ADDRESS_REGION |
Region (deprecated) |
Yes |
Yes |
|
ADDRESS_PROVINCE |
Province (deprecated) |
Yes |
Yes |
|
ADDRESS_COUNTRY |
Country (deprecated) |
Yes |
Yes |
|
ADDRESS_COUNTRY_CODE |
Country code (deprecated) |
Yes |
Yes |
|
ADDRESS_LOC_ADDR_ID |
Identifier of the location address (deprecated) |
Yes |
Yes |
|
COMMENTS |
Comment. Supports bb-codes |
Yes |
Yes |
|
OPENED |
Available to everyone. Can take values |
Yes |
Yes |
|
EXPORT |
Participates in the export of contacts. Can take values |
Yes |
Yes |
|
HAS_PHONE |
Phone is set. Can take values |
Yes |
No |
|
HAS_EMAIL |
E-mail is set. Can take values |
Yes |
No |
|
HAS_IMOL |
Open line is set. Can take values |
Yes |
No |
|
ASSIGNED_BY_ID |
Responsible |
Yes |
Yes |
|
CREATED_BY_ID |
Who created |
Yes |
No |
|
MODIFY_BY_ID |
Who modified |
Yes |
No |
|
DATE_CREATE |
Creation date |
Yes |
No |
|
DATE_MODIFY |
Modification date |
Yes |
No |
|
COMPANY_ID |
Main company of the contact |
Yes |
Yes |
|
COMPANY_IDS |
Linking the contact to companies. Multiple. In the methods crm.contact.update and crm.contact.add, it is used to submit an array of companies. In the methods crm.contact.list and crm.contact.get, this field does not exist, and crm.contact.company.items.get should be used to get the list of companies |
Yes |
Yes |
|
LEAD_ID |
Identifier of the lead associated with the contact |
Yes |
No |
|
Fields for linking to external data sources If the contact was created by an external system, then:
|
|||
|
ORIGINATOR_ID |
Identifier of the external system that is the source of data about this contact |
Yes |
Yes |
|
ORIGIN_ID |
Identifier of the contact in the external system |
Yes |
Yes |
|
ORIGIN_VERSION |
Version of the contact data in the external system. Used to protect data from accidental overwriting by an external system. If the data was imported and not changed in the external system, such data can be edited in CRM without fear that the next export will overwrite the data. |
Yes |
Yes |
|
FACE_ID |
Link to faces from the |
Yes |
No |
|
UTM_SOURCE |
Advertising system (Google-Adwords, etc.) |
Yes |
Yes |
|
UTM_MEDIUM |
Type of traffic: CPC (ads), CPM (banners) |
Yes |
Yes |
|
UTM_CAMPAIGN |
Designation of the advertising campaign |
Yes |
Yes |
|
UTM_CONTENT |
Content of the campaign. For example, for contextual ads |
Yes |
Yes |
|
UTM_TERM |
Search condition of the campaign. For example, keywords for contextual advertising |
Yes |
Yes |
|
PARENT_ID_... |
Relationship fields. If there are SPAs related to contacts on the account, for each such SPA there is a field that stores the relationship between this SPA and the contact. The field itself stores the identifier of the item of that SPA. For example, the field |
Yes |
Yes |
|
LAST_ACTIVITY_TIME |
Date of the last activity in the timeline |
Yes |
No |
|
LAST_ACTIVITY_BY |
Author of the last activity in the timeline |
Yes |
No |
|
PHONE |
Phones. Multiple |
Yes |
Yes |
|
EMAIL |
E-mail. Multiple |
Yes |
Yes |
|
WEB |
Websites. Multiple |
Yes |
Yes |
|
Messengers. Multiple |
Yes |
Yes |
|
|
LINK |
Links. Multiple. Service |
Yes |
Yes |
|
UF_CRM_xxx |
User-defined fields. For example, Depending on the portal settings, contacts may have a set of user-defined fields of specific types. A user-defined field can be added to a contact using the method crm.contact.userfield.add |
General Requisites
The field description is returned by the method crm.requisite.fields
|
Name |
Description |
Read |
Write |
|
ID |
Identifier of the requisite. Can be obtained using the method crm.requisite.list. Created automatically and unique within the portal |
Yes |
No |
|
ENTITY_TYPE_ID |
Identifier of the parent entity type. Currently, this can only be:
Identifiers of all CRM entity types are returned by the method crm.enum.ownertype |
Yes |
Yes |
|
ENTITY_ID |
Identifier of the parent entity (contact or company). The identifier can be obtained using the method crm.company.list for a company and the method crm.contact.list for a contact |
Yes |
Yes |
|
PRESET_ID |
Identifier of the requisites template. Template identifiers can be obtained using the method crm.requisite.preset.list |
Yes |
Yes |
|
DATE_CREATE |
Creation date |
Yes |
No |
|
DATE_MODIFY |
Modification date |
Yes |
No |
|
CREATED_BY_ID |
Identifier of the user who created the requisite |
Yes |
No |
|
MODIFY_BY_ID |
Identifier of the user who modified the requisite |
Yes |
No |
|
NAME |
Name of the requisite |
Yes |
Yes |
|
CODE |
Symbolic code of the requisite |
Yes |
Yes |
|
XML_ID |
External key, used for exchange operations. Identifier of the object in the external information database. The purpose of the field may change by the end developer |
Yes |
Yes |
|
ORIGINATOR_ID |
Identifier of the external information database. The purpose of the field may change by the end developer |
Yes |
Yes |
|
ACTIVE |
Activity indicator. Values Currently, the field does not actually affect anything |
Yes |
Yes |
|
ADDRESS_ONLY |
Indicator of the state when the requisite is used only for storing the address. Values |
Yes |
Yes |
|
SORT |
Sorting. Order in the list of entity requisites when there are multiple |
Yes |
Yes |
|
RQ_NAME |
Full name |
Yes |
Yes |
|
RQ_FIRST_NAME |
First name |
Yes |
Yes |
|
RQ_LAST_NAME |
Last name |
Yes |
Yes |
|
RQ_SECOND_NAME |
Middle name |
Yes |
Yes |
|
RQ_COMPANY_ID |
Identifier of the organization |
Yes |
Yes |
|
RQ_COMPANY_NAME |
Short name of the organization |
Yes |
Yes |
|
RQ_COMPANY_FULL_NAME |
Full name of the organization |
Yes |
Yes |
|
RQ_COMPANY_REG_DATE |
Date of state registration |
Yes |
Yes |
|
RQ_DIRECTOR |
General director |
Yes |
Yes |
|
RQ_ACCOUNTANT |
Chief accountant |
Yes |
Yes |
|
RQ_CEO_NAME |
Full name of the first leader |
Yes |
Yes |
|
RQ_CEO_WORK_POS |
Position of the first leader |
Yes |
Yes |
|
RQ_CONTACT |
Contact person |
Yes |
Yes |
|
RQ_EMAIL |
|
Yes |
Yes |
|
RQ_PHONE |
Phone |
Yes |
Yes |
|
RQ_FAX |
Fax |
Yes |
Yes |
|
RQ_IDENT_TYPE |
Method of identification |
Yes |
Yes |
|
RQ_IDENT_DOC |
Type of document |
Yes |
Yes |
|
RQ_IDENT_DOC_SER |
Series |
Yes |
Yes |
|
RQ_IDENT_DOC_NUM |
Number |
Yes |
Yes |
|
RQ_IDENT_DOC_PERS_NUM |
Personal number |
Yes |
Yes |
|
RQ_IDENT_DOC_DATE |
Date of issue |
Yes |
Yes |
|
RQ_IDENT_DOC_ISSUED_BY |
Issued by |
Yes |
Yes |
|
RQ_IDENT_DOC_DEP_CODE |
Department code |
Yes |
Yes |
|
RQ_INN |
Taxpayer identification number |
Yes |
Yes |
|
RQ_KPP |
Tax registration reason code |
Yes |
Yes |
|
RQ_USRLE |
Commercial register number (for country DE) |
Yes |
Yes |
|
RQ_IFNS |
Tax authority |
Yes |
Yes |
|
RQ_OGRN |
Primary state registration number |
Yes |
Yes |
|
RQ_OGRNIP |
Primary state registration number for individual entrepreneurs |
Yes |
Yes |
|
RQ_OKPO |
National classification of enterprises and organizations |
Yes |
Yes |
|
RQ_OKTMO |
Municipal classification of territories |
Yes |
Yes |
|
RQ_OKVED |
All-Russian classifier of economic activities |
Yes |
Yes |
|
RQ_EDRPOU |
Unified State Register of Enterprises and Organizations |
Yes |
Yes |
|
RQ_DRFO |
Taxpayer registration number |
Yes |
Yes |
|
RQ_KBE |
Classification of economic activities |
Yes |
Yes |
|
RQ_IIN |
Individual identification number |
Yes |
Yes |
|
RQ_BIN |
Business identification number |
Yes |
Yes |
|
RQ_ST_CERT_SER |
Series of the state registration certificate |
Yes |
Yes |
|
RQ_ST_CERT_NUM |
Number of the state registration certificate |
Yes |
Yes |
|
RQ_ST_CERT_DATE |
Date of the state registration certificate |
Yes |
Yes |
|
RQ_VAT_PAYER |
VAT payer (for country UA). Values |
Yes |
Yes |
|
RQ_VAT_ID |
VAT ID (identification number of the VAT payer) |
Yes |
Yes |
|
RQ_VAT_CERT_SER |
Series of the VAT certificate |
Yes |
Yes |
|
RQ_VAT_CERT_NUM |
Number of the VAT certificate |
Yes |
Yes |
|
RQ_VAT_CERT_DATE |
Date of the VAT certificate |
Yes |
Yes |
|
RQ_RESIDENCE_COUNTRY |
Country of residence |
Yes |
Yes |
|
RQ_BASE_DOC |
Basis for action |
Yes |
Yes |
|
RQ_REGON |
REGON (for country PL) |
Yes |
Yes |
|
RQ_KRS |
KRS (for country PL) |
Yes |
Yes |
|
RQ_PESEL |
PESEL (for country PL) |
Yes |
Yes |
|
RQ_LEGAL_FORM |
Legal form (for country FR) |
Yes |
Yes |
|
RQ_SIRET |
SIRET number (for country FR) |
Yes |
Yes |
|
RQ_SIREN |
SIREN number (for country FR) |
Yes |
Yes |
|
RQ_CAPITAL |
Share capital (for country FR) |
Yes |
Yes |
|
RQ_RCS |
RCS (for country FR) |
Yes |
Yes |
|
RQ_CNPJ |
CNPJ (for country BR) |
Yes |
Yes |
|
RQ_STATE_REG |
State registration (IE) (for country BR) |
Yes |
Yes |
|
RQ_MNPL_REG |
Municipal registration (IM) (for country BR) |
Yes |
Yes |
|
RQ_CPF |
CPF (for country BR) |
Yes |
Yes |
|
UF_CRM_... |
User-defined fields. For example, Requisites may have a set of user-defined fields with types: A user-defined field can be added to requisites using the method crm.requisite.userfield.add |
Yes |
Yes |
Bank Details
The field description is returned by the method crm.requisite.bankdetail.fields
|
Name |
Description |
Read |
Write |
|
ID |
Identifier of the bank detail. Created automatically and unique within the portal |
Yes |
No |
|
ENTITY_TYPE_ID |
Identifier of the parent object type. Can only be Identifiers of object types are returned by the method crm.enum.ownertype |
Yes |
No |
|
ENTITY_ID |
Identifier of the parent object |
Yes |
Yes |
|
COUNTRY_ID |
Identifier of the country corresponding to the set of bank detail fields (see method crm.requisite.preset.countries for available values). The country code of the bank detail matches the country code in the linked requisites template, the identifier of which is specified in the field |
Yes |
Yes |
|
DATE_CREATE |
Creation date |
Yes |
No |
|
DATE_MODIFY |
Modification date |
Yes |
No |
|
CREATED_BY_ID |
Identifier of the user who created the requisite |
Yes |
No |
|
MODIFY_BY_ID |
Identifier of the user who modified the requisite |
Yes |
No |
|
NAME* |
Name of the bank detail |
Yes |
Yes |
|
CODE |
Symbolic code of the requisite |
Yes |
Yes |
|
XML_ID |
External key. Used for exchange operations. Identifier of the object in the external information database. The purpose of the field may change by the end developer. Each application ensures the uniqueness of values in this field. It is recommended to use a unique prefix to avoid collisions with other applications |
Yes |
Yes |
|
ACTIVE |
Activity indicator. Values Currently, the field does not actually affect anything |
Yes |
Yes |
|
SORT |
Sorting |
Yes |
Yes |
|
RQ_BANK_NAME |
Name of the bank |
Yes |
Yes |
|
RQ_BANK_ADDR |
Address of the bank |
Yes |
Yes |
|
RQ_BANK_CODE |
Bank code (for country BR) |
Yes |
Yes |
|
RQ_BANK_ROUTE_NUM |
Bank Routing Number |
Yes |
Yes |
|
RQ_BIK |
BIK |
Yes |
Yes |
|
RQ_CODEB |
Bank Code (for country FR) |
Yes |
Yes |
|
RQ_CODEG |
Branch Code (for country FR) |
Yes |
Yes |
|
RQ_RIB |
RIB Key (for country FR) |
Yes |
Yes |
|
RQ_MFO |
MFO |
Yes |
Yes |
|
RQ_ACC_NAME |
Bank Account Holder Name |
Yes |
Yes |
|
RQ_ACC_NUM |
Bank Account Number |
Yes |
Yes |
|
RQ_ACC_TYPE |
Account Type (for country BR) |
Yes |
Yes |
|
RQ_AGENCY_NAME |
Agency (for country BR) |
Yes |
Yes |
|
RQ_IIK |
IIK |
Yes |
Yes |
|
RQ_ACC_CURRENCY |
Currency of the account |
Yes |
Yes |
|
RQ_COR_ACC_NUM |
Correspondent account |
Yes |
Yes |
|
RQ_IBAN |
IBAN |
Yes |
Yes |
|
RQ_SWIFT |
SWIFT |
Yes |
Yes |
|
RQ_BIC |
BIC |
Yes |
Yes |
|
COMMENTS |
Comment |
Yes |
Yes |
|
ORIGINATOR_ID |
Identifier of the external information database. The purpose of the field may change by the end developer |
Yes |
Yes |
Templates of Requisites
The field description is returned by the method crm.requisite.preset.fields
|
Name |
Description |
Read |
Write |
|
ID |
Identifier of the requisite. Created automatically and unique within the portal |
Yes |
No |
|
ENTITY_TYPE_ID |
Identifier of the parent object type. Identifiers of CRM object types are returned by the method crm.enum.ownertype |
Yes |
Yes |
|
COUNTRY_ID |
Identifier of the country corresponding to the set of fields of the requisites template (for available values see method crm.requisite.preset.countries) |
Yes |
Yes |
|
DATE_CREATE |
Creation date |
Yes |
No |
|
DATE_MODIFY |
Modification date. Contains an empty string if the template has not been changed since creation |
Yes |
No |
|
CREATED_BY_ID |
Identifier of the user who created the requisite |
Yes |
No |
|
MODIFY_BY_ID |
Identifier of the user who modified the requisite |
Yes |
No |
|
NAME |
Name of the requisite |
Yes |
Yes |
|
XML_ID |
External key. Used for exchange operations. Identifier of the object in the external information database. The purpose of the field may change by the end developer. Each application ensures the uniqueness of values in this field. It is recommended to use a unique prefix to avoid collisions with other applications. Values of the form |
Yes |
Yes |
|
ACTIVE |
Activity indicator. Values |
Yes |
Yes |
|
SORT |
Sorting |
Yes |
Yes |
Fields of Requisites Templates
The field description is returned by the method crm.requisite.preset.field.fields
|
Name |
Description |
Read |
Write |
|
ID |
Identifier of the field. Created automatically and unique within the template |
Yes |
No |
|
FIELD_NAME |
Name of the field |
Yes |
Yes |
|
FIELD_TITLE |
Alternative name of the field for the requisite. The alternative name is displayed in various forms for filling requisites. Depending on the specific form, the alternative name may or may not be used |
Yes |
Yes |
|
SORT |
Sorting. Order in the list of template fields |
Yes |
Yes |
|
IN_SHORT_LIST |
Show in the short list. Deprecated field, currently not used. Kept for backward compatibility. Can take values |
Yes |
Yes |
Addresses of Requisites
The field description is returned by the method crm.address.fields
|
Name |
Description |
Read |
Write |
|
TYPE_ID |
Identifier of the address type. Element of the enumeration "Address Type". Elements of the enumeration "Address Type" can be obtained using the method crm.enum.addresstype |
Yes |
Yes |
|
ENTITY_TYPE_ID |
Identifier of the parent object type. Identifiers of object types can be obtained using the method crm.enum.ownertype. Addresses can only be linked to Requisites (and requisites to companies or contacts) or Leads. For backward compatibility, the ability to link Addresses to Contacts or Companies has been left. However, this link is only possible on some old portals where the old address handling mode was specifically enabled by technical support. |
Yes |
Yes |
|
ENTITY_ID |
Identifier of the parent object |
Yes |
Yes |
|
ADDRESS_1 |
Street, house, building |
Yes |
Yes |
|
ADDRESS_2 |
Apartment / office |
Yes |
Yes |
|
CITY |
City |
Yes |
Yes |
|
POSTAL_CODE |
Postal code |
Yes |
Yes |
|
REGION |
Region |
Yes |
Yes |
|
PROVINCE |
Province |
Yes |
Yes |
|
COUNTRY |
Country |
Yes |
Yes |
|
COUNTRY_CODE |
Country code |
Yes |
Yes |
|
LOC_ADDR_ID |
Identifier of the location address. This field contains the identifier of the address object in the If the identifier of the If at least one string field was specified, then only the specified fields will be saved in the CRM address, and their values will overwrite the corresponding values in the location address object. The same behavior will occur when updating the address |
Yes |
Yes |
|
ANCHOR_TYPE_ID |
Identifier of the type of the main parent object. This field is for service use. The value is automatically filled when adding an address. Identifiers of object types can be obtained using the method crm.enum.ownertype. This field contains the identifier of the type of the parent requisite object (company or contact) if the address is linked to the requisite. If the address is linked to a lead, then this value will be the identifier of the lead |
Yes |
No |
|
ANCHOR_ID |
This field is for service use. The value is automatically filled when adding an address. This field contains the identifier of the parent requisite object (company or contact) if the address is linked to the requisite. If the address is linked to a lead, then this value will be the identifier of the lead |
Yes |
No |
The field description is returned by the method crm.activity.fields
|
Name |
Description |
Read |
Write |
|
ID |
Identifier of the activity |
Yes |
No |
|
OWNER_ID |
Identifier of the owner, immutable |
Yes |
Yes |
|
OWNER_TYPE_ID |
Type of owner, immutable |
Yes |
Yes |
|
TYPE_ID |
Type, immutable |
Yes |
Yes |
|
PROVIDER_ID |
Identifier of the provider |
Yes |
Yes |
|
PROVIDER_TYPE_ID |
Identifier of the provider type |
Yes |
Yes |
|
PROVIDER_GROUP_ID |
Type of connector |
Yes |
Yes |
|
ASSOCIATED_ENTITY_ID |
Identifier of the entity associated with the activity |
Yes |
No |
|
SUBJECT |
Subject, title of the activity |
Yes |
Yes |
|
START_TIME |
Start time of execution |
Yes |
Yes |
|
END_TIME |
End time |
Yes |
Yes |
|
DEADLINE |
Deadline. The field is not set directly; the value is taken from |
Yes |
Yes |
|
COMPLETED |
Completed |
Yes |
Yes |
|
STATUS |
Status |
Yes |
Yes |
|
RESPONSIBLE_ID |
Responsible |
Yes |
Yes |
|
PRIORITY |
Importance |
Yes |
Yes |
|
NOTIFY_TYPE |
Type of notifications |
Yes |
Yes |
|
NOTIFY_VALUE |
Notification parameter |
Yes |
Yes |
|
DESCRIPTION |
Description |
Yes |
Yes |
|
DESCRIPTION_TYPE |
Type of description |
Yes |
Yes |
|
DIRECTION |
Direction of the activity: incoming/outgoing. Relevant for calls and emails, not used for meetings |
Yes |
Yes |
|
LOCATION |
Location |
Yes |
Yes |
|
CREATED |
Creation date |
Yes |
No |
|
AUTHOR_ID |
Creator of the activity |
Yes |
Yes |
|
LAST_UPDATED |
Date of the last update |
Yes |
No |
|
EDITOR_ID |
Who modified |
Yes |
No |
|
SETTINGS |
Settings |
Yes |
Yes |
|
ORIGIN_ID |
Identifier of the item in the data source. Used only for linking to external sources |
Yes |
Yes |
|
ORIGINATOR_ID |
Identifier of the data source. Used only for linking to external sources |
Yes |
Yes |
|
RESULT_STATUS |
Unused field, remains for compatibility |
Yes |
Yes |
|
RESULT_STREAM |
Report statistics |
Yes |
Yes |
|
RESULT_SOURCE_ID |
Unused field, remains for compatibility |
Yes |
Yes |
|
PROVIDER_PARAMS |
Provider parameters |
Yes |
Yes |
|
PROVIDER_DATA |
Provider data |
Yes |
Yes |
|
RESULT_MARK |
Unused field, remains for compatibility |
Yes |
Yes |
|
RESULT_VALUE |
Unused field, remains for compatibility |
Yes |
Yes |
|
RESULT_SUM |
Unused field, remains for compatibility |
Yes |
Yes |
|
RESULT_CURRENCY_ID |
Unused field, remains for compatibility |
Yes |
Yes |
|
AUTOCOMPLETE_RULE |
Autocomplete |
Yes |
Yes |
|
BINDINGS |
Bindings |
Yes |
No |
|
COMMUNICATIONS |
Communication channel. Multiple, required |
Yes |
Yes |
|
FILES |
Added files. Multiple |
Yes |
Yes |
|
WEBDAV_ELEMENTS |
Added files. Multiple. Deprecated, kept for compatibility |
Yes |
Yes |
|
IS_INCOMING_CHANNEL |
Is the activity incoming, that is, created as a result of an incoming client request in the communication channel |
Yes |
No |