[Idea] need of new modern webservice #35694
Replies: 4 comments
-
I decided to create a mobile application based on a web service and unfortunately it was a difficult process. While I use the link_rewrite trick to download product photos, I have no idea how to download product attributes. Does anyone have an idea on how to associate the id_product_attribute from the stock_availables resource with product_option_values? In the case of combinations, I use the combinations resource, but I have no idea how to implement it in the case of simple products. I need available sizes of clothes -> click on the size to select the appropriate id_product_attribute. |
Beta Was this translation helpful? Give feedback.
-
According to the devs, the new API Platform is coming in v9: It will have an OpenAPI spec, so you can (auto) generate the code bindings in whatever language you want. |
Beta Was this translation helpful? Give feedback.
-
Hello @makhloughi Web services are not ready by default to help you create a feature-rich mobile application, although we do have great documentation for them: https://devdocs.prestashop-project.org/8/webservice/. How to extend it: https://devdocs.prestashop-project.org/8/modules/concepts/webservice/ If you want to avoid using web services and search for something better for your needs, you might want to look at https://docs.vuestorefront.io/prestashop/. And, as @silentyak mentioned, with the upcoming release of version 9, PrestaShop's API is about to enter a new era, with API Platform-based solution :) |
Beta Was this translation helpful? Give feedback.
-
you are right that's extendable, but it's very resource draining to work with such API which requires to query the World to get a useful product object. |
Beta Was this translation helpful? Give feedback.
-
The problem
problem is non-well and non-useful formatted. actually there is no way to get public image url of a product. most useful fields are missing and for getting information about a product we need deep dive into multiple nested requests instead of having them in one object. this structure and thinking method belongs to under 2000!
what if we want to create a third-party program or mobile application for our website? is that right for viewing a product we make 4-5 or more requests to the server? also serve images not-optimized and with dynamic urls? where are using benefits of caching and webserver performance? we need a token to view images in third party app. is that safe and have good performance? absolutely not.
i studied PRs and issues. original developers like their old XML/JSON formatted API as it is and deny any changes to it and saying not to break old api. ok. then bring new webservice in a complete new endpoint and keep that junk in your code for backward compatibility. please do that, or say something useful, i don't think you have that!
The solution
create a simple json api for getting products info at least. with complete structure and not to make 3-4 requests to get informations about a product ,images of it or attributes of it.
there is noooooooooooooo well documentation about this.
Alternatives
No response
Additional context
No response
Do you plan to work on this subject?
Beta Was this translation helpful? Give feedback.
All reactions