# Update a price type

`PATCH /v1/catalog-price-types/:id` calls `catalog.priceType.update`. It requires the `catalog` scope and the Bitrix24 Manage price types permission.

Send at least one of `name`, `sort` or `xmlId`. The `id` comes from the path. `base` is read-only because setting it to `Y` would switch the base type across the account. Audit fields are read-only too.

```bash
curl -X PATCH 'https://vibecode.bitrix24.com/v1/catalog-price-types/15' \
  -H 'X-Api-Key: YOUR_API_KEY' -H 'Content-Type: application/json' \
  -d '{"name":"Wholesale 2026","sort":210}'
```

Success: `200` with the updated type in `data`. A missing `id` returns `404 ENTITY_NOT_FOUND`; a read-only field returns `400 READONLY_FIELD`; Bitrix24 business refusals return `422 BITRIX_ERROR` with the original message.

[Price type fields](/docs/entities/catalog-price-types/fields) · [Delete a type](/docs/entities/catalog-price-types/delete) · [Errors](/docs/errors)
