# Update custom field

> Partially updates a custom field on people: only the fields you send change. key and type cannot be changed. Fields synced from a CRM integration cannot be…

`PATCH /v2/api/crm/attributes/{key}`

<Note>
**Required scope:** `CRM_WRITE`
</Note>

This endpoint performs a partial update. Only the fields you send are modified. `key` and `type` cannot be changed.

## Body fields

| Field | Type | Description |
|-------|------|-------------|
| `label` | string | New display name |
| `description` | string | Description of the field. A blank value clears it |
| `options` | array | Replaces the full option list with `{ label, key? }` objects. `DROPDOWN` fields only |

## Renaming options

Option keys stay stable. To rename an option, send its current `key` with the new `label`. An option sent without a matching `key` is treated as new and gets a key derived from its label. Options missing from the list are removed.

## Fields synced from a CRM

A field whose `source` is not `allo` is managed by your CRM integration and cannot be edited. Any update returns `409 ATTRIBUTE_MANAGED_BY_INTEGRATION`. Built-in fields such as `name` or `company` return `400 ATTRIBUTE_BUILT_IN`.

## Response

Returns `200` with the updated field, in the same shape as [List custom fields](/docs/crm/list-attributes).

```json
{
  "data": {
    "key": "lead_status",
    "label": "Lead temperature",
    "type": "DROPDOWN",
    "options": [
      { "key": "hot", "label": "Hot" },
      { "key": "warm", "label": "Warm" },
      { "key": "cold", "label": "Cold" }
    ],
    "source": "allo"
  }
}
```

## Errors

| Status | Code | When |
|--------|------|------|
| `400` | `ATTRIBUTE_LABEL_INVALID` | `label` is blank, longer than 255 characters, or has no letter or digit |
| `400` | `ATTRIBUTE_OPTION_INVALID` | An option label is blank, longer than 255 characters or duplicated |
| `400` | `ATTRIBUTE_OPTIONS_NOT_SUPPORTED` | `options` sent for a field that is not `DROPDOWN` |
| `400` | `ATTRIBUTE_BUILT_IN` | The key is a built-in field, not a custom field |
| `403` | `API_KEY_INSUFFICIENT_SCOPE` | The key does not hold `CRM_WRITE` |
| `404` | `TEAM_NOT_FOUND` | The workspace is not on the new contact model |
| `404` | `ATTRIBUTE_NOT_FOUND` | No field with this key, or the field was deleted |
| `409` | `ATTRIBUTE_MANAGED_BY_INTEGRATION` | The field is managed by a CRM integration |
