Get a list of custom fields user.userfield.list
Scope:
user.userfieldWho can execute the method: administrator
The method user.userfield.list retrieves a list of custom fields based on the filter.
Method Parameters
|
Name |
Description |
|
Sorting of the selected custom fields in the format Possible values for
Possible values for
|
|
|
filter |
Filter for the selected custom fields in the format Possible values for An additional prefix can be assigned to the key to clarify the filter behavior. Possible prefix values:
|
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"order":{"id":"desc"},"filter":{"id":13}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/user.userfield.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"order":{"id":"desc"},"filter":{"id":13},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/user.userfield.list
// callListMethod: Retrieves all data at once. Use only for small selections (< 1000 items) due to high memory usage.
try {
const response = await $b24.callListMethod(
'user.userfield.list',
{
order: {
id: 'desc',
},
filter: {
id: 13
},
},
(progress) => { console.log('Progress:', progress) }
)
const items = response.getData() || []
for (const entity of items) { console.log('Entity:', entity) }
} catch (error) {
console.error('Request failed', error)
}
// fetchListMethod: Retrieves data in parts using an iterator. Use it for large data volumes to optimize memory usage.
try {
const generator = $b24.fetchListMethod('user.userfield.list', {
order: {
id: 'desc',
},
filter: {
id: 13
},
}, 'ID')
for await (const page of generator) {
for (const entity of page) { console.log('Entity:', entity) }
}
} catch (error) {
console.error('Request failed', error)
}
// callMethod: Manually controls pagination through the start parameter. Use it for precise control of request batches. For large datasets, it is less efficient than fetchListMethod.
try {
const response = await $b24.callMethod('user.userfield.list', {
order: {
id: 'desc',
},
filter: {
id: 13
},
}, 0)
const result = response.getData().result || []
for (const entity of result) { console.log('Entity:', entity) }
} catch (error) {
console.error('Request failed', error)
}
try {
$response = $b24Service
->core
->call(
'user.userfield.list',
[
'order' => [
'id' => 'desc',
],
'filter' => [
'id' => 13
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// Your logic for processing data
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error fetching user fields: ' . $e->getMessage();
}
BX24.callMethod(
"user.userfield.list",
{
order: {
id: 'desc',
},
filter: {
id: 13
},
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'user.userfield.list',
[
'order' => [
'id' => 'desc',
],
'filter' => [
'id' => 13,
],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result":[
{
"ID":"176",
"ENTITY_ID":"USER",
"FIELD_NAME":"UF_USR_1724228142162",
"USER_TYPE_ID":"enumeration",
"XML_ID":null,
"SORT":"100",
"MULTIPLE":"Y",
"MANDATORY":"N",
"SHOW_FILTER":"E",
"SHOW_IN_LIST":"Y",
"EDIT_IN_LIST":"Y",
"IS_SEARCHABLE":"N",
"SETTINGS": {
"DISPLAY":"UI",
"LIST_HEIGHT":1,
"CAPTION_NO_VALUE":"",
"SHOW_NO_VALUE":"Y"
},
"LIST":[
{
"ID":"26",
"SORT":"0",
"VALUE":"1",
"DEF":"N",
"XML_ID":"2a53ce08b86a6aba152b1b19204fdef2"
},
{
"ID":"27",
"SORT":"100",
"VALUE":"2",
"DEF":"N",
"XML_ID":"292df2be1171ed6ab038996deac29ac8"
},
{
"ID":"28",
"SORT":"200",
"VALUE":"3",
"DEF":"N",
"XML_ID":"3c5af70eafbba79a6cf52e299ed75123"
}
]
},
{
"ID":"177",
"ENTITY_ID":"USER",
"FIELD_NAME":"UF_USR_MONEY",
"USER_TYPE_ID":"money",
"XML_ID":null,
"SORT":"100",
"MULTIPLE":"N",
"MANDATORY":"N",
"SHOW_FILTER":"N",
"SHOW_IN_LIST":"Y",
"EDIT_IN_LIST":"Y",
"IS_SEARCHABLE":"N",
"SETTINGS": {
"DEFAULT_VALUE":""
}
}
],
"total":2,
"time": {
"start":1747313326.788124,
"finish":1747313328.641663,
"duration":1.853538990020752,
"processing":0.011211156845092773,
"date_start":"2025-05-15T14:48:46+02:00",
"date_finish":"2025-05-15T14:48:48+02:00",
"operating":0
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response |
|
total |
Total number of records found |
|
time |
Information about the execution time of the request |
Error Handling
HTTP status: 400
{
"error":"",
"error_description":"Access denied."
}
|
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 |
Description |
Value |
|
Empty string |
Access denied. |
A field with such |
|
Empty string |
ID is not defined or invalid |
|
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Add Custom Field user.userfield.add
- Update User Field user.userfield.update
- Delete User Field user.userfield.delete