Loading Profile...
Twitter,
Facebook, or email.
Would it be possible to release an API for permitting third party developers to contribute interfaces between camelcamelcamel and shopping sites? For example, if I wanted price history and alters for Harborfreight.com, I could develop a module for retrieving the necessary data from their site and supply it to you, which you could then audit and deploy.
Or is the act of adding support for a shopping site as much about politics and negotiating access as it is technical?
I’m
indifferent
developer API for adding support for new sites
-
In theory, I like this idea. But, as you mentioned in your closing sentence, reality may be a bit different.
Some things we'd have to consider: how is the data being collected? If the developer using our API is screen scraping, that exposes us to its maintenance (including potential blockage by the retailer site). If the data is coming from the retailer's API, what are the terms of service associated with that? Are we allowed to display their data on any domain, or does it have to be on a site dedicated solely to that retailer?
These are just a couple of the problems we've already faced. I'd much rather have one Camel site, for example, but Amazon (and most other retailers) prefers that you dedicate your site solely to them.
To reference your other Idea, this is why I like the Shopzilla approach. All of the retailers come in from one data source, and we aren't restricted by each retailer's terms of service (only Shopzilla's); both of which make it easier for us to have one site that provides Camel functionality to tons of retailers.Comment -
EMPLOYEE
