[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-userfields\u002Fsmart-processes\u002Fdelete":3,"docs-tabs-userfields\u002Fsmart-processes\u002Fdelete":6},{"content":4,"lastmod":5},"\n## Delete field\n\n`DELETE \u002Fv1\u002Fitems\u002F:entityTypeId\u002Fuserfields\u002F:id`\n\nDeletes a smart process user field along with all of its values in items. A deleted field cannot be restored via the API — create a new one if needed.\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 on each element of the `data` array |\n| `:id` (path) | number | yes | Numeric field identifier (from the response of [`GET \u002Fv1\u002Fitems\u002F:entityTypeId\u002Fuserfields`](\u002Fdocs\u002Fuserfields\u002Fsmart-processes\u002Flist) or [`POST \u002Fv1\u002Fitems\u002F:entityTypeId\u002Fuserfields`](\u002Fdocs\u002Fuserfields\u002Fsmart-processes\u002Fcreate)) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F174\u002Fuserfields\u002F8210\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F174\u002Fuserfields\u002F8210\" \\\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\u002F8210',\n  {\n    method: 'DELETE',\n    headers: {\n      'X-Api-Key': 'YOUR_API_KEY',\n    },\n  }\n)\n\nif (res.status === 204) {\n  console.log('Field deleted')\n}\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch(\n  'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F174\u002Fuserfields\u002F8210',\n  {\n    method: 'DELETE',\n    headers: {\n      'X-Api-Key': 'YOUR_APP_KEY',\n      'Authorization': 'Bearer USER_SESSION_TOKEN',\n    },\n  }\n)\n\nif (res.status === 204) {\n  console.log('Field deleted')\n}\n```\n\n## Response\n\nOn successful deletion, an HTTP `204 No Content` status is returned with an empty body. The success indicator is the response code, not the body.\n\n## Response example\n\n```http\nHTTP\u002F1.1 204 No Content\n```\n\n## Error response example\n\n403 — the key has no `userfieldconfig` scope:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ACCESS_DENIED\",\n    \"message\": \"The request requires higher privileges than provided by the webhook token\"\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| 400 | `INVALID_PARAMS` | `:id` is not a positive integer or exceeds `9007199254740991`. The value must contain digits only, with no leading zero, sign, fractional part, exponent or spaces. The field is not deleted |\n| 403 | `BITRIX_ACCESS_DENIED` | The key has no `userfieldconfig` scope — reissue the key with this scope |\n| 403 | `SCOPE_DENIED` | The API key has no `crm` scope |\n| 404 | `SMART_PROCESS_NOT_FOUND` | A smart process with the given `entityTypeId` was not found on the portal |\n| 404 | `ENTITY_NOT_FOUND` | The smart process in the path has no field with the given `id`: the field is already deleted or belongs to another entity. Nothing is deleted |\n| 422 | `BITRIX_ERROR` | The field was deleted between the check and the deletion — Bitrix24 responds \"You cannot delete the user field\" |\n| 401 | `TOKEN_MISSING` | The API key has no configured tokens |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**Values in items are deleted permanently.** When a field is deleted, all of its values in existing smart process items are lost. If the field is used in automations, automation rules, or integrations, check the dependencies before deleting.\n\n**Only a field of the smart process in the path is deleted.** Field IDs are shared across all entities of the Bitrix24 account, so before deleting, the platform checks that the smart process `:entityTypeId` has a field with this `id`. A field of another entity is not deleted; the response is `404 ENTITY_NOT_FOUND`.\n\n**Repeated deletion.** A repeated `DELETE` on the same `id` returns `404 ENTITY_NOT_FOUND`: the field is already deleted.\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-10-06",{},1794739616062]