The Latest News On The API Economy
Security researcher Avicoder reported that he uncovered a vulnerability in Twitter's Docker installation housing its Vine source code. The researcher downloaded the entire Vine source code in one of the 80+ server images pulled. Twitter secured the install within 5 minutes, and paid compensation.
Microsoft, tech giant and one of the world's largest API producers, has published version 2.3 of its REST API Guidelines. While the guidelines are focused on simplifying API development and consumption through a REST/HTTP architecture, Microsoft touts the ever-increasing need for consistency.
As the use of APIs in business continues to grow, MuleSoft founder Ross Mason encourages organisations to shift away from traditional thinking on IT. He encourages a new, two-speed operational model, as used by GE, to deliver flexible digital services while maintaining traditional business units.
IBM transitioned its Bluemix natural language interface (Watson Conversation) from Experimental to GA. The move suggests that IBM has tweaked the cutting edge technology to a level of service that supports real-time, production environments. The service enables automated interaction with users.
The microservices architecture continues to grow in popularity as it enables the scalability and flexibility necessary to serve the modern marketplace. Saba Anees discusses some key considerations for migrating your existing monolithic architecture to a more streamlined microservices one.
IBM announced v2 of its Watson IoT APIs last August. The company has now announced the pending removal of v1. IBM has yet to set an exact date, but plans to announce such information soon. v2 includes all v1 features plus new additions and enhanced ability to integrate with third party apps.
ProgrammableWeb is constantly looking to evolve the data model behind its API directory to keep pace with changes in the API economy. We also want it to be forward looking in anticipation of developers' and API providers' future needs. This primer explains our new data model and how to work with it.
Google has released an updated Gmail API that functionally replaces the Email Settings API. The Gmail API includes a number of new endpoints that enable features previously unavailable through any Google API. Developers have access to filters, auto-replies, send-as aliases, and more.
Can your application programming interfaces truly be “public” if your terms and conditions disallow application contexts deemed to be competitive to your business interests? This article looks at a recent ruling and how it may or may not help secure Uber’s ability to have a selectively public API.
Scale has released an API that connects apps and workflows to a human workforce. After a single line of code calls the Scale API, Scale assigns a human member to complete the requested task. To start, the Scale workforce supports phone calls, transcription, and categorization services.
Google implemented a number of changes to its Maps API Standard Plan. Apps created on or after June 22nd will be subject to a host of new rules surrounding access and limits. Active domains utilizing the APIs prior to June 22nd are grandfathered in to differing degrees depending on implementation.
Red Hat announced that it signed an agreement to acquire 3scale. By adding 3scale to its existing portfolio, including Red Hat JBoss Middleware, Red Hat OpenShift and Red Hat Mobile Application Platform, Red Hat hopes to strengthen its enablement of the API economy with simplified cloud integration.
BetterWorks announced an API that connects data points from across an enterprise into a single report, dashboard, or method. The API enables companies to gather the data necessary to create and measure company goals. BetterWorks aims to "combine the power of goals and the value of people".
As the focus on APIs grows, we spend a lot of time optimizing the DX by focusing on delivering robust documentation, easy accessible and un-throttled sandboxes, various support channels, and community events. To maximize the DX it's important to understand the larger context in which your API fits.
One of the challenges with API design is focusing on the complexities of designing a UX for your API. In most product development roadmaps, the focus is on B2C or B2B and the ideas behind those delivery models are well understood, but keeping in mind the end user experience can make a difference.
When RESTful APIs first hit the radar, one of the benefits often cited was that the APIs could be easily understood from the WADL alone. As the API industry evolves , both providers and consumers have started to recognize the need for better, more easily consumed documentation.
The idea of design first is extremely simple, and highly cost-effective. Many companies seem to be unaware, or simply choose to take a short-cut to save on the development cycle, exchanging months of refactoring and struggles for a couple of weeks to make sure it was done right.
By Jan 13th 2018, EU banks will be required to open payment and account services to third-party providers. The disruption this may cause in the banking industry is reminiscent of the shipping industry and the changes brought about by the standardization of containers 50 years ago.
Microsoft just announced one of the more groundbreaking enhancements to its app maker, Windows App Studio. The REST AI Data Source allows users to retrieve data from third party API providers. The move greatly expands the potential for app development within the Windows App Studio environment.
Last week, UrbanHail, a Boston startup which developed an app to provide real-time price comparisons for Uber, Lyft and taxi services, found its access to the Uber API revoked for violating Uber's terms of service. The startup claims that Uber's actions are "anti-competitive."