---
title: "Update specification field"
method: PUT
path: "/api/catalog_system/pvt/specification/field"
tags: ["Specification field"]
---

# Update specification field

`PUT /api/catalog_system/pvt/specification/field`

Updates a specification field in a category. 
>⚠️ This is a legacy endpoint. We recommend using [Update specification](https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/stockkeepingunit/-skuId-/specification?endpoint=put-/api/catalog/pvt/stockkeepingunit/-skuId-/specification) instead.

## Permissions

Any user or [API key](https://developers.vtex.com/docs/guides/api-authentication-using-api-keys) must have at least one of the appropriate [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) to be able to successfully run this request. Otherwise they will receive a status code `403` error. These are the applicable resources for this endpoint:

| **Product** | **Category** | **Resource** |
| --------------- | ----------------- | ----------------- |
| Catalog | Commercial | **SKU management** |

There are no applicable [predefined roles](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy) for this resource list. You must [create a custom role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role) and add at least one of the resources above in order to use this endpoint. To learn more about machine authentication at VTEX, see [Authentication overview](https://developers.vtex.com/docs/guides/authentication).

>❗ To prevent integrations from having excessive permissions, consider the [best practices for managing API keys](https://help.vtex.com/en/tutorial/best-practices-api-keys--7b6nD1VMHa49aI5brlOvJm) when assigning License Manager roles to integrations.

## Headers

- `Content-Type` string, required
- `Accept` string, required

## Request body

- object
  - `Name` string, required — Specification field ID.
  - `CategoryId` integer, nullable, required — Category ID.
  - `FieldId` integer, nullable, required — Specification field ID.
  - `IsActive` boolean, required — Enables(`true`) or disables (`false`) the specification field.
  - `IsRequired` boolean, required — Makes the specification field mandatory (`true`) or optional (`false`).
  - `FieldTypeId` integer, required — Specification field type ID.
  - `FieldValueId` integer, nullable — Specification field value ID.
  - `Description` string, nullable, required — Specification field description.
  - `IsStockKeepingUnit` boolean, required — If `true`, it will be added as a SKU specification field. If `false`, it will be added as a product specification field.
  - `IsFilter` boolean, required — Store Framework - Deprecated. Legacy CMS Portal - To allow the specification to be used as a facet (filter) on the search navigation bar.
  - `IsOnProductDetails` boolean, required — Store Framework - Deprecated. Legacy CMS Portal - If the specification is visible on the product page.
  - `Position` integer, required — Specification field position.
  - `IsWizard` boolean, required — Deprecated field.
  - `IsTopMenuLinkActive` boolean, required — Store Framework - Deprecated. Legacy CMS Portal - To make the specification visible in the store's upper menu.
  - `IsSideMenuLinkActive` boolean, required — Store Framework - Deprecated. Legacy CMS Portal - To make the specification field clickable in the search navigation bar.
  - `DefaultValue` string, nullable, required — Specification field default value.
  - `FieldGroupId` integer, required — Specification field group ID.
  - `FieldGroupName` string, required — Specification field group name.

## Response `200`

OK

- integer — Specification field ID.

---

[API](https://skmtc.dev/vtex/apis/catalog-api.md) · [All operations](https://skmtc.dev/vtex/apis/catalog-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/vtex/catalog-api/revisions/ba9fbd1b771f/schema)