As the API economy matures, not only are more and more companies publishing their digital services through APIs; an increasing number of organizations are working together to deliver API-based products that are mutually beneficial for themselves, and valuable for their collective customers.
The web is littered with good API intentions gone wrong. Too many businesses have realized they “need APIs” and created them as a tick-the-box feature without thinking about their broader strategic value. One critical difference between the businesses that succeed and those that don’t is the underlying approach by which APIs are planned and conceived. Put simply: Is the API a project or a product?
I began my career in retail technology in 1992, a few years before Amazon began selling books online and would, as we all know, go on to forever redefine retail and consumer behavior. In all that time, data about customers, inventory, service, and marketing simmered below the surface of retail organizations — never rising to the level of prioritization that would have empowered us to leverage it to full effect.
In 1989, when Jan Carlzon, the now former CEO of Scandinavian Airlines (SAS), published his bookMoments of Truth, he posited that a customer’s journey with any organization involves an untold number of seminal moments, each of which possesses the power to make or break that company’s future with that customer. Yet, somehow, long after his book was published, if you ask anyone who regularly travels by air about their experiences,
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.