November 4, 2016
Sorry, No followers
View all 1385 Related Articles
Related Articles (1385)
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.
CAD tools have assisted architects and engineers in product development for decades. Despite their widespread adoption and usefulness, two aspects of CAD tools remain pretty consistent across the CAD landscape: high costs and proprietary software. Sunglass aims to alleviate both pains of traditional CAD tools through the Sunglass API. Sunglass co-founder and CEO, Kaustuv DeBiswas, asserts: "We don't want to compete on a feature-by-feature basis" with traditional CAD tools. Rather, the Sunglass API constitutes a collaboration tool that serves "as the bridge for sharing 3D product design data and for managing version control for engineers and colleagues working across different systems."