There are two ways. First is not efficient, second is better. First is available out of the box, second not. So, first: You can make a GET request and get all products from your store. Then find the specified one, take its ID and use to GET by ID request. It will show you the whole JSON for product update.
Better option is to extend API with a plugin and add PUT request which will allow you to update only particular fields from product. Thank you for suggestion, we will add this request out of the box. I've added it to our roadmap, here is an work item.
OK, so we’re trying the simple solution first: Update using POST to our store API http://[OUR_DOMAIN]/odata/product , with similar JSON as received from GET.
However, the POST gives a 400 Bad Request result. We have not implemented SSL yet so just using http.
I have looked at the API source code and understand that the product’s Id should be specified in the JSON, and not be part of the url, and that it needs to be POST and not PUT.
Authorization is OK using Bearer, and have checked that JSON syntax is valid. I have tried to “wrap” the JSON in different ways with curly braces and labels, but have not been able to get this to work.
I’m pasting the raw request and response from Fiddler below. Any suggestions that can help us solve this are appreciated.
Note: I have not included the contents of the Categories / Manufacturers arrays (etc) in the bottom in the request.
I tried to send your request and I had the same problem. I found the issue, it's a problem with date format. It's unsupported by OData. It's some kind of bug, we need to fix it and I made a task here. As a workaround, you can use supported date format, I compare them below: My format: "CreatedOnUtc": "2019-03-16T12:37:49.234+01:00", Your format: "UpdatedOnUtc": "2019-03-16T06,03,28.991Z",