## 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 |
|----------|-----|:-----:|---------|
| `:entityTypeId` (path) | number | yes | Smart process type identifier. Source: [`GET /v1/smart-processes`](/docs/entities/smart-processes) — the `entityTypeId` field. The value does not affect the result — it is used only to validate the path |

## Examples

### curl — personal key

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

### curl — OAuth application

```bash
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 |
|------|-----|---------|
| `success` | boolean | Always `true` on success |
| `data` | array | Array of field type objects |
| `data[].ID` | string | Type identifier — used as `userTypeId` in create and filter requests |
| `data[].title` | string | Display name of the type |

Full list of types from the API response:

| `ID` | `title` |
|------|---------|
| `string` | String |
| `integer` | Integer |
| `double` | Number |
| `boolean` | Yes/No |
| `enumeration` | List |
| `datetime` | Date/Time |
| `date` | Date |
| `money` | Money |
| `url` | Link |
| `address` | Google Map address |
| `file` | File |
| `employee` | Bind to user |
| `crm_status` | Bind to CRM directories |
| `iblock_section` | Bind to information block sections |
| `iblock_element` | Bind to information block elements |
| `crm` | Bind 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 |
|------|-----|---------|
| 400 | `INVALID_ENTITY_TYPE_ID` | `:entityTypeId` is not a positive integer |
| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |
| 401 | `TOKEN_MISSING` | The API key has no configured tokens |
| 403 | `SCOPE_DENIED` | The API key has no `crm` scope |

Full list of common API errors — [Errors](/docs/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

- [List smart process fields](/docs/userfields/smart-processes/list)
- [Create field](/docs/userfields/smart-processes/create)
- [Smart process fields](/docs/userfields/smart-processes)
- [User fields](/docs/userfields)