v50

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

SKU file

Reorder SKU files

Defines SKU images positions. For the request to work properly, you must send all SKU images positions. For example, if the SKU has 10 images, you have to send in the request all file IDs and positions. There is no need to send them in order, but all positions must be defined.

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:

Product	Category	Resource
Catalog API	General	Edit Product

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.

put/api/catalog/pvt/stockkeepingunit/{skuId}/file/reorder

Path parameters

skuIdinteger required

Example:3101188

SKU unique numerical identifier.

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

Idinteger required

SKU image file unique identifier.

Positioninteger required

The number of the position you wish to display the image in the storefront, where 0 corresponds to the first position, 1 to the second position, and so on.

Example request

[
  {
    "Id": 6541
  }
]

v50