This is the last part of Building Effective API Programs. We’re concluding this series with a “cheat sheet” summary of the key success factors.
In the introduction, we explained that exposing assets via APIs can prove to be extremely valuable but that tackling the technical challenges of building the API is only one aspect. To reap the true benefits of your APIs, there’s a lot more that needs to be addressed.
Your API program should address all elements necessary to describe, deliver, and capitalize on the value of the API. In other words, at the core of an API program is the description of the value of the API – both the value for the organization exposing APIs and the value that API consumers get out of it. Delivery is all about how you make the API available,…
This morning Tim O’Reilly posted an inspiring slideshare presentation on measuring the economic impact of sharing [embedded below] – some of the content has been posted before but it’s a great reminder of what we see as one of the core principles behind APIs:
Create more Value than you Capture!
In other words – make the API such that there is benefit for others to use – perhaps even vastly more benefit than there is for yourself. Breaking it down, there are really two parts of the statement:
Do not attempt to capture all the value you create.
The first is obviously important. An API which does not enable its users to do anything valuable will not be used (we covered this at the beginning in our