July 8, 2019
Related Articles (803)
Should you let people scrape data from your site or offer a web service API instead? This is one of the classic arguments for offering an API: to get better control over how your data is accessed and who gets access. A recent news story about Flybe, Europe's largest independent regional airline carrier, demonstrates a case where this was the main driver for creating an API. For Flybe, having third party service and applications access their booking engine is very important to them, but they want to make it more structured and reliable.
Innovation in web service APIs is not always technical, sometimes it's about money. Such is the case with Yahoo's announcement that later this year they will begin charging for usage of BOSS (Build your Own Search Service), their search web service for developers. Given that search revenue is typically ad-driven, and that advertising doesn't typically mesh with APIs, this has meant that search APIs have been one of the most challenging classes of APIs for providers to monetize. So it's notable to see how Yahoo has chosen to tackle this: via a 'utility' pricing model, somewhat akin to how infrastructure services like Amazon Web Services charge by usage.