A series of conferences known as the Nordic APIs have started a four-day tour of four countries in Northern Europe. The mission: Bringing API discussions to the capitals of Sweden, Denmark, Finland and Norway. Presentations by sponsors MuleSoft (parent company of ProgrammableWeb), Ping Identity, Twilio, Axway and Layer 7 are joined by local speakers in each country under the overarching theme of “Private, Partner and Public APIs.” The first event, held in Stockholm today, was fully booked, with events in Copenhagen and Helsinki also expected to reach audience capacity. ProgrammableWeb spoke with presenters and participants at the opening event.
Businesses exploring an API strategy are asking themselves: private, partner or public? Since the start of the year, there has been a lot more thinking aloud about how businesses decide whether to start with an internal (private) API; use partner APIs to manage specific business relationships; or jump straight into designing external, developer-facing open (public) APIs.
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.
You don’t have to look much further than the Consumer Electronics Show (CES) this week to see how dominant mobile computing is becoming. In fact, a recent survey of 6,698 developers conducted by Appcelerator found that 44 percent of enterprise developers will create and publish APIs that external developers will optimize for mobile computing. Another 45.3 percent said they would likely do so, creating a total of 89.3 percent. That total would suggest a mass movement is well under way.
As pharmacy retail giant Walgreens has announced a new revenue sharing program that rewards in-app developers using its QuickPrints API with a bigger slice of the customer pie, we take a closer look at the business model behind the API.
At this year’s Defrag conference, several themes emerged: identity management and security, quantified self and (of course) robotics. And, although the conference claimed to have APIs as a common theme (and it did), the APIs themselves were part of a much bigger and louder conversation about what they enable. Along with big data comes APIs’ ability to use the data to instruct the things around us. We may be enabling data transfers among machines faster than we can interpret the data and the legalities around using it.
It’s easy to forget that private APIs are the norm. Putting together the right public/private API strategy requires identifying the risks and needs of your business, and making smart moves to take things in the right direction.
MuleSoft’s Fall Summit series will be hosted across October in 5 North American cities (Denver, Toronto, Washington DC, Atlanta, San Francisco) and 3 European locations (London, Paris, Stockholm). Subtleties in the framing of the event agenda point to the ways the maturing API economy needs to position itself in a wider business environment. ProgrammableWeb spoke with Katie Doyle, Director of Marketing at MuleSoft to discuss what participants can expect.
A slideshare on the business value of APIs been gaining kudos from enterprises around the world. Created by the international business consultancy faberNovel, the slide deck has been presented to APIdays audiences earlier this year, as well as being delievered at industry events like Hewlett Packard’s Innovision meetup.
This past week 6 new mashups were added to our mashup directory and 29 different APIs were used to build them. Some of the newer or less frequently seen APIs include Assembla, Baby Names, Behance, Coderwall Profile, Dribbble, Envato, Forrst, Geeklist, Hacker News Mobile, jsFiddle, Launchpad, Ohloh, Plunker, Primal, Readability , RubyGems and ScraperWiki. The most often used APIs this week are Dribbble, Rotten Tomatoes and ScraperWiki. And the most commonly used types of APIs were Social (7 APIs, 7 mashups), Tools (4 APIs, 4 mashups) and Other (3 APIs, 3 mashups). The list below shows which APIs were used by which mashups: