## Delete an SKU

`DELETE /v1/catalog-skus/:id`

Deletes a parent product by identifier together with all its offers. A deleted product and its offers cannot be restored via the API — create them again if needed.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|---------|
| `id` (path) | number | yes | Parent product identifier. List: [`GET /v1/catalog-skus`](./list.md) |

## Examples

### curl — personal key

```bash
curl -X DELETE "https://vibecode.bitrix24.com/v1/catalog-skus/7203" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl -X DELETE "https://vibecode.bitrix24.com/v1/catalog-skus/7203" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/catalog-skus/7203', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

if (res.status === 204) {
  console.log('Parent product deleted')
}
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/catalog-skus/7203', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

if (res.status === 204) {
  console.log('Parent product deleted')
}
```

## Response

On successful deletion, an HTTP status `204 No Content` is returned with an empty body — success is checked by the status.

## Response example

```http
HTTP/1.1 204 No Content
```

## Error response example

404 — no parent product with the specified `id` exists:

```json
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "sku does not exist."
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|----------|
| 404 | `ENTITY_NOT_FOUND` | No product with the specified `id` exists, including on a repeated delete request (`sku does not exist.`) |
| 422 | `BITRIX_ERROR` | An offer of the parent product cannot be deleted because it is used in inventory documents. The Bitrix24 message names the offer by its `#<id>` and name. The parent product and its offers stay in place |
| 403 | `SCOPE_DENIED` | The key lacks the `catalog` scope |
| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |

Full list of common API errors — [Errors](/docs/errors).

## Known specifics

**Offers are deleted together with the parent product.** After `204`, a request for any of its offers — [`GET /v1/catalog-offers/:id`](/docs/entities/catalog-offers/get) — returns `404 ENTITY_NOT_FOUND`.

**The method does not check that the `id` belongs to a parent product.** With the `id` of a regular product, the call returns `204` and deletes that product. Check the record before deleting: [`GET /v1/catalog-skus/:id`](./get.md) returns `404 ENTITY_NOT_FOUND` for an `id` that does not belong to a parent product.

## See also

- [Create an SKU](/docs/entities/catalog-skus/create)
- [List SKUs](/docs/entities/catalog-skus/list)
- [Get an SKU](/docs/entities/catalog-skus/get)
- [Update an SKU](/docs/entities/catalog-skus/update)
- [Catalog offers](/docs/entities/catalog-offers)
- [Batch](/docs/batch)
- [Limits and optimization](/docs/optimization)