
Much of our inspiration for starting Newspaper Club is down to Aaron Straup-Cope, and his Papernet projects. Aaron’s thoughts on how paper and printed media can be a natural part of the web and the “network” encouraged us to play around, led to experiments with newspapers, and lo: Newspaper Club was born.
A lot of what we do at Newspaper Club is about making it easy as possible to access newsprint: to lower the barrier of entry and let people make whatever they want. We’ve built ARTHR, our layout tool, we’ve written lots of help pages, and we try and be helpful on email and the phone, all to try and make it as easy as possible.
But we want to make it easier for machines too. Because why should humans have all the fun? Machines should be able to make good looking newspapers too.
So, today we’re launching the alpha release of the Newspaper Club API. The API provides programatic access to ARTHR, letting you write tools and apps that generate newspapers from any content you have.
We’ve written some API documentation which should help you along the way. We know it needs fleshing out in places, but if you’ve got any suggestions for what we’re not explaining very well, please let us know.
As a demonstration, we’ve built a tool nicknamed The Telepaper, that turns a Readability Reading List into a newspaper with just a couple of clicks.

As luck and timing would have it, The Engineering Dept. entered this in Readability’s API contest and are very pleased that it won third place! Hurrah! (Thank you Readability folks.)
The Telepaper is a very simple Ruby Sinatra application that glues the Newspaper Club and Readability APIs together. All the source code is available on the Newspaper Club Github account, and you can try the application for yourself if you’ve got a Readability account.
If you’d like to have a go with the API yourself, you’ll need an API key from us. First take a look at the documentation, then drop us an email containing your Newspaper Club account’s email address, an OAuth callback URL, and a brief description of whatever you’re playing around with, if you know. We’ll have a web interface for this as we tidy things up and enter the beta stage.
We’ll be honest: this is going to be a bit of a learning curve for us. Running an API is hard. And mapping the concepts of print layout to an API is hard. So it’s likely that we won’t have got it right first time. Do let us know your thoughts.