---
title: "Get all SKU attributes"
method: GET
path: "/api/catalog/pvt/stockkeepingunit/{skuId}/attribute"
tags: ["SKU attribute"]
---

# Get all SKU attributes

`GET /api/catalog/pvt/stockkeepingunit/{skuId}/attribute`

Retrieves all SKU attributes, which are informative fields defined at the SKU level that don't create new SKU variants. They only accept open-text values.

>ℹ️ These attributes are indexed and can be retrieved in the `attribute` field of the search payload. However, they cannot be used as search filters or searched directly in the storefront. In the storefront context, they are available in the `additionalProperty` field and can be differentiated from regular specifications by the `valueReference` field, which contains `ATTRIBUTE` instead of `SPECIFICATION`.

## 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 API | General | **View Product** |

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.

## Path parameters

- `skuId` integer, required

## Headers

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

## Response `200`

OK

- object[]
  - `Id` integer — SKU attribute unique numerical identifier.
  - `SkuId` integer — SKU's unique numerical identifier.
  - `SpecificationName` string — Name of the SKU attribute.
  - `SpecificationValue` string — Value of the SKU attribute.
  - `IsVisible` boolean — Defines if the attribute is visible on the store (`true`) or not (`false`).

## Changes

- **2026-03-19** `b33ae94b7e62` — 1 info
  - endpoint added
- **2026-03-19** `afc172650ba2` — 1 breaking
  - api path removed without deprecation
- **2026-03-12** `a85881b17f55` — 2 info
  - api tag `SKU attribute` added
  - api tag `Unstructured SKU attribute` removed

[Change history](https://skmtc.dev/vtex/apis/catalog-api/changes/api/catalog/pvt/stockkeepingunit/:skuId/attribute/get.md)

---

[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)