API illustration



Almost overnight, it seems, our lives came to revolve around social networks: We scan our Facebook feeds for updates from our families and relevant news, use Twitter to follow friends and celebrities, and pin the latest fashions or home-improvement ideas via Pinterest. Behind it all is the desire to drive engagement, to stay connected with people, brands and trends.

If engagement is fueled by people, then the fossil fuel of the next generation is the API — Application Programming Interface. Without APIs, none of these new engagement models would have become the most critical new business growth tool we have seen since the television revolutionized the living room and advertising.

So, what are APIs? For many of us, the first exposure to the influence of APIs has been via mobile phones and the explosion of apps. The majority of mobile apps today are a combination of user interface, tactile interaction, integration with device features, and data delivered and consumed via APIs. By the very nature of mobility afforded to such devices and the ability to connect geolocation to marketing opportunities, APIs have created a bridge to customer habits, and have become part of their daily conversations.

Mobile is simply the beginning of an entire new generation of businesses built around the customer. A recent report from Cisco stated that by the end of 2014 there will more mobile-connected devices than there are people on earth. Not all of these devices will be mobile phones, however many will be wearable devices like Fitbit band, connected cars like Tesla, and connected homes, as we see through products such as Nest.

Each of these devices, powered by APIs, are giving organizations greater visibility into their customers, which is allowing them to connect in whole new ways. Before long, a typical visit to the doctor will begin by downloading your activity monitor at home, rather than completing paperwork while sitting in cramped waiting rooms struggling to remember your exercise and dietary habits.

We could discuss the importance of RESTful for mobile services, streaming and bulk APIs for efficient data access and OAuth for authentication, but the true API imperative for businesses is how to become a high-growth company in this emerging API economy. The simple answer is Platform as a Service (PaaS).

Consider Apple, Facebook and Salesforce.com, just to begin with. Each one of these companies is a PaaS provider — they offer everything organizations need to build their business based on services provided: Apple offers an easy way to instantly buy music and apps; Facebook has the social graph; and Salesforce.com provides the tools for any user to build social, mobile and next-generation enterprise apps. However, each of these companies also provides access to the data and insights created through these transactions via APIs.

Geoffrey Moore, in his book, “Crossing the Chasm,” coined the phase “core vs. context.” APIs are platform companies’ core business, but for the majority of businesses it is contextual; they are not in the business of building APIs. Successful businesses of tomorrow need to focus on business growth and customer engagement and utilize platform companies to provide APIs in order to fuel this growth and deeper relationships with customers.

Platforms must also make API consumption — and the data collected through APIs — easy. Often this ease of use translates to organizations building mobile apps for employees and customers quickly and without the need for specialized resources, or integrating with existing systems. Where developers are tasked with building custom apps, APIs must be accessible using the latest languages and technologies. Developer productivity is a fundamental goal of organizations. Without it, apps, the conduit of APIs, and the collection of critical customer and business data may fail due to poor user adoption, bad customer experience, or costly and delayed development cycles. Regardless of the cause, the symptom is the same — lack of visibility and customer engagement.

Business users consume APIs differently. APIs can enable businesses to improve organic sales growth and reach new audiences. Businesses need powerful data analysis tools such as dashboards, reports and insights to improve engagement. Twitter, for example, provides Twitter cards to help provide insights on how a company’s products are being shared. Leading platforms support business growth by eliminating ad-hoc tools like spreadsheets and local databases.

At Salesforce.com, APIs have been a core aspect of our platform for more than 10 years. Our customers perform more than a billion transactions a day via our platform, with more than 50 percent of these coming via the API. Yet the majority of them never consider that they are growing their business because of these APIs. And that’s the true test of any platform provider. We are not here to power data. We are here to power our customers and their customers’ success.

The true business imperative of APIs is how an Internet of Customers will drive the business models of tomorrow’s global brands. Without APIs to create this customer connection as that fundamental fossil fuel of business growth, organizations will fundamentally fail to adapt to the world of tomorrow.

Quinton Wall is director of technical platform marketing for Salesforce.com. Reach him @quintonwall.

Peter Vazquez
Peter Vazquez

Funny thing happened to me very recently on this topic. Currently working with a company that provides an api for an online directory service they offer and along with it comes an android and iOS app. Obviously the .apk and .ipa files are encrypted so I asked if they could quote me on simply adding the necessary code in order to use a service like parse.com that would allow us to send segmented push notifications; a feature their solution currently does not offer. Their current push notification features sends a message to all who download the app, meanwhile their directory website service provides the ability to add events in any location. It does not make sense that their push notification feature does not originally provide this feature. In the end, they came back with some ridiculous price to add about 15 lines of code in the android manifest.xml file. So we figured for that amount of money it would be best to simply recreate the entire app for that amount and populate the app using the api code they already offer. 

My point is this... API's are very common today. Using services like parse.com for notifications is also very common now a days. I will admit I am not a mobile developer, but I am website developer and do a lot of research. I can not wait to learn how to use an api with their key and rebuild the app they currently offer. 

Thank you for the motivation..


hmm.. this article has taken on a couple tones. The portion on evaluating the benefits of implementing APIs is a dated topic, and I think it only retracts from what I presume is your overall point in this article. I agree that businesses, both big and small, should provide an API into their services. They should commit to that investment. Even if that API simply leverages larger platform APIs, and adds the necessary contextual data for that exchange. 

I haven't read 'Crossing the Chasm', but in my experience developing core libraries and implementing them.. every exchange (request/response;I/O) is contextual. It is really the scopes of that context that developers, and the systems they develop, deem relevant. However, I suspect he means circumstantial instances in business services, where there is an element of flexibility in the handling of that service that makes the typical constraints and handling irrelevant.

I think before we provide articles and suggestions on businesses to provide APIs, it should be recommended that they commit to making workflow diagrams of their services and product purchasing process.  You get them to commit to doing that, and it won't be too long before they look at automation and better reporting.


 We build custom apps, API's are a fundamental part of that process. They give the data and specifications to make that data useful. Look at one of our new apps Buy Local, it is the first app we have built that allows for business to pick what data they want to display to get the data they want.



A.J. Weinzettel
A.J. Weinzettel

Of course APIs are bridging gaps for mobile.  This is really nothing new. APIs have been bridging gaps way before the thought of a mobile device could consume a YouTube API for streaming video. What about the days when XML was the craze for exchanging data back for forth for B2B payments? Instead of talking about data centric APIs between servers the next bridge to build are the device to device APIs.  I am talking about LE Bluetooth APIs as an example. This is the next big thing for mobile.  It is going to provide the custom experience for what is happening to a person In Real Life (IRL). Bringing a mobile experience to IRL experiences is really the bridge we need to focus on.


Get every new post delivered to your Inbox.

Join 309,268 other followers