For AI agents: markdown of this page — /docs-content-en/userfields/smart-processes/types.md documentation index — /llms.txt

Field type catalog

GET /v1/items/:entityTypeId/userfields/types

Returns the list of available user field types. The list is the same for all smart processes and for CRM entities.

Parameters

Parameter Type Required Description
Parameter:entityTypeId (path) Typenumber Requiredyes DescriptionSmart process type identifier. Source: GET /v1/smart-processes — the entityTypeId field. The value does not affect the result — it is used only to validate the path

Examples

curl — personal key

Terminal 
curl "https://vibecode.bitrix24.com/v1/items/174/userfields/types" \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

Terminal 
curl "https://vibecode.bitrix24.com/v1/items/174/userfields/types" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"

JavaScript — personal key

javascript 
const res = await fetch(
  'https://vibecode.bitrix24.com/v1/items/174/userfields/types',
  {
    headers: { 'X-Api-Key': 'YOUR_API_KEY' },
  }
)
const { success, data } = await res.json()
console.log(`Available types: ${data.length}`)

JavaScript — OAuth application

javascript 
const res = await fetch(
  'https://vibecode.bitrix24.com/v1/items/174/userfields/types',
  {
    headers: {
      'X-Api-Key': 'YOUR_APP_KEY',
      'Authorization': 'Bearer USER_SESSION_TOKEN',
    },
  }
)
const { success, data } = await res.json()

Response fields

Field Type Description
Fieldsuccess Typeboolean DescriptionAlways true on success
Fielddata Typearray DescriptionArray of field type objects
Fielddata[].ID Typestring DescriptionType identifier — used as userTypeId in create and filter requests
Fielddata[].title Typestring DescriptionDisplay name of the type

Full list of types from the API response:

ID title
IDstring titleString
IDinteger titleInteger
IDdouble titleNumber
IDboolean titleYes/No
IDenumeration titleList
IDdatetime titleDate/Time
IDdate titleDate
IDmoney titleMoney
IDurl titleLink
IDaddress titleGoogle Map address
IDfile titleFile
IDemployee titleBind to user
IDcrm_status titleBind to CRM directories
IDiblock_section titleBind to information block sections
IDiblock_element titleBind to information block elements
IDcrm titleBind to CRM elements

Response example

JSON 
{
  "success": true,
  "data": [
    { "ID": "string", "title": "String" },
    { "ID": "integer", "title": "Integer" },
    { "ID": "double", "title": "Number" },
    { "ID": "boolean", "title": "Yes/No" },
    { "ID": "enumeration", "title": "List" },
    { "ID": "datetime", "title": "Date/Time" },
    { "ID": "date", "title": "Date" },
    { "ID": "money", "title": "Money" },
    { "ID": "url", "title": "Link" },
    { "ID": "address", "title": "Google Map address" },
    { "ID": "file", "title": "File" },
    { "ID": "employee", "title": "Bind to user" },
    { "ID": "crm_status", "title": "Bind to CRM directories" },
    { "ID": "iblock_section", "title": "Bind to information block sections" },
    { "ID": "iblock_element", "title": "Bind to information block elements" },
    { "ID": "crm", "title": "Bind to CRM elements" }
  ]
}

Error response example

400 — invalid entityTypeId:

JSON 
{
  "success": false,
  "error": {
    "code": "INVALID_ENTITY_TYPE_ID",
    "message": "entityTypeId must be a positive integer"
  }
}

Errors

HTTP Code Description
HTTP400 CodeINVALID_ENTITY_TYPE_ID Description:entityTypeId is not a positive integer
HTTP401 CodeMISSING_API_KEY DescriptionThe X-Api-Key header is missing
HTTP401 CodeTOKEN_MISSING DescriptionThe API key has no configured tokens
HTTP403 CodeSCOPE_DENIED DescriptionThe API key has no crm scope

Full list of common API errors — Errors.

Known specifics

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.

Does not require the userfieldconfig scope. Unlike the other /items/:entityTypeId/userfields* endpoints, the types request works with the crm scope alone.

See also