For a couple of years at least, Buffer fans have been clamoring for the social media service to integrate with Google+. Why can’t we schedule posts to our Google+ Pages?, they asked. The answer was because Google had not released a Google+ write API yet.
Buffer creates scheduled posting via Google+’s new API. Facebook updates its Android SDK, catches up with its iOS SDK. Plus: SOA and API management markets may be merging, the two syllables barred from app titles on Instagram are “Insta” and “gram”, and 10 new APIs.
There is a category of vendors on the rise in the API space; Integration Platform as a Service (iPaaS). The term is fairly new and there is some debate as to the definition and features of vendors that would be classified in the iPaaS category. This post is an overview of iPaaS and features several vendors that offer iPaaS solutions.
APIs open up a lot of unique opportunities that require engineers with diverse skill sets. You can see this in both the engineering and evangelism roles below from Stormpath, Xero and Klout. Being a polyglot is as important as ever, especially when the technology you’re building by definition can work with everything else.
There are two sides to the API equation: production and consumption. This week’s API job openings are focused on the consumption side which presents a unique set of challenges as an application becomes more distributed.
Flowdock will continue as an independent service despite acquisition by Rally. Google Highlights App Engine award winners. Plus: Dropbox highlights new Chooser integrations, Twilio upgrades iOS and Android client libraries, and 12 new APIs.
This week we have three openings that all put equal weight on the developer experience side of APIs as much as the APIs themselves. Building a great developer portal is a key part of any public API strategy and these positions at State, Macys.com and Emergent One reinforce this.
While testing out a new tool I’m working on that uses a variety of OAuth2 providers and thought I’d catalog some of the quirks I came across. This is just for the authorization flow, not for actually making requests once you’ve secured a token. Now that the OAuth2 spec is solidified we should start seeing less and less of these issues.