---
title: "Get SKU by reference ID"
method: GET
path: "/api/catalog/pvt/stockkeepingunit"
tags: ["SKU"]
---

# Get SKU by reference ID

`GET /api/catalog/pvt/stockkeepingunit`

Retrieves information about a specific SKU by its `RefId`.

## 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 | Content | **SKUs** |

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.

## Query parameters

- `RefId` string, required

## Headers

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

## Response `200`

OK

- object
  - `Id` integer — SKU unique identifier.
  - `ProductId` integer — ID of the product associated with this SKU.
  - `IsActive` boolean — Defines if the SKU is active (`true`) or not (`false`).
  - `ActivateIfPossible` boolean — When set to `true`, this attribute will automatically update the SKU as active once associated with an image or an active component.
  - `Name` string — SKU name, meaning the variation of the previously added product. For example: **Product** - _Fridge_, **SKU** - _110V_.
  - `RefId` string — Reference code used internally for organizational purposes. Must be unique. Required only if `Ean` is not informed, but can be used alongside `Ean` as well.
  - `Ean` string — EAN code. Required only if `RefId` is not informed, but can be used alongside `RefId` as well.
  - `PackagedHeight` number — Height used for shipping calculation.
  - `PackagedLength` number — Length used for shipping calculation.
  - `PackagedWidth` number — Width used for shipping calculation.
  - `PackagedWeightKg` integer — Weight used for shipping calculation, in the measurement unit [configured in the store](https://help.vtex.com/en/tutorial/filling-in-system-settings--tutorials_269), which by default is in grams.
  - `Height` number — SKU real height.
  - `Length` number — SKU real length.
  - `Width` number — SKU real width.
  - `WeightKg` number — Weight of the SKU in the measurement [configured in the store](https://help.vtex.com/en/tutorial/filling-in-system-settings--tutorials_269), which by default is in grams.
  - `CubicWeight` number — [Cubic weight](https://help.vtex.com/en/tutorial/understanding-the-cubic-weight-factor--tutorials_128).
  - `IsKit` boolean — Defines whether the SKU is made up of one or more SKUs (part of a kit) (`true`) or not (`false`). Must be enabled if you are adding a kit. Once activated, this definition cannot be reverted.
  - `CreationDate` string — Date and time of the SKU's creation.
  - `RewardValue` number — Credit that the customer receives when finalizing an order that includes the SKU. By filling this field out with `1`, the customer receives credit on the site in the selected currency, e.g. U$ 1.
  - `EstimatedDateArrival` string, nullable — SKU estimated arrival date in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format, when the product is on pre-sale. You must take into consideration both the launch date and the freight calculation for the arrival date.
  - `ManufacturerCode` string — Identifier provided by the manufacturers to identify their product. This field should be filled in if the product has a specific manufacturer's code.
  - `CommercialConditionId` integer — Commercial condition ID, used to define SKU specific promotions or installment rules. In case of no specific condition, use `1` (default value). This field does not accept `0`. Learn more at [Registering a commercial condition](https://help.vtex.com/tutorial/registering-a-commercial-condition--tutorials_445).
  - `MeasurementUnit` string — Measurement unit. This field should only be used when it is necessary to convert the unit of measure for sale. For example, if a product is sold in boxes, but customers want to buy per square meter (m²). In common cases, use `"un"`.
  - `UnitMultiplier` number — Multiple number of SKU. If the multiplier is 5.0000, the product can be added in multiple quantities of 5, 10, 15, 20, onward.
  - `ModalType` string, nullable — Links an unusual type of SKU that needs special transportation, such as meat, glass, or a mattress, to a carrier specialized in delivering it. This field should be filled in with the name of the modal (e.g. "Chemicals" or "Refrigerated products"). To learn more about this feature, read our articles [How the modal works](https://help.vtex.com/en/tutorial/how-does-the-modal-work--tutorials_125) and [Setting up modal for carriers](https://help.vtex.com/en/tutorial/configure-modal--3jhLqxuPhuiq24UoykCcqy).
  - `KitItensSellApart` boolean — Defines if kit components can be sold apart.
  - `Videos` string[] — Videos URLs.

---

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