Back to book

Identifying Developer API

A guide on how to identify potential uses of the Developer API behaviour.

When it comes down to it, the Developer API is one of the most simple behaviours to identify. All you need to do is simply ask yourself, "Do other applications need to be able to access the data from my application?".

The Developer API behaviour, which is included as part of every application, allows the data from your application to be accessed by third-party applications. This is not to be confused with your application needing to access things from an API. The behaviour is about enabling your application to be opened up and become available.

Examples of Developer API

Legacy Systems

When companies have old legacy systems which they are trying to modernise, they will often make use of an API to connect their new databases with their old ones. When they build their new applications, they can use the API behaviour to make the data and functionality available to the old system, to help ease the migrations process.


Let's take the example of Twitter as a use of the Developer API. They have made their main functionality and data available (with security) to be used by developers as they require. Developers can use the API to make a profile follow another one, like or retweet a tweet, along with other options. In this scenario, it is Twitter who used the behaviour, and the developers hooked into the API to achieve their goals.