[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fcatalog-price-types\u002Fdelete":3,"docs-tabs-entities\u002Fcatalog-price-types\u002Fdelete":6},{"content":4,"lastmod":5},"## Delete a price type\n\n`DELETE \u002Fv1\u002Fcatalog-price-types\u002F:id`\n\nDeletes a catalog price type. The deleted record and its related data cannot be restored through the API.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|-------|----------|\n| `id` (path) | number | yes | Price type ID, a non-negative integer. List: [List price types](.\u002Flist.md). |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcatalog-price-types\u002F19\" \\\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\u002Fcatalog-price-types\u002F19\" \\\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\u002Fcatalog-price-types\u002F19', {\n  method: 'DELETE',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\n\nif (res.status === 204) {\n  console.log('Price type deleted')\n}\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcatalog-price-types\u002F19', {\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('Price type deleted')\n}\n```\n\n## Response\n\nSuccessful deletion returns HTTP status `204 No Content` with an empty body. The response status indicates success.\n\n## Response example\n\n```http\nHTTP\u002F1.1 204 No Content\n```\n\n## Error response example\n\n404 — the price type does not exist, for example when deleting it again:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"priceType does not exist.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 404 | `ENTITY_NOT_FOUND` | During the check before deletion, Bitrix24 reported that no price type exists with this `id`. |\n| 404 | `ENTITY_NOT_FOUND` | The check before deletion returned an empty price type record. |\n| 422 | `BASE_PRICE_TYPE_CANNOT_DELETE` | The price type is the base type: its `base` is `Y`. |\n| 400 | `INVALID_PARAMS` | `id` is not a non-negative integer, for example `abc`. |\n| 400 | `INVALID_PARAMS` | Bitrix24 rejected the request parameters. |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the request. The reason is in `error.message`. |\n| 403 | `BITRIX_ACCESS_DENIED` | The user does not have the Bitrix24 “Manage price types” permission. |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode. |\n| 403 | `SCOPE_DENIED` | The key does not have the `catalog` scope. |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was omitted. |\n| 401 | `TOKEN_MISSING` | The key has no Bitrix24 tokens configured. For an OAuth application key, check the user session. |\n\nFor the full list of common API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**Deleting a price type also deletes every product price assigned to that type and its rounding rules on the Bitrix24 account.** Before calling the method, check the record with [Get a price type](.\u002Fget.md) and find related prices with [List prices](\u002Fdocs\u002Fentities\u002Fcatalog-prices\u002Flist).\n\n## See also\n\n- [Get a price type](.\u002Fget.md)\n- [List price types](.\u002Flist.md)\n- [Create a price type](.\u002Fcreate.md)\n- [Update a price type](.\u002Fupdate.md)\n- [Catalog prices](\u002Fdocs\u002Fentities\u002Fcatalog-prices)\n","2026-10-14",{},1794739330037]