We are a team of developers currently working on a social shopping site, and our site is 6-9 months from alpha stage. We are interested in integrating shopping.com API into the site, but before allocating resources on working on the integration, there are several questions that we might need further clarification.
1) There is a policy for the API program stating that content returned through the REST API call should not be cached. For our usage, our implementation allows our site's user to "like" or "add to favorite" certain items so that they can return and view it later. Such items will appear in one of the pages of their user profile page. In this case, we would need to cache a copy of the product that the user "favorited" or "added to wishlist", mainly due to latency reason. For example, if a user has 20 items favorited, it is easier to cache a copy of the product info, and for each product , provide the correct link that will redirect them to the i product on shopping.com in order to complete the purchase. Our intention is purely on a technical perspective and to improve the user experience for those using our site. Does such caching comply to the usage policy?
2) Our team is not based in US or Canada, and we are a development team in the APAC region, is the API program open to developers in other countries other than US?
Hi, shopping.com support team.
We are a team of developers currently working on a social shopping site, and our site is 6-9 months from alpha stage. We are interested in integrating shopping.com API into the site, but before allocating resources on working on the integration, there are several questions that we might need further clarification.
1) There is a policy for the API program stating that content returned through the REST API call should not be cached. For our usage, our implementation allows our site's user to "like" or "add to favorite" certain items so that they can return and view it later. Such items will appear in one of the pages of their user profile page. In this case, we would need to cache a copy of the product that the user "favorited" or "added to wishlist", mainly due to latency reason. For example, if a user has 20 items favorited, it is easier to cache a copy of the product info, and for each product , provide the correct link that will redirect them to the i product on shopping.com in order to complete the purchase. Our intention is purely on a technical perspective and to improve the user experience for those using our site. Does such caching comply to the usage policy?
2) Our team is not based in US or Canada, and we are a development team in the APAC region, is the API program open to developers in other countries other than US?
We look forward for your reply.
-Tommy
Senior Software Developer.
Tags