The Latest News On The API Economy
Searching: No Search Term , No Filters
Over 57 million Americans get their health insurance through Medicare. However, one barrier to significantly improved care has been the free flow of Medicare claims data between dissimilar systems. According to the US Digital Service however, version 2.0 of the Blue Button API should fix that.
To all of you — including the US Congress — that want Mark Zuckerberg's head over the personal data that was gleaned from Facebook and used for profit by Cambridge Analytica, you have got the wrong guy. If you’re quitting Facebook, you might be doing it for the wrong reasons.
Facing significant blowback from horrified organizations and users worldwide with respect to the Cambridge Analytica debacle, Facebook appears to be responding with swift action that will undoubtedly result in disgruntled developers and users.
When it comes to Oracle v. Google on the subject of the latter’s alleged misappropriation of Java’s APIs in the Android operating system, a federal appeals court has hammered what appears to be all but the last remaining nail into the coffin that could seal Google’s fate.
Over the last few years, one of the more painful things to watch (from a business perspective) is how Twitter hasn’t been able to seriously capitalize on its insane popularity. The stock currently trades at roughly the same level it did one year before the 2016 presidential election.
Back in 2005, when I bore witness to the debut of the first two Web APIs (Google Maps and Flickr) while working as a journalist for CNET, I knew something big was about to happen. To this day, it is still one of the most dramatic tipping points our industry has ever seen.
In a post market-closing announcement yesterday March 20, 2018, MuleSoft and Salesforce jointly announced Salesforce’s intent to acquire MuleSoft in a deal worth approximately $6.5 billion. The announcement comes almost exactly one year after MuleSoft went public on the New York Stock Exchange.
Despite the infinite compute power of the cloud and all the machine learning and artificial intelligence that thrives on that compute power, technology just falls short of our expectations. Which is exactly what happened when one developer gave Microsoft's Bing Speech Recognition API a whirl.
Software developed by the US government is technically in the public domain. But without clear direction on how to handle the public domain issue or what that means for using an open source license, agencies are often unclear on how to open source software and reap the benefits of re-using code.
Today, on the heels of news about concerns regarding the use of certain fitness technologies that could reveal confidential military troop and base locations, comes an entirely different spectrum of issues to consider before allowing for public or partner consumption of your APIs.
SmartBear has released a tool that it says is helpful for the testing that API providers might do during the API lifecycle. For example, it can reverse engineer an API definition by inspecting existing API calls. However, the experience is marred by several references to the Swagger specification.
We recently wrote about a post from CodePen.io that suggested a way of keeping API keys private when publicly sharing code samples. This time, we've gone back to that idea, given a try, and dogfooded it. We used JSBin to not only show how it works, we've embedded the "bin" in our tutorial.
In this, developer-blogger Alex Kras shows us how to overcome the 60 second audio file limitation of the free tier of Google's Cloud Speech API by taking a longer audio file, breaking it up into short chunks, and then cycling through those chunks to make a complete transcription.
Today the conditions are more favorable than ever for organizations to consider implementing event-driven non-polling based data retrieval patterns in their APIs. This series aims to help you to better understand your options when it comes to push/streaming API architectural styles.
How to Create a Quick and Dirty Example of The Proposed Standard for In-Band API Service Warnings API University
As a best practice, API providers often go to a lot of trouble to notify developers of upcoming disruptions or changes to their APIs. All of this happens out-of-band like in a ChangeLog or an email. But how about the idea of in-band notifications, especially when developers are impossible to reach?
To laypeople, the high potential disciplines of artificial intelligence (AI), machine learning (ML), and data science are enigmas. Most people don't even know what these terms mean, let alone what to do about them. But, in its Einstein portfolio of AI offerings, Salesforce has cracked the code.
It's the end of November, temps are dropping, holiday music is already filling the airwaves, many of us are still experiencing the consequences of over-eating during the Thanksgiving weekend, and next week is the first week of the month. And you know what that means! Time for another DC API Meetup!
When Yahoo! shut off a stock quote service that developers were relying on -- albeit anonymously -- developers erupted with disappointment and anger. But those developers were probably trespassing on the service and Yahoo! had no way to notify them of the shutdown. Maybe a standard can fix that.
Everywhere you look, you'll find old business processes that have been in place for decades. When many of these processes went online, chances are they were reproduced, step-for-step, electronically. No one bothered to think differently about those steps. Jetty is example of one company that did.
In partnership with Intuit, the provider of the very popular QuickBooks Online SaaS app, Lighter Capital has established a $15M investment fund in order to make additional financial resources available to 3rd party developers who are part of Intuit's growing developer network.