March 31, 2006
New: JSON output from any EVDB API method
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!]
Posted by chris at 10:15 AM | Comments (0)
March 09, 2006
New: Performers and Demand
If you haven't seen it yet, check out our most exciting project to date: Eventful Demand. It's a way to make your dream events happen by showing a performer that there's already an audience waiting. I've already started using it myself.
As with all Eventful features, there's already a complete API for demand including lots of new functionality for performers. Documentation for the relevant API calls is being written as I write this. (OK, I'll get back to it as soon as I finish.) Keep an eye on the documenation page; I'll post an update to this post once the update is available.
Posted by chris at 02:47 PM | Comments (0)