The API now supports JSON encoding for the result of any method. (We added it to support our soon-to-be-released Javascript and Python API libraries.) To get a result in JSON, just replace /rest in the method URL with /json and send along the same arguments. For example:
http://api.evdb.com/rest/events/search?app_key=...&q=ditty+bops
http://api.evdb.com/json/events/search?app_key=...&q=ditty+bops
It's just that simple. All methods are supported, including all options listed in the API documentation. There are a few caveats: methods that don't ordinarily return XML (like /events/ical) will return an empty object, and any error result will return an empty object. Also, JSON isn't supported as an input format, although we could probably set that up if there's interest.
Question for lightweight markup fans: now that we have JSON support, is there any reason to provide YAML support as well?
[UPDATE: Paul informed me that it's possible to provide output that's both valid JSON and valid YAML. We're updating our JSON formatter to use that format, and it should be available in the next day or three. Thanks, Paul!]
