January 5, 2016
View all Followers
View all Related Articles
The week is in full gear and we bring you a review of the stories we couldn’t cover with a look at what what going on in the world of APIs. We look at a customized speech recognition API from AssemblyAI, a new banking payments API from Oracle and some confusion over just how secure the Uber app is.
For a few days, Facebook was providing a user's phone number and address available, with the user's permission, via its Facebook Graph API. Likely fueled by distrust of Facebook's previous approaches to privacy, users and press reacted negatively to the concept. Based on this feedback, Facebook reversed its decision and neither phone or address is returned to applications at this time. Privacy is a big concern, especially for APIs, but Facebook took appropriate steps for gaining user permission. The reaction to Facebook's platform change was an overreaction, which points to a need for more granular privacy controls and a better method of granting access.
It seems at every API conference, there is a new feature being released by the team at OAuth.io. In October, at API Strategy and Practice in San Francisco, OAuth.io released a mobile SDK. Now after APIDays in Paris, OAuth.io has released a 'code request' feature to abstract usage tokens in the authentication process. Co-Founder Mehdi Medjaoui spoke with ProgrammableWeb about the service that provides a unified API for any OAuth implementation.