In earlier pieces about APIs where developers pay for access, I’ve covered methods of pricing APIs and even shared the top three API trial methods. However, some of you are probably not that far along in that process. You may have a good idea for a developer-focused company. Or perhaps your company solved a big issue internally and you want to expose your solution as a new revenue stream. In any case, before you dive into your pricing page and start selling your API, you’ll want to consider some basic questions about the problem, your solution and whether you’re able to support your potential customers. These are the three questions to ask yourself if you sell an API.
According to the employment Web site Simply Hired, job advertisements for “developer evangelists” grew by 38% in 2013. The average salary for these new jobs was between $80K and $120K per year. With new vacancies from Twilio, Pebble, and HelloSign all being advertised this month, there is no end in sight for developers who want to combine marketing and business development skills with their programming expertise. ProgrammableWeb surveyed the career field and spoke with Context.io Developer Evangelist Tony Blank about what the job involves.
Some APIs provide data. Others offer functionality. Many of the APIs developers pay for solve a big developer problem, often with infrastructure. A company’s own intelligent calculations are a great opportunity for consumers and providers alike that may not be an obvious avenue at first. Below are a few of many examples of these types of APIs to inspire your next project or maybe your company’s next product.
Photo APIs have long been a staple of developer applications. There are more than 350 photo APIs in the ProgrammableWeb directory and almost 800 photo mashups. However, most applications integrate with photo sharing services, like the Flickr API and Instagram API, missing the real power of photo APIs. This post identifies four ways that APIs are getting smart by using image recognition technology to find faces, words and more.
Along with the growth of APIs in general has come the emergence of the API as a product. Many times a new startup is entirely an API. When the entire company is an API, you’d better choose the right API business model. When the API is the product, or the whole business, many times this means charging developers to use your API. It turns out, it’s not just about how much you charge them, but how. This post will look at the many different ways that API-as-product companies are getting developers to pay for access.
This week we had 40 new APIs added to our API directory including an application to help users learn and analyze the art market, a platform that brings together thousands of data sources, a completely automated trading environment giving access to liquidity streams and pricing, and an adaptive search engine provider. In addition, we profiled an API that allows suers to virtually fit their clothing before buying it online.
Google’s shopping API is being shuttered, what are the alternatives? Qubit’s API makes integration of ecommerce business intelligence easier. Plus: API best practices and advice, why analytics are important, and 18 new APIs.
KidoZen, leading provider of mobile platform as a service, announced that Salesforce.com’s mobile APIs are now part of KidoZen’s backend as a service platform. Vivante has launched its new Vega IP product line that includes new API support, and 7 new APIs.
Our API directory now includes 82 address APIs. The newest is the 1Map API. The most popular, in terms of mashups, is the geocoder API. We list 41 geocoder mashups. Below you’ll find some more stats from the directory, including the entire list of address APIs.