The API Ratings agency aimed at instilling greater trust amongst businesses entering the API economy is set to be unveiled early in 2014. Co-founder Jonathan Bourguignon presented at APIdays Paris last week to discuss the need for the crowdsourced service and told ProgrammableWeb more about the roadmap to launch.
In the very early days of APIs, when John Musser founded ProgrammableWeb, the default for every new API was open–wide open. As the industry has matured, companies have become more careful to enter the open, public API waters. Though the number of APIs is still growing rapidly, most new APIs look very different from those of a few years ago. Popular services used to launch with public APIs, or perhaps have them soon after. Now the popular services are more likely to hold out for awhile, perhaps learning from those before. This wariness of openness has perhaps gone too far, ignoring the positive potential of embracing the ecosystem.
Today at The Ultimate Developer Event, Jason Lengstorf provided 4 technical keys to building better REST APIs. Jason is Founder of Copter Labs, a web design and consulting company based in Portland, Oregon. In his mind, these keys are all simple, as long as you stick to the basics.
In the final part of our series looking at the strategies businesses are using to engage with developers (B2D), we summarize three Developer Experience (DX) models from Brian Koles (ChallengePost), Pamela Fox (Khan Academy), and Ronnie Mitra (Layer 7).
Successful Twitter engagement is generally measured with the simple goal of gaining a high follower count, but true engagement doesn’t end with a follow-back—that is just the beginning. What you really need for success on Twitter is an ongoing conversation with like-minded individuals, folks who will provide informed feedback on your tweets, introduce you to their friends on Twitter who share your opinions and help spread your messages. This series of articles on engagement programming will show you how to use Twitter API 1.1 to move from simply following to truly engaging on Twitter.
Walk through any shopping mall food court and you’re bound to be offered a free sample from at least one of the restaurants. The taster is such a staple of mall marketing for one simple reason: it just plain works. This tactic has been borrowed with success by software-as-a-service (and even downloadable software) companies and as such is also common with API Products.
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.
Last week, the social posting site Buffer had both their database of access tokens and their OAuth client secrets compromised by attacks on Github and MongoDB. Buffer uses Github to store their client_secret in source code and MongoDB to store their access tokens.
In our continuing focus on Analytics APIs that help enterprises come closer to the customer by easier integration through APIs, here is an interview with José Luis Martinez of Textalytics. Textalytics is a brand by Daedalus, a Spanish SME that has been working in the field of natural language processing since 1998.