Create a New Custom Field for crm.requisite.userfield.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
This method creates a new custom field for the requisite.
Restrictions for the Symbolic Code of the Custom Field
The system limitation for the field name is 20 characters. The custom field name always has the prefix UF_CRM_, meaning the actual length of the name is 13 characters.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fields* |
A set of fields — an object of the form |
Parameter fields
Required parameters are marked with *
|
Name |
Description |
|
ENTITY_ID* |
The identifier of the entity to which the custom field belongs. For requisites, this is always |
|
FIELD_NAME* |
Symbolic code. For requisites, it always starts with the prefix |
|
USER_TYPE_ID* |
|
|
XML_ID |
External key. Used for exchange operations. Identifier of the object in the external information base. The purpose of the field may change by the final developer |
|
SORT |
Sorting |
|
MULTIPLE |
Multiplicity indicator. Possible values:
Defaults to |
|
MANDATORY |
Mandatory indicator. Possible values:
Defaults to |
|
SHOW_FILTER |
Show in the list filter. Possible values:
Defaults to |
|
SHOW_IN_LIST |
Show in the list. Possible values:
Defaults to |
|
EDIT_IN_LIST |
Allow user editing. Possible values:
Defaults to |
|
IS_SEARCHABLE |
Are field values included in the search. Possible values:
Defaults to |
|
EDIT_FORM_LABEL |
Label in the edit form |
|
LIST_COLUMN_LABEL |
Header in the list |
|
LIST_FILTER_LABEL |
Filter label in the list |
|
ERROR_MESSAGE |
Error message |
|
HELP_MESSAGE |
Help |
|
LIST |
List elements. For detailed information, see the section Get Field Descriptions for Custom Field Type "Enumeration" (List) crm.userfield.enumeration.fields |
|
SETTINGS |
Additional settings (dependent on type). For detailed information, see the section Get Field Settings Description for Custom Field Type crm.userfield.settings.fields |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"USER_TYPE_ID":"string","ENTITY_ID":"CRM_REQUISITE","SORT":100,"MULTIPLE":"N","MANDATORY":"N","SHOW_FILTER":"E","SHOW_IN_LIST":"Y","EDIT_FORM_LABEL":"PP - String","LIST_COLUMN_LABEL":"PP - String","LIST_FILTER_LABEL":"PP - String","FIELD_NAME":"NEWTECH_v1_STRING"}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.requisite.userfield.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"USER_TYPE_ID":"string","ENTITY_ID":"CRM_REQUISITE","SORT":100,"MULTIPLE":"N","MANDATORY":"N","SHOW_FILTER":"E","SHOW_IN_LIST":"Y","EDIT_FORM_LABEL":"PP - String","LIST_COLUMN_LABEL":"PP - String","LIST_FILTER_LABEL":"PP - String","FIELD_NAME":"NEWTECH_v1_STRING"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.requisite.userfield.add
try
{
const response = await $b24.callMethod(
"crm.requisite.userfield.add",
{
fields:
{
"USER_TYPE_ID": "string",
"ENTITY_ID": "CRM_REQUISITE",
"SORT": 100,
"MULTIPLE": "N",
"MANDATORY": "N",
"SHOW_FILTER": "E",
"SHOW_IN_LIST": "Y",
"EDIT_FORM_LABEL": "PP - String",
"LIST_COLUMN_LABEL": "PP - String",
"LIST_FILTER_LABEL": "PP - String",
"FIELD_NAME": "NEWTECH_v1_STRING"
}
}
);
const result = response.getData().result;
console.dir(result);
}
catch(error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'crm.requisite.userfield.add',
[
'fields' => [
'USER_TYPE_ID' => 'string',
'ENTITY_ID' => 'CRM_REQUISITE',
'SORT' => 100,
'MULTIPLE' => 'N',
'MANDATORY' => 'N',
'SHOW_FILTER' => 'E',
'SHOW_IN_LIST' => 'Y',
'EDIT_FORM_LABEL' => 'PP - String',
'LIST_COLUMN_LABEL' => 'PP - String',
'LIST_FILTER_LABEL' => 'PP - String',
'FIELD_NAME' => 'NEWTECH_v1_STRING',
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error adding user field: ' . $e->getMessage();
}
BX24.callMethod(
"crm.requisite.userfield.add",
{
fields:
{
"USER_TYPE_ID": "string",
"ENTITY_ID": "CRM_REQUISITE",
"SORT": 100,
"MULTIPLE": "N",
"MANDATORY": "N",
"SHOW_FILTER": "E",
"SHOW_IN_LIST": "Y",
"EDIT_FORM_LABEL": "PP - String",
"LIST_COLUMN_LABEL": "PP - String",
"LIST_FILTER_LABEL": "PP - String",
"FIELD_NAME": "NEWTECH_v1_STRING"
}
},
function(result)
{
if(result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'crm.requisite.userfield.add',
[
'fields' => [
'USER_TYPE_ID' => 'string',
'ENTITY_ID' => 'CRM_REQUISITE',
'SORT' => 100,
'MULTIPLE' => 'N',
'MANDATORY' => 'N',
'SHOW_FILTER' => 'E',
'SHOW_IN_LIST' => 'Y',
'EDIT_FORM_LABEL' => 'PP - String',
'LIST_COLUMN_LABEL' => 'PP - String',
'LIST_FILTER_LABEL' => 'PP - String',
'FIELD_NAME' => 'NEWTECH_v1_STRING'
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": 235,
"time": {
"start": 1717681176.885836,
"finish": 1717681177.353738,
"duration": 0.46790218353271484,
"processing": 0.084564208984375,
"date_start": "2024-06-06T15:39:36+02:00",
"date_finish": "2024-06-06T15:39:37+02:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Identifier of the created custom field |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 40x, 50x
{
"error": "ERROR_CORE",
"error_description": "Field UF_CRM_NEWTECH_V1_STRING for object CRM_REQUISITE already exists."
}
|
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 |
|
|
|
Attempt to recreate a custom field with the same symbolic code |
|
Empty string |
|
Data type for the custom field is not specified |
|
Empty string |
|
Symbolic code for the custom field is not specified |
|
Empty string |
|
Insufficient access permissions to add a custom field |
|
|
|
Failed to create a custom field |
|
|
|
Failed to save values for the custom list-type field (e.g., when there is a duplication of the external key of one of the values) |
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
- Update Custom Field of CRM Requisite
- Get User Field by ID crm.requisite.userfield.get
- Get a list of custom fields of the requisite by filter crm.requisite.userfield.list
- Delete User Field of Requisite crm.requisite.userfield.delete