Magento 2 - REST API PUT product

Magento 2 - REST API PUT product

July 21, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento 2 - REST API PUT product

Fixing Magento 2 REST API PUT Product Issue: Updating Multiple Websites

Dear developer,

I understand your frustration with updating products via the Magento 2 V1 REST API. The issue you’re facing is quite common—only the default website values are updated when using the PUT method, even though you’ve manually linked the product to specific websites.

Understanding the Problem

The root of this problem lies in how Magento handles website associations with products. When you create a product via /V1/products, it’s initially associated only with the default website (website ID 0). Even if you subsequently link the product to other websites using /V1/products/{product_id}/websites (POST), Magento doesn’t automatically update these associations when you use PUT /V1/products/{product_id}.

This means that, by default, a PUT request updates only the attributes related to the product itself, not its website-specific data. The JSON format you’re using is correct for updating basic product attributes like SKU, name, and price. However, it’s missing the website-specific data needed for the custom_attributes section.

A Step-by-Step Solution

To resolve this issue, we need to manually include the necessary website data in our PUT request. Here’s how you can do it:

  1. Retrieve the current product attributes: Before updating, fetch the current product data using a GET /V1/products/{product_id} call. This will give you a complete JSON representation of the product, including its website-specific custom_attributes.

  2. Manually update the required websites: In your PUT request, include only the website IDs that need to be updated in the custom_attributes array. Remove any other attributes (like SKU or name) from this section.

Here’s an example of how you might structure a PUT /V1/products/{product_id} request:

{
  "product": {
    "sku": "123456",
    "name": "D4D0123299",
    "price": 21,
    "type_id": "simple",
    "custom_attributes": [
      {"attribute_code":"website_ID_1", "value":[{"website_id":1,"value":1}}],
      {"attribute_code":"website_ID_2", "value":[{"website_id":2,"value":0.5}]}
    ],
    "extension_attributes":{
      "stock_item":{
        "use_config_manage_stock": 1
      }
    }
  }
}

In this example, website_ID_1 and website_ID_2 are custom attributes that correspond to the website-specific prices for websites with IDs 1 and 2 respectively. The values [{"website_id":ID,"value":PRICE}] map each website ID to its corresponding price.

Best Practices

Remember these best practices when working with Magento’s REST API:

  • Always fetch the current product data before updating.
  • Be careful not to include extraneous attributes in your PUT request, as they can cause conflicts or errors.
  • If you’re working with complex products (like configurable or grouped products), ensure that you update the child items separately using /V1/products/{parent_sku}/children (GET and POST methods).

Conclusion

While Magento 2’s REST API has a lot of advantages, it does require some careful handling when dealing with multi-website products. By manually including the necessary website data in your PUT requests, you can ensure that all product attributes are properly updated across all linked websites.

Remember, if you need more advanced solutions or find yourself stuck, don’t hesitate to reach out to a professional Magento development team like Laravel Company. We’re always ready to help with your eCommerce needs!

Stay tech-savvy!

Magento 2 Catalog API Pricing

Our network