Fork me on GitHub

API Voice Blog

My Continued Support As Signer Of Oracle v Google Amicus Brief From EFF

Posted on As the Oracle v Google API copyright case was on its way to the Federal Circuit Court in 2012, the EFF reached out to me for help in crafting stories of how important it is that APIs remain free of copyright, ensuring they remain open and interoperable. I shared three stories, one on cloud computing and AWS APIs, the second on Delicious APIs, and the third on Instagram APIs, all reflecting three different scenarios that would never have happened if APIs were copyrightable. A couple weeks ago EFF reached out again, asking for my signature again, on another more.

We Only Launched An API When It Helps Us, But We Will Act Like It Is Was For You

Posted on

Hacker News launched an API today, complete with real-time features. Hacker News was created by Paul Graham in February 2007, and in October 2014 they are launching an API, something that is clearly innovation and forward thinking at work--not. Don’t get me wrong, I love me some APIs (if you hand’t notice), but waiting seven years to launch your API, as one of the “leading” technology news sites, ran by one of the “leading VC firms”, is not something to celebrate. The irony of the release will be celebrated by the HN community, the larger tech community, and sadly more.

Reworking My API 101 Content And First Up Is The 100K View

Posted on

The home page of API Evangelist has always been my API 101 page, where any new visitor can land, not know a thing about APIs, read the page, and walk away understanding at least what an API is, and hopefully also a greater understanding of how it impacts their world. From the beginning the API Evangelist home page always had a lean toward API providers, and over time I've added information about consuming APIs, as well as trends in the API space I'm seeing. In my opinion my 101 content has become too lengthy, and not properly onboarding people more.

Introducing API.Report, A Community API News Site

Posted on

I curate a lot of interesting stories across the API space from my RSS feeds, the Twittersphere, and my overactive email inbox each day. Only a small percentage of these stories ever make it to my business of API analysis site, or my politics of APIs analysis at Over the summer, this got me thinking, and while wandering around Detroit after API-Craft Detroit this last July, Steve Willmott (@njyx) and I were talking about the rapidly expanding API space, and both felt there was a gap in the news reporting for the API sector. ProgrammableWeb (PW) does a good more.

API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing

Posted on

There was a very interesting piece from venture capitalist Albert Wenger (@albertwenger) of Union Square Ventures over the labor day weekend, called Labor Day: Right to an API Key (Algorithmic Organizing), that I’ve had open ever since and wanted to take a moment to add my thoughts to. First let me say, I agree 100% with Albert’s post, but I felt that the piece left out some very critical elements, which I think Albert simply left out because he was just trying to get a short thought published over a holiday weekend, but I feel pretty strongly these points are more.

You Can Have An API Just By Choosing Products And Services That Have APIs

Posted on

When it comes to APIs, the quickest way to get an API for your company, organization or government agency is to choose to only use online services that have APIs. Twitter, Facebook, Google, Dropbox, Github, Instagram, Flickr, and many other popular services you already use, all have APIs. As I’m expanding on my tracking of API deployment tools, to include deploying APIs via Google Spreadsheets, and to scraping data from websites, I can’t help but step back and consider truly what is the easiest way to deploy an API, which really is about choosing to use online services that more.

If We Cannot Keep the Pipes Transparent And Accessible We Are Screwed

Posted on

As I look through the 800+ companies that I'm tracking on doing interesting things in the API space, I can't help but think about how important it is that we encourage API providers to inject as much transparency into their operations as possible. Something that includes providing end-users consistent account management, and oAuth controls, as well as developer transparency. It is not enough to just make API resources are publicly available, you have to be transparent in your pricing, roadmap, terms of use, and overall API operations--you have to be honest, open, and communicate with your API consumers, and more.

Taking A Look At The API Licensing Stack

Posted on

One of the byproducts of the Oracle vs Google API copyright case, was a realization that many API providers and consumer do not understand the layers of the API stack, let alone the potential licensing considerations for each layer of the API onion. I wouldn't just blame API providers, and consumers, I’m still getting a grasp on all of this, which is why I'm blogging about the subject. Let’s take a quick crack at defining the layers to the potential API licensing onion: Data - What is the licensing for the actual data returned and collected by an API? I’ more.

Machine Readable Terms Of Service Didnt Read Applied To Apis Via Apisjson

Posted on

I’ve long been fascinated by the Terms of Service Didn’t Read project. i’m on the mailing list, and try to make time to stay in tune, but have yet to ever contribute any bandwidth to the EXTREMELY important project, around making sense of the crazy terms of services (TOS), that we agree to in our daily lives. I finally found myself at a point where I'm forced to start paying more attention to API terms of service, and hopefully will be able to slice off a little bit of dedicated bandwidth to Terms of Service; Didn’t Read. I have more.

Hipster Coffee Shop Interface

Posted on

I’m continuing to expand on my restaurant API analogy, to be used when helping people understand the API copyright debate. A restaurant menu works well to get folks on boarded with the separation between an API definition, its server side, and client side code—when compared with the restaurant menu and the behind the scenes kitchen. My expansion this week is from an experience in a hipster coffee shop, while meeting a client in San Francisco. I walked into this small coffee shop, and there was no menu, just a list of beans on a chalkboard, several lines of customers more.