Twitter: 75% of Our Traffic is via API (3 billion calls. There were plenty of stats doled out by Twitter’s founders during Chirp Conference keynotes today.
The two that stuck with us were: 1) that its servers handle 3 billion calls every day, just to the API, and 2) that 75% of all their traffic comes from their API. If you look at the volume alone, that’s over 30,000 updates, timeline requests and searches per second. That’s a massive API. That other number, that 75% of Twitter traffic comes from third-party applications, demonstrates just how much of their growth and popularity rides on the efforts of outside developers.
Twitter’s 1 API Gave Birth to 43 New APIs. While Twitter mashups continue their tremendous growth, there’s another area we’re also noticing blossom: APIs that are based on the Twitter API.
It’s a growing trend, and we now have 43 Twitter-derived APIs in our directory. These developer-created apps and platforms process data from Twitter, adding value, and in-turn share that back out for developers via their own API. In essence, the Twitter API is the basis for a growing stack of APIs. The API Billionaires Club. We write a lot about the growth in the number of APIs on ProgrammableWeb.
Why startup needs API. There is a long list of things people will tell you that you need as a startup: You need a working product.
You need a business plan. You need a lawyer. You need a good coffee maker, a video game system, and beer on Fridays. Here's one more thing for the list: you need an API. And here are the top five reasons why: 10 Common Mistakes. Twitter was one of the first to see what happened when traffic to the site came more from the API than the Web.
Another 10 Mistakes. There was a recent post on ReadWriteCloud about 10 common mistakes made by API providers.
I think this is a very thoughtful post, but I think it's an inward look at the problem. In other words, they are looking at problems that developers face while implementing their own APIs. I think biggest mistakes are not necessarily how to implement your API, but how API consumers will perceive, implement and use the API. So I came up with my own list based on nearly a decade of implementing APIs from the receiving end. Guest author Marcelo Calbucci is the Chief Startup Officer at Conceivian, a Seattle-based Startup Lab, and the founder of Seattle 2.0, an organization providing resources for tech entrepreneurs and startups. I’m done building Facebook apps. I started building Facebook apps about three years ago, when I first started doing web development consulting full-time.
My first apps were simple affairs, but over time they grew more complex and I leveraged the platform features more and more. Marketing. Last week, Alex Williams posted a list in ReadWriteWeb's Cloud Computing channel of the "!
0 Common Mistakes Made by API Providers. " Alex's post points to some of the problems that occur in both the technical and the business realms of API development. In the case of the latter, he lists "Poor Community Management" and "Not Recognizing the API as a Core Line of Business" as common business-related errors. Weekly bugs report. We have received a great deal of feedback recently about things we should do to improve Facebook Platform.
The themes are clear: “fix the bugs,” “update the documentation,” “talk to us more,” and “make things more reliable.” We are listening, and this post outlines some of the things we are doing to address your concerns. Fixing Bugs We have set up new mechanisms to triage and track the bugs you report. Attracting Developers. This guest post comes from Alex Willen, Business Analyst at Box.net.
Alex works with the Box platform, improving its usability and evangelizing it to developers. An API can be an extremely powerful tool, allowing you to expand the functionality of your product without having to do the development yourself. APIs Enterprise Ready. Typically, when anyone talks about APIs, they talk about internal or enterprise APIs and external or open APIs. But as the cloud services become more widely adopted, we’ll see an interest in more hybrid situation, where internal IT departments use external APIs or other services as part of a broader architecture. Hackathon.
Twitter kills whitelists. Last night, Twitter made official what many members of the developer community had long suspected - there would be no more whitelisting for data-hungry apps. For some developers, this either means that they have to come up with creative work-arounds or, for others, that their projects are dead in the water. So why did Twitter kill the exception to the rule and what does it mean for the future of Twitter apps and the developers who create them? Appstore. This guest post comes from Alex Willen, Developer Advocate at Box.net. Alex works with the Box platform, improving its usability and evangelizing it to developers. So you’ve decided to put together an API, an excellent choice which I applaud. Appstores.com.
Business Models. Business models were nascent in 2005, when ProgrammableWeb listed only 105 APIs in our directory. There were only four basic models, according to John Musser’s talk this morning at Glue. Fast forward six years and those same business models exist, but there’s a lot more detail, as the now 3,000+ APIs have refined the ways an API can make money. 2005 API Business Models 2011 API Business Models (larger version) Most of the 2005 models contain at least another level of detail, with the “developer gets paid” model containing the most granularity. Limiting API Usage? As a consumer of APIs, one thing you encounter every day are API rate limits. Pricing Data in the overload age. :D Marijuana APIs. We are seeing APIs appear in just about every industry this year, from finance to green tech to health care.
One industry that clearly seen the value of APIs is the U.S. medical marijuana industry, recognizing thatAPIs can provide the seeds for entirely new strains of business models and applications to grow (pun intended). As more states are legalizing medical marijuana, there has been a subsequent wave of APIs being launched to support the industry and developers who are working to build apps for both patients and growers.