Mashups using the same API (3095)
Locate and connect to 3,700+ Tim Hortons / Coldstone Creamery stores across Canada and United States. Supports click-to-call. Smartphone friendly.
User driven search where users contribute listings, reviews, pictures, tags, and more. Toronto is first city setup, includes mapped traffic conditions.
Mashup of Google Maps and YouTube videos.
Planning a trip, whether just down the road or into the next city, normally revolves around the distance of the desired location. It's common practice to search for the distance between two points on a map, then take a rough guess as to how long it will actually take to get there. But we all know that distance isn't the only factor to consider. What about mode of transport, peak traffic hours or alternate routes? All these can dramatically affect how long it actually takes to get to your destination. This post will discuss how iGeolise's Travel Time and the Travel Time API changes the way people search and the results that are produced.
The Earthquake Data Portal API provides event information in both SOAP and REST-style services. For SOAP, the information is provided in QuakeML format. For REST, information is in either QuakeML or JSON formats. Users can do Event Searches, review Latest Events and look at Event Details. Data on seismic waveforms and their velocity are also provided, including the ability to predict arrival times and locations after they have been detected. The API will identify the data providers within the Seismolink network.
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.
||The Reise API offers integration with Ruter's journey planner service. GET methods are used for requests. Ruter is a Norway based transportation firm that provides information about several related...||Travel||09.19.2016|
||BeMyGuest is a booking platform specialized in Asian destinations. The API offers interface options such as locations, supported languages and currencies, product types and categories, and default...||Travel||09.13.2016|
City of Chicago Divvy Trips
||The City of Chicago Divvy Trips API supports the development of apps for individual divvy bike sharing trips. It offers users access to detailed descriptions of the origins, destinations, and...||Transportation||08.29.2016|
Harvard University CS50 Courses
||This API provides a RESTful interface and allows you to request data programmatically from CS50 Courses in JSON, JSONP, or XML format. At least once per day, CS50 synchronizes with the Courses of...||Education||08.26.2016|
Harvard University CS50 Food
||This API provides a RESTful interface and allows you to retrieve Harvard University Dining menus in JSON, JSONP, or XML. Each night, CS50 screen-scrapes nutritional facts, menus, and recipes from...||Food||08.26.2016|