v50

latestOpenAPI 3.0.0raw.githubusercontent.com2026-05-29208421.4 MB
Specification group

Create specification group

Create a specification group.

⚠️ It is also possible to create a specification Group by using an alternative legacy route: /api/catalog_system/pvt/specification/group.

Permissions

Any user or API key must have at least one of the appropriate License Manager resources 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:

ProductCategoryResource
CatalogContentGroups

There are no applicable predefined roles for this resource list. You must create a custom 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.

❗ To prevent integrations from having excessive permissions, consider the best practices for managing API keys when assigning License Manager roles to integrations.

post/api/catalog/pvt/specificationgroup

Headers

Content-Typestring required

Type of the content being sent.

Acceptstring required

HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.

Request body

CategoryIdinteger required

Category ID.

Namestring required

Specification group name.

Example request

{
  "CategoryId": 1,
  "Name": "Sizes"
}

Response

OK

Idinteger

Specification group ID.

CategoryIdinteger

Category ID.

Namestring

Specification group name.

Positioninteger

Store Framework - Deprecated. Legacy CMS Portal - specification Group Position.