[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-userfields\u002Fusers\u002Fdelete":3,"docs-tabs-userfields\u002Fusers\u002Fdelete":6},{"content":4,"lastmod":5},"## Delete employee field\n\n`DELETE \u002Fv1\u002Fuserfields\u002Fusers\u002F:id`\n\nDeletes an employee user field together with all its values in employee cards. 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| `:id` (path) | number | yes | Numeric identifier of the field (from the response of [`GET \u002Fv1\u002Fuserfields\u002Fusers`](\u002Fdocs\u002Fuserfields\u002Fusers\u002Flist) or [`POST \u002Fv1\u002Fuserfields\u002Fusers`](\u002Fdocs\u002Fuserfields\u002Fusers\u002Fcreate)) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fuserfields\u002Fusers\u002F6007923\" \\\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\u002Fuserfields\u002Fusers\u002F6007923\" \\\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('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fuserfields\u002Fusers\u002F6007923', {\n  method: 'DELETE',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\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('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fuserfields\u002Fusers\u002F6007923', {\n  method: 'DELETE',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nif (res.status === 204) {\n  console.log('Field deleted')\n}\n```\n\n## Response\n\nOn successful deletion, the API returns HTTP status `204 No Content` with an empty body. Success is indicated by 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\n404 — there is no field with this `id`:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"User field 999999999 not found\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_ID` | `:id` is not a positive integer — the request is rejected before the portal is contacted |\n| 404 | `ENTITY_NOT_FOUND` | There is no field with this `id` — including a repeated `DELETE` after a successful deletion |\n| 422 | `BITRIX_ERROR` | The key owner is not a Bitrix24 account administrator — Bitrix24 responds with the message `Access denied.` |\n| 422 | `BITRIX_ERROR` | Other Bitrix24 rejections — including a field removed between the existence check and the deletion itself. The text is returned verbatim in `error.message` |\n| 403 | `SCOPE_DENIED` | The API key does not have the `user.userfield` scope |\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 employee cards are deleted irreversibly.** When a field is deleted, all of its values for employees are lost. If the field is used in workflows or integrations, check the dependencies before deleting.\n\n**The field disappears from the employee schema immediately.** After deletion, the `UF_USR_*` name disappears from [`GET \u002Fv1\u002Fusers\u002Ffields`](\u002Fdocs\u002Fentities\u002Fusers\u002Ffields) without delay, and [`GET \u002Fv1\u002Fuserfields\u002Fusers\u002F:id`](\u002Fdocs\u002Fuserfields\u002Fusers\u002Fget) for the former `id` returns `404 NOT_FOUND`. A repeated `DELETE` on the same `id` returns `404 ENTITY_NOT_FOUND`.\n\n## See also\n\n- [List employee fields](\u002Fdocs\u002Fuserfields\u002Fusers\u002Flist)\n- [Create employee field](\u002Fdocs\u002Fuserfields\u002Fusers\u002Fcreate)\n- [Employee fields](\u002Fdocs\u002Fuserfields\u002Fusers)\n- [User fields](\u002Fdocs\u002Fuserfields)\n","2026-10-09",{},1794739617916]