AvidMobile, mobile marketing solutions provider, gives developers two-way access to its mobile marketing platform through the AvidMobile API. The two-way approach to an API strategy allows AvidMobile users to better engage targets and track success. The API is available to build a custom app upon, or users can simply send and receive SMS messages from existing apps.
There are over 1,000 social APIs in the ProgrammableWeb directory. The big names in that list, Facebook, Google Plus, LinkedIn and Twitter, are also amongst the most popular public APIs overall. Since other API providers look to these leaders for examples in engaging with developers, I thought it would be useful to see how each uses a common communications medium. That’s right, how do the social APIs use social media themselves?
The afternoon sessions at the API Strategy and Practice conference included one focused on business models in an API centric world. The session featured talks on the Evolution of API Business Models, Market Driven API Business Models and Lessons learned from $0 to $1M API Revenue. One talk that caught my ear was by 3scale CMO Guillaume Balas discussing how to select the right business model.
A new API description language is looking to help out where many modern APIs get stuck: at the design phase. Officially announced, today, the RESTful API Modeling Langauge (aka RAML) offers a format friendly to both humans and machines. It also centers on re-use of results within responses. Like other description languages, it also offers the potential for post-design benefits such as streamlining documentation, enabling interactive consoles and generating client libraries. Though not formally announced at the time, the format was originally revealed earlier this month.
YouTube continues to grow, doubling its subscription rate year after year. Even more mind-boggling is the fact that 100 hours of video are uploaded to YouTube every minute. In other words, that is almost 2 hours of video every second! With over 6 billion hours of video being watched each month it becomes apparent that YouTube is stronger than ever. On the developer side we continue to see YouTube as a focal point. This week we will take a look at recent mashups utilizing the YouTube API.
This past week 6 new mashups were added to our mashup directory and 12 different APIs were used to build them. Some of the newer or less frequently seen APIs include BitStamp and Realtime Register. The most often used APIs this week are BTC-e, CampBX and Mt Gox. And the most commonly used types of APIs were Financial (4 APIs, 4 mashups), Mapping (3 APIs, 3 mashups) and Music (2 APIs, 2 mashups).
With developers already sourcing code snippets to cut and paste into their dev projects, Runnable has launched to provide a “YouTube of code” social network. Runnable have calculated there are over 200 million code searches each month, as developers look to stand on the shoulders of giants – or at least each other – when creating quick, workable solutions to include in their projects.
API middleware is emerging as a key new industry segment in the API economy with at least two launch announcements expected today (including one at DataWeek) from services offering middleware tools to API developers. Meanwhile, in an exclusive for ProgrammableWeb, Webshell.io founders share details of their API integration platform interface, and discuss why trust is the principal currency in the API economy.
This past week 7 new mashups were added to our mashup directory and 12 different APIs were used to build them. Some of the newer or less frequently seen APIs include Metro Transit NexTripand MotorsportReg.com. The most often used APIs this week are Facebook, Google Fusion Tables and Google Maps. And the most commonly used types of APIs were Social (3 APIs, 4 mashups), Database (2 APIs, 3 mashups) and Photos (2 APIs, 2 mashups).
Day 2 of the Twitter-trending Nordic APIs event wrapped up last week with presentations from global and regional players ranging from business use cases of APIs to technical discussions. In an unconference session in which participants set their own agenda, major themes included scaling issues and security.