API management came about to help companies create and manage developer ecosystems by following in the footsteps of the successful API programs of Twitter and Facebook. Today, APIs have become the connective tissue that powers all interactions with customers and partners across an extended value chain.
In this webcast, Apigee's Ed Anuff and Dilshad Simons discuss the technical and business implications of this shifted landscape.
We’ve looked at internal, partner, and customer API initiatives. This time we’ll look at the Open API initiative, probably the most familiar of strategies given the success of companies like Twitter, Foursquare, Facebook . . . A lot of companies are inclined to start with an Open API using Twitter, Foursquare, or Facebook as the archetype. We generally recommend against this approach.
In this short series to explore different API strategies, we've looked at the characteristics and examples of Internal and Partner API Initiatives, which are often the first and second stages of a company's API strategy.
The Customer API initiative is mostly used in one of two scenarios. The first is when offering software as a service (SaaS). (Look at Salesforce as an example where customers demand an API.) The second is when the customer of your business is another business (a B2B scenario).
Here we look at...
Last time we looked at the archetype of an Internal API initiative, which is often the first stage in a company’s API strategy.
The second stage is often to collaborate with partners. A partner API initiative is one that focuses first on collaboration with strategic partners. Those partners create applications, add-ons, or integrations with the API. At this stage the API gets hardened and because the API is used across organizational boundaries, the API team will learn a new set of lessons including support, documentation, authentication schemes and so on.
Anatomy of a...
In a recent post, I made the argument that the key to bridging the gulf between IT requirements and those of the new app economy is an API.
We categorize the API initiatives that support the app economy in four flavors - Internal, Partner, Customer, or Open - according to the different roles that app developers can play.
So what does each of these API initiatives look like? What are common scenarios in which you see them employed and how do you align your business goals with a particular strategy? Let’s start from...
In my previous post, I talked about the challenges of ubiquity and an explosion in consumption driven by the threesome of cloud, social, and mobile apps. Businesses need to effectively target and support their customers and partners in these new contexts.
We received some strong interest in our recent webcast Why APIs in which we explored why APIs are important to successful businesses and the different API strategies (Internal, Partners, Customers or Open) we see employed. So we thought we'd drill down into the core ideas in a few blog posts.
What challenges are businesses facing in 2012?
The three major trends of social, mobile, and cloud in the market today are driving huge changes in how individuals connect, how businesses connect, how businesses engage with their customers and employees, and therefore how Information Technology (IT) works.