Given the rabid nature of most of their fan base, professional football teams were among the first organizations to see the value of developing mobile applications to get closer to those fans. The problem for most teams now is the stadium WiFi experience they provide to their most loyal fans leaves much to be desired.
For many APIs, a developer portal is the first interaction a developer will have with the API. Typically, this is where a developer finds documentation, code examples, an app gallery and other details that connect them with the API provider. If you want developers to use your service, you’ll aim to make everything within the developer portal as clear as possible. Consider these six steps to bring clarity to your current and future developers.
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.
We have covered Algorithms.io before on ProgrammableWeb and it is an exciting API using machine learning algorithms to deliver predictive analytics. It has specialized in classifying streaming data using machine learning. Algorithms.io was acquired in December 2013 by LumenData, and we have an exclusive interview with Algorithms.io co-founder Andy Bartley post the acquisition.
The benefits of a well-designed, well-implemented, easily integated API are well known: happier developers, higher usage and, hopefully, greater profit as a result. While many high-level best practices for developing a great API have been established, a failure to pay close attention to small details, such as parameter defaults, can create big headaches.
This year has seen an increasing number of creative agencies incorporating APIs into the way they work. Sure, PR and digital creatives are using APIs in their monitoring and analytics to measure reach and impact of their efforts, but increasingly, they are using APIs to funnel realtime data into the very fabric of their campaigns and to ramp up audience engagement around a brand’s story. ProgrammableWeb spoke with Arvid Dyfverman from the award-winning Swedish PR agency, Deportivo, about how APIs are at the very center of their creative campaigns.
We have covered Web scraping before. As the amount of data that can be captured from the web increases, developers increasingly need a way to handle huge quantities of data downloads from the internet, both structured as well as unstructured. The basic underlying problem in creating custom scrapers is that websites often differ in the basic variety of formats, so a scraper that runs smoothly on some websites may return junk results on other websites.
Following up on an earlier post outlining the top ten mistakes commonly made at hackathons, Brandon Wirtz now offers his take on ten things every organizer should do when running a hackathon.
The team at Intel Mashery has helped launch more than 200 customer API programs, and has identified a few key steps that can encourage an overall API launch with the potential to generate new revenue streams, increase innovation and drive business development.
The adoption of REST as the predominant method to build public APIs has over-shadowed any other API technology or approach in recent years. Although several alternatives (mainly SOAP) are still (very) prevalent in the enterprise, the early adopters of the API movement have taken a definitive stance against them and opted for REST as their approach and JSON as their preferred message format.