developer love > ClubWiki

In the spirit of peace, love and trendiness, ClubWiki makes all of its venue data freely available via an XML interface (subject to your ability to remain conscious while reading our Terms of Use). Still with us? Read on!

Getting Club XML

XML for a club can be fetched from http://clubwiki.org/club_xml by specifying either the "id" or "name" arguments. The club id uniquely identifies a club, so you will get information for one specific club. The "name" argument will return XML for all clubs with an exact name match, but results can be narrowed down by providing a "loc" argument which specifies a geographic location. The loc argument can be anything which will geocode to a location, but is generally intended to be a city. Clubs within a 50 mile radius of the geocoded location will be returned.

Example request urls

Get XML for the club with id 216:
http://clubwiki.org/club_xml?id=216
Get XML for all clubs named "Elbo Room" (many results):
http://clubwiki.org/club_xml?name=Elbo%20Room
Get XML for clubs named "Elbo Room" in Chicago (1 result):
http://clubwiki.org/club_xml?name=Elbo%20Room&loc=Chicago,%20IL

Response XML

The response will be an XML document with a root <results> element containing 0 or more <club> elements as children. The <results> element contains a "count" attribute indicating how many clubs are contained. The <club> element contains the following children [1]:

<name>: The club name
<description>: The club description
<url>: The url to the club's own website [2]
<phone>: Club phone number
<fax>: Club fax number
<full_address>: The fully-qualified address as returned from geocoding.
<location>: The location as entered by the user (before geocoding)
<street_address>: The street number and name
<city>: City returned from geocoding
<state_prov>: The state or province returned from geocoding
<postal_code>: The postal code (zip code in the US) returned from geocoding
<country>: The country returned from geocoding
<lat>: The latitude returned from geocoding
<lng>: The longitude returned from geocoding
<admittance>: Club admittance age restrictions
<gear>: Descriptive string of house gear
<booking_name>: Booking contact name
<booking_email>: Booking contact email address [3]
<booking_phone>: Booking contact phone number
<booking_hours>: Booking contact hours restrictions
<booking_info_url>: Booking "more info" url [2]
<booking_form_url>: Booking online form url [2]
<mod_date>: Last modified date
<rss_link>: URL to RSS feed for changes to this club
<genre> (multiple): Each genre entry contains a single genre from the comma-seperated "music styles" list
<photo> (multiple): A photo entry has the children defined in the photos section below.
<show> (multiple): A show entry has the children defined in the shows section below.

Photos

Photos are represented by a series of <photo> elements, each containing the following children [1]:

<url>: The URL to the full size photo
<thumb>: The URL to the thumbnail photo
<num>: The slot number, from 1-5, which this photo goes in on the club page
<width>: Photo width in pixels
<height>: Photo height in pixels

Shows

Shows are represented by a series of <show> elements, each containing the following children [1]:

<band_name>: The name of the band
<date>: The date of the show

Notes

[1] Fields which do not have set values will not be present
[2] URLs are not always strictly well-formed URLs. ClubWiki is somewhat permissive about what it will recognize as a URL and turn into a link. For example, "example.com/somepath", is assumed to mean "http://example.com/somepath".
[3] Email addresses may be obfuscated, such as "user [at] somesite [dot] com"