v50

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

Change notification with seller ID and seller SKU ID

⚠️ Check out the updated version of this endpoint in our SKU Bindings API documentation. If you are doing this integration for the first time, we recommend that you follow the updated documentation.

The seller is responsible for suggesting new SKUs to be sold in the VTEX marketplace and also for informing the marketplace about changes in their SKUs that already exist in the marketplace. Both actions start with a catalog notification, which is made by this request.

With this notification, the seller is telling the marketplace that something has changed about a specific SKU, like price or inventory, or that this is a new SKU that the seller would like to offer to the marketplace.

There are two information expected by the marketplace in this request: the sellerId, which identifies the seller, and the sellerSkuId, which identifies the binding of the seller with the SKU.

Both information are passed through the request URL. The body of the request should be empty.

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
CatalogMarketplaceSeller SKUs

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_system/pvt/skuseller/changenotification/{sellerId}/{sellerSkuId}

Path parameters

sellerIdstring required
Example:101

ID that identifies the seller in the marketplace. It can be the same as the seller name or a unique number. Check the Sellers management section in the Admin to get the correct ID.

sellerSkuIdstring required
Example:1

ID of the binding of the seller with the SKU.

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.

Response

No Content