Get a List of User Field Settings userfieldconfig.list
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:
userfieldconfig, module scope frommoduleId(for example,crm)Who can execute the method: a user with read access permission to the object that owns the fields in the
moduleId
The method userfieldconfig.list returns a list of user field settings based on the filter.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
moduleId* |
The identifier of the module in which the fields are being searched |
|
select |
Set of fields to return (detailed description) |
|
order |
Object format:
Available fields for sorting:
By default:
|
|
filter |
Object format:
All conditions for individual fields are combined using |
|
start |
Offset for pagination. Use the |
Select Parameter
|
Name |
Description |
|
* |
Return all standard settings fields |
|
language |
Language identifier for language fields, for example |
|
id |
Identifier of the field setting |
|
entityId |
Identifier of the object |
|
fieldName |
Code of the field |
|
userTypeId |
Type of the field |
|
xmlId |
External identifier |
|
sort |
Sort index |
|
multiple |
Whether the user field is multiple. Possible values: |
|
mandatory |
Whether the user field is mandatory. Possible values: |
|
showFilter |
Whether to show the field in the list filter. Possible values: |
|
showInList |
Whether to show the field in the list. Possible values: |
|
editInList |
Whether to allow editing the value in the list. Possible values: |
|
isSearchable |
Whether the field values are searchable. Possible values: |
|
settings |
Additional settings for the field |
|
languageId |
Language identifier. When this parameter is passed, a set of language fields in the selected language is returned:
|
Filterable Fields
|
Name |
Description |
|
id |
Identifier of the user field |
|
fieldName |
Code of the user field |
|
userTypeId |
Type of the user field |
|
xmlId |
External code |
|
sort |
Sort index |
|
multiple |
Whether the user field is multiple. Possible values: |
|
mandatory |
Whether the user field is mandatory. Possible values: |
|
showFilter |
Whether to show in the list filter. Possible values: |
|
showInList |
Whether to show in the list. Possible values: |
|
editInList |
Whether to allow user editing. Possible values: |
|
isSearchable |
Whether the field values are searchable. Possible values: |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"moduleId":"crm","select":{"0":"*","language":"de"},"order":{"id":"DESC"},"filter":{"multiple":"Y"},"start":0}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/userfieldconfig.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"moduleId":"crm","select":{"0":"*","language":"de"},"order":{"id":"DESC"},"filter":{"multiple":"Y"},"start":0,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/userfieldconfig.list
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
type UserFieldConfig = {
id: string
fieldName: string
userTypeId: string
}
// Shape of the payload returned in result (match the "response handling" section of the page)
type UserFieldConfigListResult = {
fields: UserFieldConfig[]
}
// userfieldconfig.list returns a single page (max 50 records). For the whole result set
// use a list helper: $b24.actions.v2.callList.make() returns every record as one
// array, $b24.actions.v2.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `start` variant when sort matters.
try {
const response = await $b24.actions.v2.call.make<UserFieldConfigListResult>({
method: 'userfieldconfig.list',
params: {
moduleId: 'crm',
select: ['*'],
order: {
id: 'DESC',
},
filter: {
multiple: 'Y',
},
start: 0,
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info(`Loaded ${result.fields.length} field config(s) on this page`)
console.info(result.fields)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function listUserFieldConfigs() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
// userfieldconfig.list returns a single page (max 50 records). For the whole result set
// use a list helper: $b24.actions.v2.callList.make() returns every record as one
// array, $b24.actions.v2.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `start` variant when sort matters.
const response = await $b24.actions.v2.call.make({
method: 'userfieldconfig.list',
params: {
moduleId: 'crm',
select: ['*'],
order: {
id: 'DESC',
},
filter: {
multiple: 'Y',
},
start: 0,
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info(`Loaded ${result.fields.length} field config(s) on this page`)
console.info(result.fields)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', listUserFieldConfigs)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.userfieldconfig.list(
module_id="crm",
select={
0: "*",
"language": "ru",
},
order={
"id": "DESC",
},
filter={
"multiple": "Y",
},
start=0,
).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}")
try {
$response = $b24Service
->core
->call(
'userfieldconfig.list',
[
'moduleId' => 'crm',
'select' => [
0 => '*',
'language' => 'de',
],
'order' => [
'id' => 'DESC',
],
'filter' => [
'multiple' => 'Y',
],
'start' => 0,
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Result: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error: ' . $e->getMessage();
}
BX24.callMethod(
'userfieldconfig.list',
{
moduleId: 'crm',
select: {
0: '*',
language: 'de',
},
order: {
id: 'DESC',
},
filter: {
multiple: 'Y',
},
},
(result) => {
if (result.error()) {
console.error(result.error());
return;
}
console.info(result.data());
if (result.more()) {
result.next();
}
},
);
require_once('crest.php');
$result = CRest::call(
'userfieldconfig.list',
[
'moduleId' => 'crm',
'select' => [
0 => '*',
'language' => 'de',
],
'order' => [
'id' => 'DESC',
],
'filter' => [
'multiple' => 'Y',
],
'start' => 0,
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "userfieldconfig.list", b24.Params{
"moduleId": "crm",
"select": b24.Params{
"0": "*",
"language": "ru",
},
"order": b24.Params{
"id": "DESC",
},
"filter": b24.Params{
"multiple": "Y",
},
"start": 0,
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("userfieldconfig.list: %w", err)
}
// The method wraps the response in an object with the "fields" key.
raw, ok := b24.Unwrap(res.Result, "fields")
if !ok {
return fmt.Errorf("no fields key in the response")
}
var items []struct {
ID b24.ID `json:"id"`
EntityID string `json:"entityId"`
FieldName string `json:"fieldName"`
UserTypeID string `json:"userTypeId"`
Sort string `json:"sort"`
Multiple string `json:"multiple"`
}
if err := json.Unmarshal(raw, &items); err != nil {
return fmt.Errorf("parse response: %w", err)
}
for _, it := range items {
fmt.Println(it.ID)
}
Response Handling
HTTP Status: 200
{
"result": {
"fields": [
{
"id": "7095",
"entityId": "CRM_7",
"fieldName": "UF_CRM_7_NEW_REST_LIST_2026",
"userTypeId": "enumeration",
"xmlId": null,
"sort": "100",
"multiple": "Y",
"mandatory": "N",
"showFilter": "N",
"showInList": "Y",
"editInList": "Y",
"isSearchable": "N",
"settings": {
"DISPLAY": "LIST",
"LIST_HEIGHT": 1,
"CAPTION_NO_VALUE": "",
"SHOW_NO_VALUE": "Y"
},
"languageId": {
"de": "de"
},
"editFormLabel": {
"de": "List of Characteristics"
},
"listColumnLabel": null,
"listFilterLabel": null,
"errorMessage": null,
"helpMessage": null
}
]
},
"next": 50,
"total": 94,
"time": {
"start": 1724239307.903115,
"finish": 1724239308.567422,
"duration": 0.6643068790435791,
"processing": 0.20090818405151367,
"date_start": "2024-08-21T13:21:47+02:00",
"date_finish": "2024-08-21T13:21:48+02:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response (detailed description) |
|
total |
Total number of settings found |
|
next |
Offset for the next page. Field is returned if the number of found items exceeds 50 |
|
time |
Information about the execution time of the request |
Result Object
|
Name |
Description |
|
fields |
List of found user field settings (detailed description) |
Fields Object[]
|
Name |
Description |
|
id |
Identifier of the user field |
|
entityId |
Identifier of the object to which the user field belongs |
|
fieldName |
Code of the user field |
|
userTypeId |
Type of the user field |
|
xmlId |
External code |
|
sort |
Sort index |
|
multiple |
Whether the user field is multiple. Possible values: |
|
mandatory |
Whether the user field is mandatory. Possible values: |
|
showFilter |
Display mode in the filter. Possible values: |
|
showInList |
Whether to show the field in the list. Possible values: |
|
editInList |
Whether to allow editing the value in the list. Possible values: |
|
isSearchable |
Whether the field values are searchable. Possible values: |
|
settings |
Additional settings for the field. The composition of keys depends on |
|
languageId |
Language identifiers for which labels are set |
|
editFormLabel |
Labels in the edit form |
|
listColumnLabel |
Header in the list |
|
listFilterLabel |
Label of the filter in the list |
|
errorMessage |
Error message |
|
helpMessage |
Help |
|
enum |
List elements for Field may be absent for other types |
Error Handling
HTTP Status: 400
{
"error": "",
"error_description": "You do not have permission to view user field settings"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Code |
Description |
Value |
|
Empty value |
You do not have permission to view user field settings |
Insufficient read access permission for fields based on the provided filter |
|
Empty value |
The current method required more scopes. (crm) |
The application does not have the required scope for the module from |
|
Empty value |
No settings for UserFieldAccess |
Access to user fields is not configured for the provided |
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 |