As a consequence of the recent FTC investigation, Facebook cut off friend data access for Microsoft and Sony and announced an overhaul of its API. Facebook’s privacy changes will impact dozens of partners that have been using the Facebook API to build experiences on third-party apps and devices. Here are three essential considerations for API providers, consumers, and end-users to avoid a scandal like Facebook’s and protect the privacy of user data.
Many businesses today are trying to augment and improve their customer, partner, and employee experiences by leveraging artificial intelligence and bots, yet grapple with the issue of cybersecurity. We’ve all heard of the numerous accounts of cybercriminals taking advantage of chat APIs, social network application vulnerabilities, and increasingly sophisticated phishing campaigns. However, the majority of cybersecurity hacks are still accomplished in a rather old-fashioned manner — through the use of stolen credentials.
One of the most important parts of an organization’s API ecosystem is the community of developers who build applications that consume its APIs. The success of an API strategy often depends on understanding the target audience of developers for your APIs, identifying their different sub-groups, and then consciously growing the community.
Mike Amundsen recently joined MuleSoft as API Strategy Advisor. Mike is a well-known API expert in the global software engineering community and has authored and co-authored numerous books including “RESTful Web APIs,” “Microservice Architecture,” and “Continuous API Management,” all from O’Reilly. His latest book, “Design and Build Great APIs,” will be available through Pragmatic Bookshelf later this year.
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.
Meet Matt McLarty, who recently joined us as Global Leader for API Strategy. In this role, Matt helps MuleSoft’s customers take maximum advantage of their API opportunities through strategic guidance, sharing organizational practices, and the development of API ecosystems. He’s based in Vancouver, BC, Canada.
One month into 2019 and we’ve already covered a wide range of content – from JSON logging in Mule 4 to work automation and API strategies. To provide you with the best posts to read if you’ve missed, here are the five most popular blog posts in January 2019.
As more business people become exposed to the API economy – the idea of turning business capabilities into APIs that are subsequently monetized in some way – they often race to the most obvious question: What should my strategy for the API economy be?
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?
