## Update a price

`PATCH /v1/catalog-prices/:id`

Updates an existing price. Fields are passed flat in the JSON root. Pass only the fields being changed — the rest keep their current values.

## Parameters

| Parameter | Type | Req. | Description |
|----------|-----|:-----:|---------|
| `id` (path) | number | yes | Price identifier |

## Request fields (body)

| Field | Type | Req. | Description |
|------|-----|:-----:|---------|
| `productId` | number | no | ID of the product the price belongs to. List: `GET /v1/catalog-products?filter[iblockId]=<id>` (the `iblockId` value comes from `GET /v1/catalogs`) |
| `catalogGroupId` | number | no | Price type. Base price is `1`. The types configured in the Bitrix24 account are visible from the `catalogGroupId` values in the [price list](/docs/entities/catalog-prices/list) |
| `price` | number | no | Price value |
| `currency` | string | no | Price currency, e.g. `USD`. List: `GET /v1/currencies` |
| `quantityFrom` | number | no | Lower bound of the quantity range |
| `quantityTo` | number | no | Upper bound of the quantity range |

`id` is passed in the path (`/v1/catalog-prices/:id`); it cannot be passed in the body — it is read-only.

## Examples

### curl — personal key

```bash
curl -X PATCH "https://vibecode.bitrix24.com/v1/catalog-prices/5104" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "price": 1750
  }'
```

### curl — OAuth app

```bash
curl -X PATCH "https://vibecode.bitrix24.com/v1/catalog-prices/5104" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "price": 1750
  }'
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/catalog-prices/5104', {
  method: 'PATCH',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    price: 1750,
  }),
})

const { success, data } = await res.json()
console.log('New price:', data.price)
```

### JavaScript — OAuth app

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/catalog-prices/5104', {
  method: 'PATCH',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    price: 1750,
  }),
})

const { success, data } = await res.json()
```

## Response fields

Returns the full updated price object.

| Field | Type | Description |
|------|-----|---------|
| `id` | number | Price identifier |
| `productId` | number | Product ID |
| `catalogGroupId` | number | Price type |
| `price` | number | Price value |
| `currency` | string | Price currency |
| `quantityFrom` | number \| null | Lower bound of the quantity range |
| `quantityTo` | number \| null | Upper bound of the quantity range |
| `priceScale` | number | Price in the Bitrix24 account's base currency |
| `extraId` | number \| null | Markup identifier (`catalog_extra`). Deprecated Bitrix24 field |
| `timestampX` | string | Modification date (ISO 8601 with timezone) |

## Response example

```json
{
  "success": true,
  "data": {
    "catalogGroupId": 1,
    "currency": "USD",
    "extraId": null,
    "id": 5104,
    "price": 1750,
    "priceScale": 1500,
    "productId": 104,
    "quantityFrom": null,
    "quantityTo": null,
    "timestampX": "2026-06-08T14:59:07+00:00"
  }
}
```

## Error response example

422 — a price with the given `id` does not exist:

```json
{
  "success": false,
  "error": {
    "code": "BITRIX_ERROR",
    "message": "Price is not exists"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|----------|
| 422 | `BITRIX_ERROR` | A price with the given `id` does not exist (`Price is not exists`) |
| 400 | `READONLY_FIELD` | The body contained `id` — this field is set by the system and is not accepted on update |
| 403 | `SCOPE_DENIED` | The key lacks the `catalog` scope |
| 401 | `TOKEN_MISSING` | `X-Api-Key` was not provided |

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

## Known specifics

**`priceScale` is not recalculated when `price` changes.** On creation `priceScale` matches `price`. If you update only `price`, the response keeps the previous `priceScale` value.

## See also

- [Create a price](/docs/entities/catalog-prices/create)
- [List prices](/docs/entities/catalog-prices/list)
- [Get a price](/docs/entities/catalog-prices/get)
- [Delete a price](/docs/entities/catalog-prices/delete)
- [Catalog products](/docs/entities/catalog-products)
- [Batch](/docs/batch)
- [Limits and optimization](/docs/optimization)