The API economy is:
All commerce generated by the business of providing, consuming, integrating, and adding value to data (and thus often to products and services) via application programming interfaces (APIs) that create economic value.
The data economy and the API economy are closely related, so much so that in a recent conversation with Forrester analyst Eve Maler, we found ourselves violently agreeing that “you shouldn’t talk about the data economy without talking about the API economy, and you shouldn’t talk about the API economy without talking about the data economy.” But although the majority of APIs are about data, APIs are also a key foundation for delivering modern applications (i.e., web and mobile), so think of the way they all fit together like this:
What this means is that:
- Many aspects of the API economy are tightly bound up with both your approach to modern applications and your participation in the data economy, but
- Some aspects of APIs are more about modern applications, and
- Some aspects of the API economy are mostly about the data economy, independent of modern applications.
So how should you approach joining the API economy? Here’s how:
- Start by understanding your business context. Many firms are driven primarily by the need to implement adaptive intelligence. CIOs (and other IT leaders) should also learn what adaptive intelligence means to them. Other firms may see open data as a bigger driver of their business context.
- Understand your firm’s role within the open Web. That’s how it all started, and this underlying trend will shape your requirements for building an API strategy.
- Factor in your objectives for delivering a digital experience. Understanding your overall digital experience strategy will add more specific requirements for your API strategy.
- Factor in your goals for delivering mobile apps. Forrester’s advice for delivering mobile apps? Don’t! Instead, you should be delivering modern applications, which are by nature omnichannel. This means your mobile application delivery strategy is really a modern application delivery strategy.
- If you will provide APIs, then develop your API design strategy. OK, now you’re really ready to get going on this API stuff - and to do that you have to first translate all that context into your design strategy for APIs, which will very much reflect the shape of your business strategy as it relates to APIs.
- Choose your API management solution. Now that you have a strategy, you know your requirements for this important part of your API technology platform for developing, delivering, and monetizing your APIs, including sustaining the communities of developers who will consume your APIs.
- Get your security pro colleagues on board. APIs and security go together like, well, love and marriage, a horse and carriage. You get the idea. But seriously, API management for security pros will be a critical element of your approach — you can’t succeed without your colleagues’ active participation.
- Design and deliver APIs consistent with your design strategy. Randy Heffner has just published an important new series of four reports on how to design your APIs. You’ll begin by choosing the technology and protocols you’ll use to deliver APIs. Then decide which messaging styles you need to support, consistent with what the developers you’re targeting will want. Next, figure out your approach to transactions and error handling, then determine how to future-proof and secure your APIs, to ensure you can sustain the APIs and the business they enable.
Whew. Yes, that’s a lot to think about. But firms that are fastest and best at navigating this path to the API economy will reap the greatest rewards.
Posted by Mike Gilpin