Blog

Phish.net API 2.0 nears rollout (Blog)

September 16, 2010 - By Brando Rich

Posted from Phish.net...( http://blog.phish.net/ )

Phish.net API 2.0 nears rollout

Our webmaster, Adam Scheinberg (sethadam1), is putting the finishing touches on an updated and improved version of the Phish.net API. API is an acronym for "Application Programming Interface", or in non-computerese, bits of programming code often called "hooks" or "plug ins" that allow for third-party developers' websites and programs to interact with the Phish.net site and its online fan community.

The 2009 1.0 APIs allowed data such as new setlists to be "pushed" to other fan websites (almost all now use the Phish.net feed), or the ability to search and access our historical setlist and song databases from other sites.

The updated 2.0 APIs will allow an enhanced range of interactions. For instance, it is already possible with just the existing APIs to feed the forum or selected threads to other sites, and to post back TO the Phish.net forum from those other sites.

Even more exciting are things which would allow Phish.net users to hook into related sites, such as social networking or community non-profit ticket trading websites, such as cashortrade.org.

As an example, a user registered on both Phish.net and a trading site such as cashortrade.org could on an entirely "opt in" basis use his/her username and single login on both sites, so (unlike anonymous websites like craigslist or eBay where trust is an issue) traders would know who they were dealing with and communicate by PM or chat.

The APIs are also designed to assist in cross-platform integration of the Phish.net database contents with mobile devices such as smartphones, not only allowing setlists to be searched and updated at shows, but allowing Phish.net forum "friends" to be located in real time in tour cities and venues (to give just one example).

The 2.0 APIs also allow for the highest levels of security and trust when sites exchange information, since the Phish.net API now operates under a trust certificate that will allow for secure information exchange and 256-bit encryption (that is, a "secure" "https://" site) so that, for instances, private information such as user passwords will not be transmitted across the internet in cleartext, but encrypted.

This summary is decidedly non-technical. As the Mockingbird Foundation's counsel and secretary, I handle the administrivia and legal side of things. I confess that I have basically just scratched the surface of the technical detail that Adam's provided in the extensive documentation at the Phish.net API homepage at https://api.phish.net.

But, from talking with Adam and several of the developers who have already asked for some of these features and told us about their plans, I'm excited that the version 2.0 APIs will allow for new opportunities for the Phish.net community to be sharin' in the groove.

I'd encourage all of you Phish fans with awesome code monkey skills and a little time to waste to check out the phresh APIs.

And then write a great app! Happy coding!