Get Field Parameters or List of Fields `lists.field.get`

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: lists

Who 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 `type`	Description
IBLOCK_TYPE_ID* `string`	Identifier of the information block type. Possible values: `lists` — list information block type `bitrix_processes` — processes information block type `lists_socnet` — group lists information block type The identifier can be obtained using the method lists.get.iblock.type.id
IBLOCK_ID* `integer`	Identifier of the information block. The identifier can be obtained using the method lists.get
IBLOCK_CODE* `string`	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: `IBLOCK_ID` or `IBLOCK_CODE`
FIELD_ID `string`	Identifier of the field. For a custom field, it appears as `PROPERTY_PropertyId`. For a system field, it is its symbolic code. If not specified, all fields of the list are returned

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

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

try
        {
            const response = await $b24.callMethod(
                'lists.field.get',
                {
                    IBLOCK_TYPE_ID: 'lists',
                    IBLOCK_ID: '123',
                    FIELD_ID: 'PROPERTY_1151',
                }
            );
            
            const result = response.getData().result;
            console.log('Fetched field data:', result);
            
            processResult(result);
        }
        catch( error )
        {
            console.error('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>';

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
type

Description

result
array

Data of the field or an array of fields.

An empty array means that there are no fields in the list with the specified FIELD_ID

time
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 `type`	Description
error `string`	String error code. It may consist of digits, Latin letters, and underscores
error_description `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
`ERROR_REQUIRED_PARAMETERS_MISSING`	Required parameter `X` is missing	Required parameter not provided
`ERROR_IBLOCK_NOT_FOUND`	Iblock not found	Information block not found
`ACCESS_DENIED`	Access denied	Insufficient rights for reading

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status	Code Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`405`	`ERROR_BATCH_METHOD_NOT_ALLOWED` Method is not allowed for batch usage	The current method is not permitted for calls using batch
`400`	`ERROR_BATCH_LENGTH_EXCEEDED` Max batch length exceeded	The maximum length of parameters passed to the batch method has been exceeded
`401`	`NO_AUTH_FOUND` Wrong authorization data	Invalid access token or webhook code
`400`	`INVALID_REQUEST` Https required	The HTTPS protocol is required for method calls
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is only available on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user associated with the access token or webhook used to call the method lacks the necessary permissions
`404`	`ERROR_MANIFEST_IS_NOT_AVAILABLE` Manifest is not available	The manifest is not available
`403`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires higher privileges than those provided by the webhook token
`401`	`expired_token` The access token provided has expired	The provided access token has expired
`403`	`user_access_error` The user does not have access to the application	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
`500`	`PORTAL_DELETED` Portal was deleted	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

Update List Field

Delete Field

Get Field Parameters or List of Fields lists.field.get

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning