The serialized field does not seem to be supported in an API call. It appears to be hit and miss as to which fields are supported. categoryID, archived, manufacturerSku and probably many other are supported. Here's an example of a call that works for me in Postman:
Lucien, i'm using this field serialized now for updating my webshop throught the api, if on -> it means the item is online.. will it be deleted in the future and should i look for another solution?
tiegos
Member Posts: 12
3 comments
The serialized field does not seem to be supported in an API call. It appears to be hit and miss as to which fields are supported. categoryID, archived, manufacturerSku and probably many other are supported. Here's an example of a call that works for me in Postman:
https://api.lightspeedapp.com/API/Account/[accountID]/Item.json?load_relations=["ItemShops"]&categoryID=11&archived=falseLance Muzslay
getopt.io
Optimal Inventory & Operations
Hi @tiegos and @lancemuz,
Thank you for reaching out to us.
The
serializedandserialized_assemblyare deprecated since 2016. This is all in our documentation https://developers.lightspeedhq.com/retail/endpoints/Item/Lucien, i'm using this field serialized now for updating my webshop throught the api, if on -> it means the item is online.. will it be deleted in the future and should i look for another solution?