Wednesday 24 April 2013

What Amazon’s API Changes Mean for Us

Amazon has again modified the product pricing data they share with us.  We assumed that, although this was going to take place on October 25th, Amazon’s statement that these changes would not be mandatory until February 2012 meant we could continue along as usual and try to find a workaround before February.  Wrong!  It turns out that Amazon has retroactively applied these changes to all existing versions of their API (data source), and that means we’ve had to take some measures to protect our database from this “lesser” data while we figure out how to deal with it.

So, for now — and we really hope this is temporary — Amazon Germany and Amazon Japan support have been disabled.  You can still view our existing data, but no new data will be consumed until we find a workaround.  All other Amazon locales will continue working normally, with one caveat: due to heightened traffic, no new products will be added to our database until we can expand our updating capacity.

We are working with Amazon to resolve all of these issues, but it might take some time before we are back to running at full steam.  We are sincerely sorry that this happened, but that’s how it goes when you rely on another company for data: you take what you can get and roll with the punches.  And, due to our immense respect for Amazon, we want to avoid screen scraping if at all possible, so using their API is the only way for us to acquire product data.

Thanks for understanding.

Source: http://blog.camelcamelcamel.com/post/12046429331/what-amazons-api-changes-mean-for-us

Note:

Delta Ray is experienced web scraping consultant and writes articles on Extract Amazon Website, Product Details Scraping, Amazon Product Scraping, Linkedin Email Scraping, Screen Scraping Services, Yelp Review Scraping and yellowpages data scraping etc.

No comments:

Post a Comment