Posts From Category: api

This article is published on Medium.

If you have a traditional RESTful API then you may already be using an API management system such as Apigee, 3Scale, Kong or Amazon API Gateway. Using an API management platform has several advantages such as:

• Managing API authentication
• Analytics and logging
• Caching and traffic manipulation (e.g. transforming JSON to XML or adding a CORS header)
• Developer portals and interactive documentation
• Ability to monetize an API
• An additional layer of security (such as API request throttling)

Read More

This article is published on the Triathlon Developers documentation.

For the upcoming Olympic Games in Rio we decided to use the Triathlon API to build an application so users could quickly compare the performances of any two athletes in the start lists. In this article we will introduce the application that was developed (in under a day) in order to demonstrate the various capabilities of the API and to provide an example of the API calls that it uses.

Read More

This article is published on the Triathlon Developers documentation.

With the World Triathlon Stockholm event having taken place over the weekend we decided to perform an analysis of the tweets surrounding the event to see if we could determine trends and sentiment or extract any other valuable information from the Twitter stream. Fortunately, each event in the World Triathlon Series uses a standard hashtag to convey event tweets, which in the case of Stockholm was #WTSStockholm. Naturally, there are many other Tweets that referred to the race but did not incorporate the hashtag hence these will not be included in the analysis below.

Read More

When creating an API that delivers data that is changing rapidly or where speed is very much of the essence a real-time component soon becomes a necessity. Traditional ‘request-response’ technologies where the client makes a request, hangs around for a response and then processes it adds a huge overhead both in terms of response time but also on resources spent on wasted requests polling for changes when there are none. Indeed Zapier, a service that connects together APIs, estimated that they could reduce load by 66x by implementing a real-time component and eliminating polling.

Read More