[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-userfields\u002Fsmart-processes\u002Ftypes":3,"docs-tabs-userfields\u002Fsmart-processes\u002Ftypes":6},{"content":4,"lastmod":5},"\n## Field type catalog\n\n`GET \u002Fv1\u002Fitems\u002F:entityTypeId\u002Fuserfields\u002Ftypes`\n\nReturns the list of available user field types. The list is the same for all smart processes and for CRM entities.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `:entityTypeId` (path) | number | yes | Smart process type identifier. Source: [`GET \u002Fv1\u002Fsmart-processes`](\u002Fdocs\u002Fentities\u002Fsmart-processes) — the `entityTypeId` field. The value does not affect the result — it is used only to validate the path |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F174\u002Fuserfields\u002Ftypes\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F174\u002Fuserfields\u002Ftypes\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\"\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch(\n  'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F174\u002Fuserfields\u002Ftypes',\n  {\n    headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n  }\n)\nconst { success, data } = await res.json()\nconsole.log(`Available types: ${data.length}`)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch(\n  'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F174\u002Fuserfields\u002Ftypes',\n  {\n    headers: {\n      'X-Api-Key': 'YOUR_APP_KEY',\n      'Authorization': 'Bearer USER_SESSION_TOKEN',\n    },\n  }\n)\nconst { success, data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data` | array | Array of field type objects |\n| `data[].ID` | string | Type identifier — used as `userTypeId` in create and filter requests |\n| `data[].title` | string | Display name of the type |\n\nFull list of types from the API response:\n\n| `ID` | `title` |\n|------|---------|\n| `string` | String |\n| `integer` | Integer |\n| `double` | Number |\n| `boolean` | Yes\u002FNo |\n| `enumeration` | List |\n| `datetime` | Date\u002FTime |\n| `date` | Date |\n| `money` | Money |\n| `url` | Link |\n| `address` | Google Map address |\n| `file` | File |\n| `employee` | Bind to user |\n| `crm_status` | Bind to CRM directories |\n| `iblock_section` | Bind to information block sections |\n| `iblock_element` | Bind to information block elements |\n| `crm` | Bind to CRM elements |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    { \"ID\": \"string\", \"title\": \"String\" },\n    { \"ID\": \"integer\", \"title\": \"Integer\" },\n    { \"ID\": \"double\", \"title\": \"Number\" },\n    { \"ID\": \"boolean\", \"title\": \"Yes\u002FNo\" },\n    { \"ID\": \"enumeration\", \"title\": \"List\" },\n    { \"ID\": \"datetime\", \"title\": \"Date\u002FTime\" },\n    { \"ID\": \"date\", \"title\": \"Date\" },\n    { \"ID\": \"money\", \"title\": \"Money\" },\n    { \"ID\": \"url\", \"title\": \"Link\" },\n    { \"ID\": \"address\", \"title\": \"Google Map address\" },\n    { \"ID\": \"file\", \"title\": \"File\" },\n    { \"ID\": \"employee\", \"title\": \"Bind to user\" },\n    { \"ID\": \"crm_status\", \"title\": \"Bind to CRM directories\" },\n    { \"ID\": \"iblock_section\", \"title\": \"Bind to information block sections\" },\n    { \"ID\": \"iblock_element\", \"title\": \"Bind to information block elements\" },\n    { \"ID\": \"crm\", \"title\": \"Bind to CRM elements\" }\n  ]\n}\n```\n\n## Error response example\n\n400 — invalid `entityTypeId`:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_ENTITY_TYPE_ID\",\n    \"message\": \"entityTypeId must be a positive integer\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_ENTITY_TYPE_ID` | `:entityTypeId` is not a positive integer |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |\n| 401 | `TOKEN_MISSING` | The API key has no configured tokens |\n| 403 | `SCOPE_DENIED` | The API key has no `crm` scope |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**Same result for all entities.** The list of types is the same for smart processes and for CRM entities. It can be called with any valid `entityTypeId` — the response will be identical. The parameter value affects only path validation.\n\n**Does not require the `userfieldconfig` scope.** Unlike the other `\u002Fitems\u002F:entityTypeId\u002Fuserfields*` endpoints, the types request works with the `crm` scope alone.\n\n## See also\n\n- [List smart process fields](\u002Fdocs\u002Fuserfields\u002Fsmart-processes\u002Flist)\n- [Create field](\u002Fdocs\u002Fuserfields\u002Fsmart-processes\u002Fcreate)\n- [Smart process fields](\u002Fdocs\u002Fuserfields\u002Fsmart-processes)\n- [User fields](\u002Fdocs\u002Fuserfields)\n","2026-08-04",{},1794739616449]