February 2, 2015
Single purpose API
Sorry, No followers
This article discusses how OTT (Over The Top) rivlas are cutting into Telelcom Firm profits as their services grow. OTT rivals do not represent the end for Telecom firms, as implementing APIs into their business models could open up untapped revenue sources.
Travel reservation site Expedia starting working on its Expedia API back in 2009, according to the changelog. It has three APIs, covering hotels, flights and cars. Don't be shy. Expedia has been expecting you. The Expedia developer site has all the warmth and care of a fine bed and breakfast. They clearly want to invite you in, make you comfortable, and get your development project of the ground. Though they do have a couple hoops to jump through, as well.
If there is a segment that is ripe for integration it is travel. APIs in the travel segment have been around for a very long time. In fact, some of the earliest APIs are based on Electronic Data Interchange, which dates back to the 1960s. Granted many of these connections are highly complex enterprise only integrations, it is a history that should bode well for modern day integrations, should it not? Despite a long history of interconnectedness, much of the travel space still remains behind closed doors. The major global distribution systems, represented by Sabre, Travelport, and Amadeus all offer powerful APIs of their own, but their commercial requirements tend to be out of the league of most application developers. In spite of the limitations the travel industry has effectively self imposed, there still exists many opportunities to monetize sites using travel APIs. There are several types of APIs available in the travel space. Most are transactional and some are content driven. Let's take a look a broad categorization of available travel APIs.