# Catalog SKUs

SKUs are a distinct Bitrix24 catalog subtype. Manage their prices through [catalog prices](/docs/entities/catalog-prices).

Bitrix24 API: `catalog.product.sku.*`
Scope: `catalog`

## Operations

- [List SKUs](./catalog-skus/list.md) — `GET /v1/catalog-skus`
- [Get an SKU](./catalog-skus/get.md) — `GET /v1/catalog-skus/:id`
- [Create an SKU](./catalog-skus/create.md) — `POST /v1/catalog-skus`
- [Update an SKU](./catalog-skus/update.md) — `PATCH /v1/catalog-skus/:id`
- [Delete an SKU](./catalog-skus/delete.md) — `DELETE /v1/catalog-skus/:id`
- [SKU fields](./catalog-skus/fields.md) — `GET /v1/catalog-skus/fields`
- [Search SKUs](./catalog-skus/search.md) — `POST /v1/catalog-skus/search`
- [Aggregate SKUs](./catalog-skus/aggregate.md) — `POST /v1/catalog-skus/aggregate`

List and search require the product catalog's `filter.iblockId` (for example, 25; use your own catalog ID). Find it through [catalogs](/docs/entities/catalogs). Creation needs `iblockId` and `name`. Bitrix24 creates an empty SKU (`TYPE_EMPTY_SKU`); linking an [offer](/docs/entities/catalog-offers) changes it to `TYPE_SKU` without a separate V1 write. `type` is read only. Portal properties use names such as `property295`; their numbers depend on the catalog.