# Delete custom field

> Removes a custom field from the API: it disappears from the list, its values are no longer returned on people, and writing to it with custom attributes…

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

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

Removes the field from the API. It disappears from [List custom fields](/docs/crm/list-attributes), its values are no longer returned on people, and writing to it with `custom_attributes` returns `CUSTOM_ATTRIBUTE_KEY_UNKNOWN`.

Returns `204 No Content`.

<Note>
The values stored on people are kept. Creating a field with the same label and type with [Create custom field](/docs/crm/create-attribute) restores the field and its values. The field keeps its slot toward the [limits](/docs/crm/attributes-overview#limits) until then. This differs from [Delete company attribute](/docs/crm/delete-company-attribute), which clears the values.
</Note>

Fields synced from a CRM integration cannot be deleted. Remove them in the connected CRM. Built-in fields such as `name` or `company` cannot be deleted either.

## Errors

| Status | Code | When |
|--------|------|------|
| `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_DELETE` |
| `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 is already deleted |
| `409` | `ATTRIBUTE_MANAGED_BY_INTEGRATION` | The field is managed by a CRM integration |
