Change notification with seller ID and seller SKU ID

Sends a seller notification to the VTEX marketplace about a SKU suggestion, which can be either a new suggestion or an update. For example, a seller SKU previously approved by the marketplace may have had price or inventory changes.

The main information sent by the seller is its identification (sellerId) and the SKU binding code (sellerSkuId), both passed as path parameters. This request doesn't require a request body.

ℹ This path is an updated version of /api/catalog_system/pvt/skuseller/changenotification/{sellerId}/{sellerSkuId}.

Example

Let's say your seller has the ID 123 in the marketplace, and you want to inform the marketplace that there has been a change to the SKU with ID 700.

In this case, you would replace the sellerId parameter with the value 123, and the sellerSkuId parameter with the value 700. The URL would be the following:

https://accountName.vtexcommercestable.com.br/api/sku-binding/pvt/skuseller/changenotification/123/700

Response codes

The following response codes are possible:

• 200: The SKU whose ID was informed in the URL already exists in the marketplace and was found. The marketplace can now proceed with a fulfillment simulation in order to get updated information about this SKU's inventory and price.
• 403: Failure in the authentication.
• 404: The SKU was not found in the marketplace. The body of the response, in this case, should follow this format: "Seller StockKeepingUnit {{skuId}} not found for this seller id {{sellerId}}. This means that the seller can now proceed with sending an offer to the marketplace in order to suggest that this SKU is sold there.
• 429: Failure due to too many requests.

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:

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.