Magento 2 Rest API Can't Remove Category ID's from product

Magento 2 Rest API Can't Remove Category ID's from product

August 24, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento 2 Rest API Can't Remove Category ID's from product

Solving Category ID Removal Issues in Magento 2 REST API

As a senior developer working on e-commerce platforms like Magento, I often encounter challenges related to API calls for product updates. One common issue is the inability to remove category IDs from products using the DELETE method in the Magento 2 REST API.

Let me guide you through solving this issue step by step, as I’ve faced and resolved similar problems in my projects at Laravel Company.

Understanding the Problem

The code snippet provided is attempting to delete a category link from a product via a DELETE request. While the API call returns true, there’s no visible change either on the backend or the live website.

This issue often stems from incorrect data structures in the request payload or misunderstandings about how Magento handles product-category relationships.

The Magento 2 Product-Category Association Structure

In Magento, products and categories are associated through a many-to-many relationship managed by the catalog_category_product table. When you add a category to a product, Magento inserts an entry into this table with both the product ID and category ID as foreign keys.

To remove a category from a product, you must delete the corresponding record from this table. The DELETE request provided attempts this, but let’s analyze why it fails:

  1. Incorrect Category Links Format: In your payload, category_links is an array of objects containing position, category_id, and no link_type. Magento requires a link_type field for proper execution.

  2. DELETE vs PATCH Conflict: You’re using the DELETE HTTP verb, which typically expects a resource to be completely removed. However, in this context, you want to update an existing resource (the product), so a PATCH request would be more appropriate.

The Correct Magento 2 REST API Approach

To resolve this issue, you need to send a PATCH request with the correct payload structure:

{
 "product": {
   "sku": "MRO2222",
   "status": "0",
   "category_links": [
     {
       "link_type": "simple",
       "position": 100,
       "category_id": 8
     }
   ]
 }
}

In this updated payload:

  • I’ve added the link_type field set to "simple". This is required for category association in Magento.
  • The category_links array contains a single object with the desired category ID.

Best Practices and Troubleshooting Tips

  1. Curl vs Postman: Use tools like Postman or Curl to test your API calls directly. They provide better visibility into response headers, error messages, and network activity compared to PHP code.

  2. Error Messages: Pay close attention to the error message returned by Magento. It often provides valuable insights into what went wrong in your request.

  3. API Documentation: Always refer to official Magento 2 REST API documentation for accurate information on endpoint usage and payload structures.

Conclusion

Removing category IDs from products via Magento’s REST API requires a nuanced understanding of the underlying data structure and proper use of HTTP verbs. In this case, a PATCH request with the correct category_links format resolves the issue effectively.

Remember to always validate your API calls using tools like Postman or Curl, and leverage Magento’s official documentation for accurate guidance.

At Laravel Company, we regularly tackle such e-commerce challenges for our clients. If you need expert assistance with Magento 2 development or any other PHP framework, feel free to reach out!

Magento 2 Catalog Database API

Our network