لوكلاء AI: ملف markdown لهذه الصفحة — /docs-content-en/lists/fields.md فهرس التوثيق — /llms.txt
مقالات التوثيق متاحة حاليًا باللغة الإنجليزية فقط.
List fields
Manage a list's field set: get field descriptions, create new fields, update and delete them. A separate operation returns the allowed field types.
Bitrix24 API: lists.field.*
Scope: lists
List fields
GET /v1/lists/:iblockId/fields
Returns descriptions of system and user fields of a list to prepare forms and requests for its elements.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ParameteriblockId (path) |
Typestring | Requiredyes | Default— | DescriptionList identifier or symbolic code. Values come from the ID or CODE fields of List lists |
ParameteriblockTypeId (query) |
Typestring | Requiredno | Defaultlists |
DescriptionInfoblock type. Values:lists — regular listslists_socnet — workgroup listsbitrix_processes — service workflowsstructure — company structure type containing the built-in absence calendar infoblock absence |
ParametersocnetGroupId (query) |
Typenumber | Requiredno | Default— | DescriptionWorkgroup identifier for lists of type lists_socnet. A positive integer from the id field of List workgroups |
Examples
curl — personal key
curl https://vibecode.bitrix24.com/v1/lists/149/fields \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
curl https://vibecode.bitrix24.com/v1/lists/149/fields \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN"
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/lists/149/fields', {
headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})
const { data } = await res.json()
console.log('Field IDs:', Object.keys(data))
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/lists/149/fields', {
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
})
const { data } = await res.json()
Response fields
The response contains a field dictionary without pagination. In the path data.<FIELD_ID>, <FIELD_ID> is replaced by a field identifier, for example NAME or PROPERTY_1197. The response has no meta field.
| Field | Type | Description |
|---|---|---|
Fieldsuccess |
Typeboolean | DescriptionAlways true on success |
Fielddata |
Typeobject | DescriptionDictionary: the key is the field identifier FIELD_ID, the value is its description object |
Fielddata.<FIELD_ID>.FIELD_ID |
Typestring | DescriptionField identifier for Get field. For user fields — PROPERTY_<number>, for system fields — a symbolic code, for example NAME |
Fielddata.<FIELD_ID>.NAME |
Typestring | DescriptionDisplay name of the field |
Fielddata.<FIELD_ID>.TYPE |
Typestring | DescriptionField type code. Code reference — Field types |
Fielddata.<FIELD_ID>.IS_REQUIRED |
Typestring | DescriptionWhether the field is required: Y or N |
Fielddata.<FIELD_ID>.MULTIPLE |
Typestring | DescriptionAllows multiple values: Y or N |
Fielddata.<FIELD_ID>.SORT |
Typenumber | DescriptionSort order in the form |
Fielddata.<FIELD_ID>.DEFAULT_VALUE |
Typestring, object or null | DescriptionDefault value. The format depends on TYPE: for example, N uses a string containing a number, while S:HTML uses an object with the keys TYPE and TEXT |
Fielddata.<FIELD_ID>.CODE |
Typestring or null | DescriptionSymbolic code of the user field. null if not set. Absent for system fields |
Fielddata.<FIELD_ID>.ID |
Typestring | DescriptionNumeric identifier of the user field as a string — the numeric part of FIELD_ID. Absent for system fields |
Fielddata.<FIELD_ID>.PROPERTY_TYPE |
Typestring or boolean | DescriptionBase type of the user field: S, N, L, F, G or E. For system fields — false |
Fielddata.<FIELD_ID>.PROPERTY_USER_TYPE |
Typeobject or boolean | DescriptionDescription of the extended property type. Contains its base type PROPERTY_TYPE, code USER_TYPE, name DESCRIPTION, and handlers, which vary by type. false if there is no extended type |
Fielddata.<FIELD_ID>.LINK_IBLOCK_ID |
Typestring or null | DescriptionLinked list identifier from the ID field of List lists. null if there is no link. Absent for system fields |
Fielddata.<FIELD_ID>.ROW_COUNT |
Typestring | DescriptionInput field height in rows. Absent for system fields |
Fielddata.<FIELD_ID>.COL_COUNT |
Typestring | DescriptionInput field width in characters. Absent for system fields |
Fielddata.<FIELD_ID>.USER_TYPE_SETTINGS |
Typeobject or null | DescriptionExtended property type settings. The fields depend on TYPE, for example height for S:HTML. null if there are no settings. Absent for system fields |
Fielddata.<FIELD_ID>.SETTINGS |
Typeobject or boolean | DescriptionField display settings in forms. false if no settings are configured. A system field can also return an object |
Fielddata.<FIELD_ID>.SETTINGS.SHOW_ADD_FORM |
Typestring | DescriptionShow the field when adding an element: Y or N |
Fielddata.<FIELD_ID>.SETTINGS.SHOW_EDIT_FORM |
Typestring | DescriptionShow the field when editing an element: Y or N |
Fielddata.<FIELD_ID>.SETTINGS.ADD_READ_ONLY_FIELD |
Typestring | DescriptionThe field is read-only when adding an element: Y or N |
Fielddata.<FIELD_ID>.SETTINGS.EDIT_READ_ONLY_FIELD |
Typestring | DescriptionThe field is read-only when editing an element: Y or N |
Fielddata.<FIELD_ID>.SETTINGS.SHOW_FIELD_PREVIEW |
Typestring | DescriptionShow the field when previewing an element: Y or N |
Fielddata.<FIELD_ID>.IBLOCK_ID |
Typenumber | DescriptionIdentifier of the list the field belongs to. Source — List lists |
Fielddata.<FIELD_ID>.DISPLAY_VALUES_FORM |
Typeobject or array | DescriptionChoices for types L, G, E and E:...: the key is the identifier of an option, section or element, the value is its name. Returns an empty array [] if there are no choices |
To iterate over field descriptions, use Object.values(data). To get their identifiers, use Object.keys(data).
Response example
{
"success": true,
"data": {
"NAME": {
"FIELD_ID": "NAME",
"SORT": 10,
"NAME": "Name",
"IS_REQUIRED": "Y",
"MULTIPLE": "N",
"DEFAULT_VALUE": "",
"TYPE": "NAME",
"PROPERTY_TYPE": false,
"PROPERTY_USER_TYPE": false,
"SETTINGS": false,
"IBLOCK_ID": 149
},
"PROPERTY_1197": {
"FIELD_ID": "PROPERTY_1197",
"SORT": 20,
"NAME": "Priority",
"IS_REQUIRED": "N",
"MULTIPLE": "N",
"DEFAULT_VALUE": "0",
"TYPE": "N",
"PROPERTY_TYPE": "N",
"PROPERTY_USER_TYPE": false,
"CODE": "PRIORITY",
"ID": "1197",
"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": "N",
"SHOW_FIELD_PREVIEW": "N"
},
"IBLOCK_ID": 149
}
}
}
Error response example
404 — no list with the specified identifier exists:
{
"success": false,
"error": {
"code": "LIST_NOT_FOUND",
"message": "List not found"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| HTTP400 | CodeINVALID_IBLOCK_TYPE |
DescriptioniblockTypeId is not one of the allowed types |
| HTTP403 | CodeBITRIX_ACCESS_DENIED |
DescriptionNo permission to view the list |
| HTTP404 | CodeLIST_NOT_FOUND |
DescriptionNo list with the specified iblockId exists |
| HTTP409 | CodeLISTS_MODULE_NOT_ENABLED |
DescriptionThe lists module is not enabled on the portal |
| HTTP403 | CodeSCOPE_DENIED |
DescriptionThe key is missing the lists scope |
| HTTP401 | CodeTOKEN_MISSING |
DescriptionThe key has no configured tokens |
Full list of common API errors — Errors.