APIs are largely hailed as the driving force behind digital innovation, and it is difficult to argue with this concept. Yet despite many high-profile API evangelists preaching the good word about APIs in general, there is a need for more localised evangelism, according to a post by Sam Macklin.
Taking inspiration from enterprises that adopt an API-first culture, the new IT leadership team for the state of Arizona defined their strategy, changed the culture and built a cloud-based digital platform that leverages APIs to drive digital transformation of a decentralized enterprise.
A truly effective developer marketer knows who the decision makers are and how (and why) they make their decisions. This article provides a step-by-step guide to determining who the development decision makers are and how to match your messaging with their current and future needs.
This is the first part of ProgrammableWeb’s series on Understanding the Realities of API Security based on testimony by ProgrammableWeb’s editor-in-chief David Berlind to the ONC’s API Security and Privacy Task Force. This part looks at the actual security concerns surrounding APIs.
The growing use of APIs increases the potential security vulnerabilities that expose businesses and users to malicious intent. A recent study undertaken by Ovum and Distil Networks shows that a lack of clarity in who is responsible for API security means not enough is being done manage the risks.
Proving that it's the personal touches that matter, Planet OS goes the extra mile of dynamically populating its API documentation with details that relate to the identity of the developer (so long as they are logged in while viewing that documentation). Wouldn't it be great if more API docs it too?
Any company that makes an API knows that just having the API is not enough. A bare endpoint is probably worse than not having an API at all. To make your API and platform useful you need documentation, tools, examples and forums. If you are a successful API company you start developing a community of people that work with your service. The community shares ideas and helps each other out.
It's easy to forget that private APIs are the norm. Putting together the right public/private API strategy requires identifying the risks and needs of your business, and making smart moves to take things in the right direction.