Register a New User Field Type userfieldtype.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:
depending on the placementWho can execute the method: any user
The method userfieldtype.add registers a new type of user fields. After registering the type, create a user field using the userfieldconfig.add method.
When opening a card with a user type field, an array PLACEMENT_OPTIONS containing data about the field and entity is passed to the application handler.
{
"MODE": "view",
"ENTITY_ID": "CRM_DEAL",
"FIELD_NAME": "UF_CRM_TEST_TYPE_1",
"ENTITY_VALUE_ID": "7303",
"VALUE": null,
"MULTIPLE": "N",
"MANDATORY": "N",
"XML_ID": null,
"ENTITY_DATA": {
"entityTypeId": 2,
"entityId": "7303",
"module": "crm"
}
}
Method Parameters
Required parameters are marked with *
|
Name |
Description |
Restrictions |
|
USER_TYPE_ID* |
String code of the type |
|
|
HANDLER* |
Address of the user type handler |
|
|
TITLE |
Text title of the type. Will be displayed in the administrative interface for user field settings |
|
|
DESCRIPTION |
Text description of the type. Will be displayed in the administrative interface for user field settings |
|
|
OPTIONS |
Additional settings. Currently, one key is available: |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"USER_TYPE_ID": "test_type",
"HANDLER": "https://www.myapplication.com/handler/",
"TITLE": "Updated test type",
"DESCRIPTION": "Test userfield type for documentation with updated description",
"OPTIONS": {
"height": 60
}
}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/userfieldtype.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"USER_TYPE_ID": "test_type",
"HANDLER": "https://www.myapplication.com/handler/",
"TITLE": "Updated test type",
"DESCRIPTION": "Test userfield type for documentation with updated description",
"OPTIONS": {
"height": 60
},
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/userfieldtype.add
try
{
const response = await $b24.callMethod(
'userfieldtype.add',
{
USER_TYPE_ID: 'test_type',
HANDLER: 'https://www.myapplication.com/handler/',
TITLE: 'Updated test type',
DESCRIPTION: 'Test userfield type for documentation with updated description',
OPTIONS: {
height: 60,
},
}
);
const result = response.getData().result;
console.log(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'userfieldtype.add',
[
'USER_TYPE_ID' => 'test_type',
'HANDLER' => 'https://www.myapplication.com/handler/',
'TITLE' => 'Updated test type',
'DESCRIPTION' => 'Test userfield type for documentation with updated description',
'OPTIONS' => [
'height' => 60,
],
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
} else {
echo 'Success: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error adding user field type: ' . $e->getMessage();
}
BX24.callMethod(
'userfieldtype.add',
{
USER_TYPE_ID: 'test_type',
HANDLER: 'https://www.myapplication.com/handler/',
TITLE: 'Updated test type',
DESCRIPTION: 'Test userfield type for documentation with updated description',
OPTIONS: {
height: 60,
},
},
function(result)
{
if(result.error())
console.error(result.error());
else
console.log(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'userfieldtype.add',
[
'USER_TYPE_ID' => 'test_type',
'HANDLER' => 'https://www.myapplication.com/handler/',
'TITLE' => 'Updated test type',
'DESCRIPTION' => 'Test userfield type for documentation with updated description',
'OPTIONS' => [
'height' => 60
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result":true,
"time":{
"start":1724421710.397825,
"finish":1724421711.040353,
"duration":0.6425280570983887,
"processing":5.888938903808594e-5,
"date_start":"2024-08-23T16:01:50+02:00",
"date_finish":"2024-08-23T16:01:51+02:00","operating":0
}
}
Returned Data
|
Name |
Description |
|
result |
Result of registering the new user field type |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400
{
"error":"ERROR_CORE",
"error_description":"Unable to set placement handler: Handler already binded"
}
|
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 Error Codes
|
Code |
Error Message |
Description |
|
|
Unable to set placement handler: Handler already binded |
|
|
|
Argument 'USER_TYPE_ID' is null or empty |
|
|
|
Argument 'HANDLER' is null or empty |
|
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
- Change settings for user field type userfieldtype.update
- Get a list of registered user field types userfieldtype.list
- Delete Registered User Field Type userfieldtype.delete
- Add Custom Field userfieldconfig.add
- Custom Field Types in CRM