2014-26-August-In-The-Air.jpgSay it ain't so, Joe! API fans everywhere suffered a heartbreaking defeat when one of the most prominent public content APIs packed it in and said there might not be a next season.

Sudden Death for the ESPN API

Earlier this month on its developer website, ESPN released a notice stating that it would stop issuing public keys for it's API and would also start the process of shutting down current users of its free content as a service offering. Stating what everyone already knew -- sports is a business like any other -- ESPN cited financial reasons for the shutdown. Based upon the content monetization business model, one can assume that the site traffic generated by the content syndication did not generate the return that ESPN was hoping for.

Dear ESPN API Developers,

Since the launch of the ESPN Developer Center in March 2012 the capabilities and direction of our API program have continued to evolve in order to serve sports fans in the best way possible.

As part of that evolution, we have made the difficult decision to discontinue our public APIs, which will enable us to better align engineering resources with the growing demand to develop core ESPN products on our API platform.

Effective today, we will no longer be issuing public API keys. Developers utilizing the ESPN API with a public API key may continue to do so until Monday, December 8, 2014, at which point the keys will no longer be active.

We want to thank all of you for supporting the ESPN API, and we hope you found value interacting with the service over the past two years.

While ESPN may have been thrown out in trying to stretch a single to a double, it's an overreach to say this is the beginning of the end for every public API. Even if it is the end, it surely isn't the beginning. Last year tons of API shakeups happened between Twitter, Apple, Facebook, Tumblr and LinkedIn and we can expect to see many more such shakeups to come.

Reading Between the Lines

While my sources at ESPN have not commented, one can reasonably infer that someone at ESPN took a look at the financials. Top line ad revenue generated by traffic from content syndicated by the pubic API wasn't enough to cover the costs of maintaining the gateway along with the public support channel and developer outreach programs.

Some questions do, however, remain: 

Was the cost of data defense taken into account? Once the wall went up around the content, you can assume that a few people in the crawling and scraping communities across the internet yelled “BOOYAH!” at the prospect of seeing their business development pipeline heat up. Rest assured, content that has an audience but not an API will sooner or later be scraped by someone trying to build a business off the stolen content.

ESPN is sure to remember that just like there's no crying in baseball, there's no crying in the content business. In responding to scrapers, there's two options and crying isn't one of them. Pay to protect your data (which has dubious efficacy at best) or open a governed API with methods to make money off the referred.