The Latest News On The API Economy
Searching: No Search Term , No Filters
For over a decade, ProgrammableWeb has been unable to track multiple versions of an API. In the coming weeks, ProgrammableWeb will migrate to a new data model that addresses that shortcoming while also serving as the foundation for a powerful faceted API search feature as well as its own API.
The demand for skilled Web developers is showing no signs of abating. Organizations operating under the assumption that such developers are all it takes to modernize their monoliths into API-led, agile, shape-shifting high fliers that can survive today’s technical Darwinism are in for an awakening.
GraphQL APIs are most definitely not RESTful APIs. They bear some resemblances to RESTful APIs in that they rely on HTTP for making API calls. Like many RESTful APIs, they even use JSON for payload formatting. But, their architectural style is most definitely not RESTful.
One of the most complex topics, especially for organizations that are new to the API economy, is the concept of an API ecosystem. This whitepaper was written to help you demystify what an ecosystem is and its role in your overall API strategy. This is the second of our ongoing series of whitepapers.
Despite a barrage of headlines that could kill most companies, Facebook operates with near absolute impunity. To dissatisfied users who want out, it brazenly dangles an offer to take all their data before quitting so it can be uploaded to another service. We tested the veracity of that offer.
In this follow up to a previous case study examining Intuit's Quickbooks ecosystem, we're improving on an existing diagram of the Quickbooks ecosystem; this time we get into the details of what a successful API ecosystem looks like and how you should go about building yours.
Recent research indicates that, across organizations surveyed, old point-to-point integration habits are dying hard. In fact, they could be getting worse, resulting in an increasingly intractable situation as enterprises struggle to digitally transform themselves and avoid fatal disruption.
The decision “to API or not to API?” should not be a technology conversation. Many companies fail after attempting to monetize APIs without specific business outcomes in mind. That journey, marked by a four pillar API strategy blueprint, starts with a business conversation and "outside-in" thinking.
Roughly a year after Elastic Beam launched a machine-learning driven API security solution, Ping Identity stepped-in, acquired the startup, and folded it into its portfolio as the Ping Intelligence Business Unit. With dust from that marriage having settled, Ping's Jason Bonds gives us an update.
In Intuit’s case, the business strategy started with the right customer experience. Once they had an idea of the end-to-end customer experience it needed to enable, next came some strategic platform and ecosystem decisions.
Kong, the API platform formerly known as Mashape, recently announced the launch of Kong Cloud. This new service targets organizations that want the API Management capabilities of Kong Enterprise, but don't want the burden of managing the software itself.
In aggregate, the organizations around the world that directly or indirectly monetize their APIs form the basis of what the media often calls the “API Economy.” As a subset of the total global economy, the API economy is responsible for the exchange of trillions of dollars of value annually.
MuleSoft has announced the Winter 2018 release of its Anypoint Platform for managing APIs and enterprise integrations. Similar to a social graph, the release offers a bird's-eye view of an organization's application network graph. The release also uses machine learning to ease data mapping tasks.
More than a decade ago, a handful of companies looked to capitalize on the open source movement while at the same time perverting the licensing fundamentals behind it. The threat to open source culture was palpable. But disaster was averted. Today, history is repeating itself and it's time to act.
Earlier this week, Salesforce.com disclosed that a potential security issue with one of its APIs has been corrected. The issue impacted a subset of Salesforce.com Marketing Cloud customers that used Email Studio and Predictive Intelligence and no malicious activity related to the issue was detected.
Upon seeing the headline to this article, API experts will likely scratch their heads wondering why the journal of the API economy (ProgrammableWeb) would indirectly suggest that REST and Swagger are comparable to the point that an article about their differences is warranted.
As various services like Facebook deal with competitors by packing more functionality into their apps, those apps are increasingly experiencing usability issues. In the old days of the API economy, outside developers could leverage a service's APIs to build something better. But those days are gone.
MuleSoft founder Ross Mason has a bit of a reality check for anyone willing to listen. It has to do with how the majority of today's artificial intelligence can only do about half of what it should be doing. According to Mason, it needs to be more of a two-way street and for that, you need APIs.