Add Forum Message Custom Field forum.message.field.custom.add
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
Scope:
forumWho can execute the method: any user
The method belongs to REST 3.0. The call specifics and response format of the new API version are described in the REST 3.0 overview.
The forum.message.field.custom.add method adds a custom field for forum messages and returns its data.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fields* |
An object with the fields of the new custom field. Field description |
Parameter fields
|
Name |
Description |
|
name* |
Field code. It must start with The code must be unique among message custom fields. Codes of existing fields can be retrieved using the forum.message.field.custom.list method. The code cannot be changed after creation |
|
userTypeId* |
Field type, for example:
The type cannot be changed after creation |
|
xmlId |
External code of the field |
|
sort |
Sort order. Default: |
|
isMultiple |
Multiple field flag. Possible values:
Default: |
|
isMandatory |
Required field flag. Possible values:
Default: |
|
showFilter |
How the field is shown in the list filter. Possible values:
Default: |
|
showInList |
Whether to show the field in the list. Possible values:
Default: |
|
editInList |
Whether the field value can be edited. Possible values:
Default: |
|
isSearchable |
Whether the field values are included in search. Possible values:
Default: |
|
settings |
Field type settings. Bitrix24 does not apply the passed settings: the field is created with the default type settings. The current settings are returned in the response |
|
editFormLabel |
Field label in the edit form. Pass an object where the key is the language code and the value is the label, for example |
|
listColumnLabel |
List column label. The format is the same as for |
|
listFilterLabel |
List filter label. The format is the same as for |
|
errorMessage |
Error message shown for an invalid field value. The format is the same as for |
|
helpMessage |
Help text for the field. The format is the same as for |
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the /api/ segment to the request URL:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/forum.message.field.custom.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"name":"UF_EXTERNAL_ID","userTypeId":"string","xmlId":"EXTERNAL_ID","sort":200,"isMandatory":false,"isSearchable":true,"editFormLabel":{"de":"Externe ID","en":"External ID"},"helpMessage":{"de":"Nachrichtencode im externen System","en":"Message code in the external system"}}}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/forum.message.field.custom.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"name":"UF_EXTERNAL_ID","userTypeId":"string","xmlId":"EXTERNAL_ID","sort":200,"isMandatory":false,"isSearchable":true,"editFormLabel":{"de":"Externe ID","en":"External ID"},"helpMessage":{"de":"Nachrichtencode im externen System","en":"Message code in the external system"}},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/forum.message.field.custom.add
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
type CustomFieldAddResult = {
item: {
id: number
entityId: string
name: string
userTypeId: string
xmlId: string | null
sort: number
isMultiple: boolean
isMandatory: boolean
showFilter: string
showInList: boolean
editInList: boolean
isSearchable: boolean
settings: Record<string, unknown>
editFormLabel: string | null
listColumnLabel: string | null
listFilterLabel: string | null
errorMessage: string | null
helpMessage: string | null
}
}
try {
const response = await $b24.actions.v3.call.make<CustomFieldAddResult>({
method: 'forum.message.field.custom.add',
params: {
fields: {
name: 'UF_EXTERNAL_ID',
userTypeId: 'string',
xmlId: 'EXTERNAL_ID',
sort: 200,
isMandatory: false,
isSearchable: true,
editFormLabel: { de: 'Externe ID', en: 'External ID' },
helpMessage: { de: 'Nachrichtencode im externen System', en: 'Message code in the external system' },
},
},
requestId: Text.getUuidRfc4122()
})
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Custom field created:', result.item.id)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function addCustomField() {
try {
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v3.call.make({
method: 'forum.message.field.custom.add',
params: {
fields: {
name: 'UF_EXTERNAL_ID',
userTypeId: 'string',
xmlId: 'EXTERNAL_ID',
sort: 200,
isMandatory: false,
isSearchable: true,
editFormLabel: { de: 'Externe ID', en: 'External ID' },
helpMessage: { de: 'Nachrichtencode im externen System', en: 'Message code in the external system' },
},
},
requestId: B24Js.Text.getUuidRfc4122()
})
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Custom field created:', result.item.id)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', addCustomField)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.forum.message.field.custom.add(
fields={
"name": "UF_EXTERNAL_ID",
"userTypeId": "string",
"xmlId": "EXTERNAL_ID",
"sort": 200,
"isMandatory": False,
"isSearchable": True,
"editFormLabel": {"de": "Externe ID", "en": "External ID"},
"helpMessage": {"de": "Nachrichtencode im externen System", "en": "Message code in the external system"},
},
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via cURL or fetch.
try {
$response = $b24Service
->core
->call(
'forum.message.field.custom.add',
[
'fields' => [
'name' => 'UF_EXTERNAL_ID',
'userTypeId' => 'string',
'xmlId' => 'EXTERNAL_ID',
'sort' => 200,
'isMandatory' => false,
'isSearchable' => true,
'editFormLabel' => ['de' => 'Externe ID', 'en' => 'External ID'],
'helpMessage' => ['de' => 'Nachrichtencode im externen System', 'en' => 'Message code in the external system'],
],
]
);
$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: ' . $e->getMessage();
}
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via cURL or fetch.
BX24.callMethod(
'forum.message.field.custom.add',
{
fields: {
name: 'UF_EXTERNAL_ID',
userTypeId: 'string',
xmlId: 'EXTERNAL_ID',
sort: 200,
isMandatory: false,
isSearchable: true,
editFormLabel: { de: 'Externe ID', en: 'External ID' },
helpMessage: { de: 'Nachrichtencode im externen System', en: 'Message code in the external system' },
},
},
result => {
if (result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via cURL or fetch.
require_once('crest.php');
$result = CRest::call(
'forum.message.field.custom.add',
[
'fields' => [
'name' => 'UF_EXTERNAL_ID',
'userTypeId' => 'string',
'xmlId' => 'EXTERNAL_ID',
'sort' => 200,
'isMandatory' => false,
'isSearchable' => true,
'editFormLabel' => ['de' => 'Externe ID', 'en' => 'External ID'],
'helpMessage' => ['de' => 'Nachrichtencode im externen System', 'en' => 'Message code in the external system'],
],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "forum.message.field.custom.add", b24.Params{
"fields": b24.Params{
"name": "UF_EXTERNAL_ID",
"userTypeId": "string",
"xmlId": "EXTERNAL_ID",
"sort": 200,
"isMandatory": false,
"isSearchable": true,
"editFormLabel": b24.Params{"de": "Externe ID", "en": "External ID"},
"helpMessage": b24.Params{"de": "Nachrichtencode im externen System", "en": "Message code in the external system"},
},
})
if err != nil {
return fmt.Errorf("forum.message.field.custom.add: %w", err)
}
// The method wraps the response in an object with the "item" key.
raw, ok := b24.Unwrap(res.Result, "item")
if !ok {
return fmt.Errorf("no item key in the response")
}
var item struct {
ID int `json:"id"`
Name string `json:"name"`
UserTypeID string `json:"userTypeId"`
EditFormLabel *string `json:"editFormLabel"`
}
if err := json.Unmarshal(raw, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.ID, item.Name, item.UserTypeID)
Response Handling
HTTP status: 200
{
"result": {
"item": {
"id": 6008091,
"entityId": "FORUM_MESSAGE",
"name": "UF_EXTERNAL_ID",
"userTypeId": "string",
"xmlId": "EXTERNAL_ID",
"sort": 200,
"isMultiple": false,
"isMandatory": false,
"showFilter": "N",
"showInList": true,
"editInList": true,
"isSearchable": true,
"settings": {
"size": 20,
"rows": 1,
"regexp": "",
"minLength": 0,
"maxLength": 0,
"defaultValue": ""
},
"editFormLabel": "External ID",
"listColumnLabel": null,
"listFilterLabel": null,
"errorMessage": null,
"helpMessage": "Message code in the external system"
}
},
"time": {
"start": 1792670680,
"finish": 1792670680.614779,
"duration": 0.614778995513916,
"processing": 0,
"date_start": "2026-10-22T15:04:40+02:00",
"date_finish": "2026-10-22T15:04:40+02:00",
"operating_reset_at": 1792670760,
"operating": 0.23125314712524414
}
}
Returned Data
|
Name |
Description |
|
result |
An object with the response data |
|
result.item |
The created custom field. Field description |
|
time |
Information about the request execution time |
Item Object
|
Name |
Description |
|
id |
Custom field identifier |
|
entityId |
Identifier of the object the field belongs to. For forum messages, it is always |
|
name |
Field code |
|
userTypeId |
Field type |
|
xmlId |
External code of the field. |
|
sort |
Sort order |
|
isMultiple |
|
|
isMandatory |
|
|
showFilter |
How the field is shown in the list filter: |
|
showInList |
|
|
editInList |
|
|
isSearchable |
|
|
settings |
Field type settings. Keys are returned in camelCase, flags as |
|
editFormLabel |
Edit form label in the response language. |
|
listColumnLabel |
List column label in the response language. |
|
listFilterLabel |
List filter label in the response language. |
|
errorMessage |
Error message in the response language. |
|
helpMessage |
Help text in the response language. |
Error Handling
HTTP status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_ENTITYALREADYEXISTSEXCEPTION",
"message": "Record with ID UF_EXTERNAL_ID already exists."
}
}
|
Name |
Description |
|
error.code |
String error code. Use it to identify the type of exception |
|
error.message |
Text description of the error |
|
error.validation |
Array with error details. Present only in data validation errors |
|
error.validation[].field |
Name of the field where the validation error occurred |
|
error.validation[].message |
Description of the error related to the specified field |
Possible Error Codes
Field Validation Errors
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_DTOVALIDATIONEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Required field |
Pass |
|
|
Required field |
Pass |
|
|
Field value is not one of the possible values: N, I, E, S |
Pass one of the values |
Field Already Exists Error
Error Code: BITRIX_REST_V3_EXCEPTION_ENTITYALREADYEXISTSEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Record with ID |
A field with this code already exists. Specify a different |
Internal Error
HTTP status: 500
The response comes in the format of the previous API version: {"error":"INTERNAL_SERVER_ERROR","error_description":"Internal server error"}.
|
Field |
Error description |
How to Fix |
|
|
Internal server error |
Invalid field code or type. Make sure that |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 Forum Message Custom Field forum.message.field.custom.update
- Get Forum Message Custom Field forum.message.field.custom.get
- Get List of Forum Message Custom Fields forum.message.field.custom.list
- Delete Forum Message Custom Field forum.message.field.custom.delete
- Get Custom Field List Values forum.message.field.custom.enum.list
- Forum Messages: Overview of Methods
- Forum Message Custom Fields: Overview of Methods