Amazon Hacks

Why Expose an API?

Amazon made a radical break from conventional business thinking when they released their Web Services API in July of 2002. Instead of tightly controlling their product database—one of their biggest assets—they decided to open a direct gateway allowing developers to tinker and experiment. Not only does this direct access make all of their product information available for other applications, it’s completely free for anyone to use—in fact, with the Amazon Associates program, they’ll pay you to use it. It sounds counterintuitive on the surface; after all, with this sort of access, someone could just duplicate most of Amazon.com’s functionality with a different look and feel. They could even host it on their own web site! Call it “syndicated e-commerce.” To fully understand the API, it’s important to understand why Amazon released it in the first place.

As Amazon grew, they became one of the largest places to shop on the Web. They also became one of the largest sources of information about products on the Web. Their product information, customer reviews, sales rank information, and many other supporting bits of data became valuable in its own right. Developers started screen-scraping this information to build their own applications. Most large sites like Amazon frown on screen scraping because it uses valuable server resources in ways they didn’t intend. But instead of fighting these developers and the potential audience they bring along with them, Amazon helped them ...