Hi Nancy, I notice that the 'country' parameter has a %20 in it, though the others appear to be unencoded. Is it possible you're double-encoding the %20? When I do that as a test, I get the same "Unable to add venue" you're getting.
http://api.eventful.com/rest/venues/new?...&name=DiversityWorks%20Worshops&country=United%2520States&address=800%20Heinz%20Ave.%20%2314&city=Berkeley®ion=CA&postal_code=94710&venue_type=Community%20Center Note the double encoding of "United%2520States", versus the single encoding of "Community%20Center". If that's the culprit, I'll see what I can do to improve the error message it generates. It doesn't seem to be bubbling up the "country not found" error that it encounters at a lower level. Cheers, ~chris On Jan 17, 2011, at 10:57 AM, Nancy Tubbs wrote: > Hi Chris, > > This is what I'm posting; your version doesn't have the # in the address, nor > the venue type field but otherwise it looks the same. > > BTW, are you still using the venue type field? Should I use the values, > rather than the display text? > > Thanks! > Nancy > > > "name" value="DiversityWorks Worshops" > "address" value="800 Heinz Ave. #14" > "city" value="Berkeley" > "region" value="CA" > "postal_code" value="94710" > "country" value="United%20States" > "venue_type" value="Community Center" > "app_key" value="xxxxxxxxx" > "user" value="xxxxxxxxxx" > "user_key" value="xxxxxxxx" >
