Welcome, Guest Sign In | Sign Up | Help
Upcoming API Documentation
Currently, the use of these APIs are restricted to non-commercial use only. If you'd like to use it for commercial purposes, please contact us first.
venue.getList [HTTP GET]
Retrieve a list of venues for a particular metro.
Arguments
api_key (Required)
Your API application key. If you don't have one, create one.

metro_id (Required)
The metro_id number of the metro to look within. To find metro_id's, use metro.getList.

token (Optional)
An authentication token. Pass to return private venues. (What's this?)

Response Notes

Within the response, several geographical parameters have been added that refer to the geolocation of the underlying venue of the event. These include latitude and longitude, as well as geocoding_precision, which specifies the precision to which the venue address could be found and geocoded, and also the geocoding_ambiguous parameter, which serves as a warning that the geocoding is likely to be erroneous.

Any venue that could not be geocoded at all will have blank values in the fields.

Example Response
<?xml version="1.0" encoding="UTF-8"?>
<rsp stat="ok" version="1.0">
	<venue 	id="2047" name="14 Below" city="Santa Monica" url="http://www.14below.com" 
			user_id="2756" private="0" 
			latitude="37.9183" longitude="-122.024" geocoding_precision="zip" 
			geocoding_ambiguous="0"/>
	<venue 	id="993" name="1650" city="Los Angeles" url="" user_id="2756" private="0" 
			latitude="37.9183" longitude="-122.024" geocoding_precision="zip" 
			geocoding_ambiguous="0"/>
	<venue 	id="754" name="33 1/3 Books and Gallery" city="Los Angeles"
			url="http://www.echoparkfilmcenter.org/" user_id="1" private="0" 
			latitude="37.9183" longitude="-122.024" geocoding_precision="zip" 
			geocoding_ambiguous="0"/>
	<venue 	id="3027" name="5th and Sunset" city="Los Angeles" url="" user_id="845" 
			private="0" 
			latitude="37.9183" longitude="-122.024" geocoding_precision="zip" 
			geocoding_ambiguous="0"/>
	...
</rsp>		
Error Code (sent in HTTP Response Header)
403 Not Authorized:
  • Invalid authentication parameters - either that token was not found, or it may be deactivated. Please contact us for support.

404 Not Found:
  • Missing valid api_key - Please create an API key using the above link.
  • Your api_key is inactive or not found - Please contact us for support.
  • Missing valid metro_id parameter - Your metro_id may be improperly formatted or non-numeric. Only numeric metro_id's are allowed.
Tools
Upcoming Badges for Your Blog/Website | Invite Friends | Groups | Developers API
Help
News Blog | Community Guidelines | FAQ | Contact Us | Suggestion Board