Get Field Parameters or List of Fields lists.field.get
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:
listsWho can execute the method: a user with "Read" access permission for the required list
The method lists.field.get returns data about a field or a list of fields.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
IBLOCK_TYPE_ID* |
Information block type ID. Standard types:
In the on-premise version, you can also specify the ID of any existing custom information block type. The identifier can be obtained using the method lists.get.iblock.type.id |
|
IBLOCK_ID* |
Identifier of the information block. The identifier can be obtained using the method lists.get |
|
IBLOCK_CODE* |
Symbolic code of the information block. The code can be obtained using the method lists.get At least one of the parameters must be specified: |
|
FIELD_ID |
Identifier of the field. For a custom field, it appears as If not specified, all fields of the list are returned |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"IBLOCK_TYPE_ID":"lists","IBLOCK_ID":"123","FIELD_ID":"PROPERTY_1151"}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/lists.field.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"IBLOCK_TYPE_ID":"lists","IBLOCK_ID":"123","FIELD_ID":"PROPERTY_1151","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/lists.field.get
// 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
// Shape of the payload returned in result (match the "response handling" section of the page)
type FieldsGetResult = Record<string, FieldItem>
type FieldItem = {
FIELD_ID: string
SORT: number
NAME: string
IS_REQUIRED: string
MULTIPLE: string
DEFAULT_VALUE: string
TYPE: string
PROPERTY_TYPE: string
PROPERTY_USER_TYPE: boolean | null
CODE: string
ID: string
LINK_IBLOCK_ID: string | null
ROW_COUNT: string
COL_COUNT: string
USER_TYPE_SETTINGS: unknown | null
SETTINGS: Record<string, string>
DISPLAY_VALUES_FORM: Record<string, string>
}
try {
const response = await $b24.actions.v2.call.make<FieldsGetResult>({
method: 'lists.field.get',
params: {
IBLOCK_TYPE_ID: 'lists',
IBLOCK_ID: '123',
FIELD_ID: 'PROPERTY_1151',
},
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(Object.keys(result).map(key => `${key}: ${result[key].NAME}`))
}
} 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 fetchFieldData() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'lists.field.get',
params: {
IBLOCK_TYPE_ID: 'lists',
IBLOCK_ID: '123',
FIELD_ID: 'PROPERTY_1151',
},
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(Object.keys(result).map(key => `${key}: ${result[key].NAME}`))
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', fetchFieldData)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.lists.field.get(
iblock_type_id="lists",
iblock_id=123,
field_id="PROPERTY_1151",
).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(
'lists.field.get',
[
'IBLOCK_TYPE_ID' => 'lists',
'IBLOCK_ID' => '123',
'FIELD_ID' => 'PROPERTY_1151'
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error fetching field: ' . $e->getMessage();
}
BX24.callMethod(
'lists.field.get',
{
'IBLOCK_TYPE_ID': 'lists',
'IBLOCK_ID': '123',
'FIELD_ID': 'PROPERTY_1151'
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'lists.field.get',
[
'IBLOCK_TYPE_ID' => 'lists',
'IBLOCK_ID' => '123',
'FIELD_ID' => 'PROPERTY_1151'
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "lists.field.get", b24.Params{
"IBLOCK_TYPE_ID": "lists",
"IBLOCK_ID": "123",
"FIELD_ID": "PROPERTY_1151",
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("lists.field.get: %w", err)
}
// The method wraps the response in an object with the "L" key.
raw, ok := b24.Unwrap(res.Result, "L")
if !ok {
return fmt.Errorf("no L key in the response")
}
var item struct {
FieldID string `json:"FIELD_ID"`
Sort int `json:"SORT"`
Name string `json:"NAME"`
IsRequired string `json:"IS_REQUIRED"`
Multiple string `json:"MULTIPLE"`
DefaultValue string `json:"DEFAULT_VALUE"`
}
if err := json.Unmarshal(raw, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.FieldID, item.Sort)
Response Handling
HTTP Status: 200
{
"result": {
"L": {
"FIELD_ID": "PROPERTY_1151",
"SORT": 50,
"NAME": "Task Status",
"IS_REQUIRED": "N",
"MULTIPLE": "N",
"DEFAULT_VALUE": "1685",
"TYPE": "L",
"PROPERTY_TYPE": "L",
"PROPERTY_USER_TYPE": false,
"CODE": "PROJECT",
"ID": "1151",
"LINK_IBLOCK_ID": null,
"ROW_COUNT": "1",
"COL_COUNT": "30",
"USER_TYPE_SETTINGS": null,
"SETTINGS": {
"SHOW_ADD_FORM": "Y",
"SHOW_EDIT_FORM": "Y",
"ADD_READ_ONLY_FIELD": "N",
"EDIT_READ_ONLY_FIELD": "Y",
"SHOW_FIELD_PREVIEW": "N"
},
"DISPLAY_VALUES_FORM": {
"1669": "Planning",
"1671": "In Active Work",
"1673": "Testing",
"1675": "Completed",
"1677": "Deferred",
"1679": "Archive"
}
}
},
"time": {
"start": 1765375929,
"finish": 1765375929.696936,
"duration": 0.6969358921051025,
"processing": 0,
"date_start": "2025-12-10T12:12:09+01:00",
"date_finish": "2025-12-10T12:12:09+01:00",
"operating_reset_at": 1765376529,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Data of the field or an array of fields. An empty array means that there are no fields in the list with the specified |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400
{
"error":"ERROR_REQUIRED_PARAMETERS_MISSING",
"error_description":"Required parameter `X` is missing"
}
|
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 |
|
|
Required parameter |
Required parameter not provided |
|
|
Iblock not found |
Information block not found |
|
|
Access denied |
Insufficient rights for reading |
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 |