[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fitems\u002Fproducts-fields":3,"docs-tabs-entities\u002Fitems\u002Fproducts-fields":6},{"content":4,"lastmod":5},"## Item product fields\n\n`GET \u002Fv1\u002Fitems\u002F:entityTypeId\u002F:id\u002Fproducts\u002Ffields`\n\nReturns a description of each field on an item's product rows: name, type, and whether the field is readable and writable.\n\n> **The discount amount is called `discount`** — matching the data and the write contract. The previous name `discountSum` remains a deprecated alias: it is still returned by this endpoint and still accepted on write, so code written against the old field list keeps working. Product rows themselves carry only `discount` — migrate to it.\n\nUse the `entityTypeId` field from [`GET \u002Fv1\u002Fsmart-processes`](\u002Fdocs\u002Fentities\u002Fsmart-processes\u002Flist) in the `\u002Fv1\u002Fitems\u002F:entityTypeId` path. The type record's internal `id` is a different identifier. For example, if a type is returned as `{ \"id\": 3, \"entityTypeId\": 174 }`, the path starts with `\u002Fv1\u002Fitems\u002F174`. Use the returned value rather than assuming all type IDs start at 1030.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `entityTypeId` (path) | number | yes | Smart process type ID |\n| `id` (path) | number | yes | Item ID. Does not affect the response: the field dictionary is the same for every item |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F156\u002F741\u002Fproducts\u002Ffields\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F156\u002F741\u002Fproducts\u002Ffields\" \\\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\u002Fitems\u002F156\u002F741\u002Fproducts\u002Ffields', {\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\n\nconst { success, data } = await res.json()\nconsole.log('Fields:', Object.keys(data).length)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fitems\u002F156\u002F741\u002Fproducts\u002Ffields', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { success, data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data` | object | Product row field dictionary. The key is the field name, the value is its definition |\n| `data.\u003Cfield>.type` | string | Value type: `integer`, `double`, `string`, `char` |\n| `data.\u003Cfield>.isReadOnly` | boolean | Read-only: the field cannot be written |\n| `data.\u003Cfield>.isRequired` | boolean | Required flag. `false` on every product-row field |\n| `data.\u003Cfield>.isImmutable` | boolean | `true` on `ownerId` and `ownerType`: the row owner is set by the request path. Absent on `priceAccount` and `xmlId` |\n| `data.\u003Cfield>.isMultiple` | boolean | `false` on product row fields. Absent on `priceAccount` and `xmlId` |\n| `data.\u003Cfield>.isDynamic` | boolean | `false` on product row fields. Absent on `priceAccount` and `xmlId` |\n| `data.\u003Cfield>.title` | string | Field label. Absent on `priceAccount` and `xmlId` |\n| `data.\u003Cfield>.description` | string | Field note. Present on `id` and `discountSum` |\n| `meta.warnings` | array | Present only when Bitrix24 did not describe all of the fields. An item with the code `fields_partial` lists the fields whose definitions were derived without labels |\n\nProduct row fields described by `data`:\n\n| Field | Type | RO | Required | Description |\n|------|-----|:--:|:-----:|---------|\n| `id` | integer | yes | | Row ID |\n| `productId` | integer | | | Product ID. Catalog: `GET \u002Fv1\u002Fproducts` |\n| `productName` | string | | | Product name |\n| `price` | double | | | Price |\n| `quantity` | double | | | Quantity |\n| `discount` | double | | | Discount amount. Applied when `discountTypeId` is `1` |\n| `discountSum` | double | | | Deprecated alias of `discount` — accepted on write, absent from product rows |\n| `discountRate` | double | | | Discount percentage. Applied when `discountTypeId` is `2` |\n| `discountTypeId` | integer | | | How the discount is set: `1` — as an amount in `discount`, `2` — as a percentage in `discountRate`. Defaults to `2` |\n| `taxRate` | double | | | Tax (%) |\n| `taxIncluded` | char | | | Tax included in price. In product rows the field is returned as `true` or `false`, even though the dictionary gives its type as `char`. You can write any of the values `true`, `false`, `Y`, `N` |\n| `priceExclusive` | double | yes | | Price excluding tax, with discount |\n| `priceNetto` | double | yes | | Net price |\n| `priceBrutto` | double | yes | | Gross price |\n| `measureCode` | integer | | | Unit of measure code |\n| `measureName` | string | yes | | Unit of measure |\n| `customized` | char | yes | | Modified (`Y`\u002F`N`) |\n| `sort` | integer | | | Sort order |\n| `type` | integer | yes | | Product type — the same value as the product's `type` in `GET \u002Fv1\u002Fcatalog-products\u002F:id`: `1` — simple product, `3` — parent product with variations, `7` — service |\n| `storeId` | integer | yes | | Warehouse ID |\n| `taxName` | string | yes | | Tax name. Present only in the dictionary, never in product rows. In a write request body it is rejected with `400 INVALID_PARAMS` |\n| `ownerId` | integer | yes | | Owner (item) ID |\n| `ownerType` | string | yes | | Owner type |\n| `priceAccount` | double | yes | | Price in the reporting currency |\n| `xmlId` | string | yes | | External code of the row |\n\n## Response example\n\nThe example shows 6 of the 25 fields (24 product-row field names plus the deprecated `discountSum` alias). The full list is in the table above.\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": { \"type\": \"integer\", \"isRequired\": false, \"isReadOnly\": true, \"isImmutable\": false, \"isMultiple\": false, \"isDynamic\": false, \"title\": \"ID\", \"description\": \"Row identity. Read-only as an attribute, and NOT a handle for editing: PUT \u002Fproducts does not preserve it — a row whose fields change comes back with a new id even if the previous one was sent. To edit a row and keep its id use PATCH \u002Fproducts\u002F{rowId}.\" },\n    \"ownerId\": { \"type\": \"integer\", \"isRequired\": false, \"isReadOnly\": true, \"isImmutable\": true, \"isMultiple\": false, \"isDynamic\": false, \"title\": \"Owner ID\" },\n    \"ownerType\": { \"type\": \"string\", \"isRequired\": false, \"isReadOnly\": true, \"isImmutable\": true, \"isMultiple\": false, \"isDynamic\": false, \"title\": \"Owner type\" },\n    \"productId\": { \"type\": \"integer\", \"isRequired\": false, \"isReadOnly\": false, \"isImmutable\": false, \"isMultiple\": false, \"isDynamic\": false, \"title\": \"Product\" },\n    \"price\": { \"type\": \"double\", \"isRequired\": false, \"isReadOnly\": false, \"isImmutable\": false, \"isMultiple\": false, \"isDynamic\": false, \"title\": \"Price\" },\n    \"priceExclusive\": { \"type\": \"double\", \"isRequired\": false, \"isReadOnly\": true, \"isImmutable\": false, \"isMultiple\": false, \"isDynamic\": false, \"title\": \"Price excluding tax, with discount\" }\n  }\n}\n```\n\n> **About `id`.** An `id` supplied in the `items` array of `PUT \u002Fv1\u002Fitems\u002F:entityTypeId\u002F:id\u002Fproducts` does not guarantee that the row keeps its previous identifier: an unchanged row gets the same `id` even without this field, while a changed row gets a new one. For targeted editing, use `PATCH \u002Fv1\u002Fitems\u002F:entityTypeId\u002F:id\u002Fproducts\u002F:rowId`.\n\n## Error response example\n\n400 — `entityTypeId` in the path is not a positive integer:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_DYNAMIC_PARAM\",\n    \"message\": \"Invalid entityTypeId: must be a positive integer\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_DYNAMIC_PARAM` | `entityTypeId` is not a positive integer or is reserved (1, 2, 3, 4, 7, 31) |\n| 403 | `SCOPE_DENIED` | The API key does not have the `crm` scope |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is not passed |\n| 401 | `TOKEN_MISSING` | The API key has no configured tokens |\n| 429 | `RATE_LIMITED` | Rate limit exceeded: 300 requests per minute per portal. All API keys of the portal share one limit. The current limit is returned in the `x-ratelimit-limit` header. Retry after the delay in the `Retry-After` header |\n\nFor the full list of common API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [Product rows](\u002Fdocs\u002Fentities\u002Fitems\u002Fproducts-get)\n- [Add a product](\u002Fdocs\u002Fentities\u002Fitems\u002Fproducts-add)\n- [Set products](\u002Fdocs\u002Fentities\u002Fitems\u002Fproducts-set)\n- [Item fields](\u002Fdocs\u002Fentities\u002Fitems\u002Ffields)\n","2026-11-10",{},1794739384204]