
API - Marketing
Get flash to fully experience Pearltrees
At Arcturo , we’ve been working with a lot of remote API’s and big data lately. The more API’s from all over the web I work with, the more I realize how much some companies really get how to build an API that developers love and use all the time, but at the same time, I’m beginning to realize how little thought some teams really put into their API and how it will be used. I rant about this often to Ryan , so I thought I’d go ahead write up a little list of things that API consumers would really appreciate if you’re providing an API. Keep it consistent.
Attention API Provider: How to make people using your API love you
Neil Mansilla is Director of Developer Products and API Evangelist for Mashery . Mashery is a ProgrammableWeb sponsor. Developers are game changers.
Developer Painkiller: Interactive API Docs
Adam Kleinberg is co-founder and CEO at Traction , an interactive agency that aligns psychology with technology to create ideas that work. Catch him tweeting at @adamkleinberg and blogging at tractionco.com/blog . The most effective ads today are experiences that provide value to customers. The biggest challenge is providing that value at scale in a world where people are empowered to consume media on their own terms through a dizzying array of gadgets, devices and doodads.
Why Every Brand Needs an Open API for Developers
HOW TO: Get Devs to Use Your Company’s API
API - Marketing - Examples
A Marketer's Guide to APIs
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. The API has long been seen as a cornerstone of BizDev 2.0 , a term coined by Hunch co-founder Caterina Fake. But parallel perhaps to the misconception that "if you build (a product), they will come," is the notion that simply because you've developed an API for your business that you have, in fact, upgraded your business development to that 2.0 level.
Developing Your Business By Marketing Your API (Build 20100722155716)
We have seen an explosion in the number of APIs that are now available to developers. It seems like almost everyone has one and those that don’t are scrambling to get one. The focus now is clearly not on just having an API, but having a “great API.” Two excellent presentations from Cloudstock , held earlier this month, give you an overview on the current state of the API market and tips on what makes a great API. Programmable Web Founder John Musser gave a presentation titled Open APIs : State of the Market , which we also referenced in Open APIs: Why Bother? The presentation draws heavily on data from the ProgrammableWeb directory, including the numbers behind the rise of JSON over XML and REST over SOAP.
Two Must-View API Presentations from Cloudstock
Startup, avez-vous créé votre Status Page ?
Depuis plusieurs mois déjà, les services web qui « décollent » sont rapidement confrontés à des problématiques de tenu de charges. Rançon du succès, coup médiatique ou simple pic de charge, il n’est pas toujours évident de maintenir une plate-forme Up & Running tout en assurant des développements en parallèle et une communication agressive sur un service web. De plus en plus de services web choisissent également de diffuser leur contenu ou services via des API ouvertes en incitant les développeurs à les utiliser. Dès lors, les problèmatiques de tenue charge deviennent doubles : ne pas dégrader sa propre plate-forme tout en assurant une qualité de service minimum pour l’ensemble des utilisateurs des autres services construit sur ces API. Faire preuve de transparenceAre APIs the New Black?: Tech News and Analysis «
Many companies have launched API programs, and many more will in 2011 . Some have used their API to become unstoppable market forces by empowering a new indirect channel. Others have seen minimal API adoption, and are unclear on why they haven’t succeeded. Even more are in the “mushy middle” between success and failure. At Apigee, we observe common patterns in API programs that succeed – in planning, management, and organization. Those that fail hit common pitfalls in these categories as well.
The Building Blocks for a Successful API Strategy: Tech News and Analysis «
There’s a difference, however, between responding to inquiries versus begging for the first 1, 2 … 10 sites to use your web service. Twitter, Facebook, Google and Yelp need an API because they can’t respond to the market fast enough for people seeking access … here self-serve makes a whole lot of sense because the value of these services are well understood and it cuts out expensive teams of sales, business development, account/client management, professional services, etc. However, what happens if you believe you have an amazing service, data, content or technology but nobody really knows about it? Or nobody knows the benefits of building on top of your API?

