Once we started updating the REST API, we just couldn’t stop. Here’s a list of what’s new as of last night:

• New API Methods:
  • venue_events: list events occuring at a venue
  • venue_tags: list tags associated with a venue
  • tag_events: list events associated with a tag
  • tag_by_name: retrieve tag information by tag name
  • user_add_event: add an event to a user calendar
  • user_remove_event: remove an event from a user calendar
  • event_add_tag: add a tag to an event
  • event_remove_tag: remove a tag from an event
  • venue_delete: delete a venue and all events occuring at the venue
• New options for constraining event lists by date and time. All the methods that return event lists (e.g., group_events, venue_events, tag_events and user_events) support the sd and ed parameters for constraining the returns list to events that occur within a specific date range.
• New Message option for the event_cancel and event_delete methods. When cancelling or deleting and event, this option allows you to send an arbitrary text message to users that have added this event to their calendar.
• The RSS output format includes the xCal extensions for specifying date and time location for events and venues. There’s an example on this page.

Read the API documentation for details on all the new methods and parameters.

-Shane

If you enjoyed this post, make sure you subscribe to my RSS feed!

We recently appeared at IBDN’s Under the Radar conference. It was a great experience for us—the most fun was being up on stage with CalendarHub, Mosuki, and Skobee, all of whom said they want to take events and advertising from Zvents. I was interviewed in a podcast by Cathy Brooks of the GuideWire Group, speaking about both Zvents and Web 2.0 in general.

-Shane

If you enjoyed this post, make sure you subscribe to my RSS feed!

We’ve just pushed a series of changes to our REST API that make it both easier to use and more flexible. Here’s whats new:

• Improved Documentation – We just finished writing much more detailed documentation on supported methods, output formats and error messages. Read the documentation here.
• New Output Formats – The REST API now supports XML, RSS and JSON output formats. This applies equally to the regular output of the REST interface and to any error messages you may encounter along the way. Read about the output formats here.
• New Methods – We’ve added methods for cancelling events, listing events created by specific users and updating group definitions.

Through the magic of method aliasing, these changes are almost entirely backwards-compatible with the previous version of the REST interface. However, the output of several methods has changed. We are now returning much more information for each method call which should make it significantly easier to use the API. In the previous version, most methods would return a list object IDs. This necessitated an additional call(s) to the API to retrieve information for the object IDs. Now, we simply return all information available for all objects. This saves the round-trip, cuts down on the number of calls to the server and generally makes your life easier.

Feel free to send an email to support <at> zvents.com if you have any questions or notice any problems.

I’m not done yet. Sometime in the next week we’ll roll out the following enhancements:

• Many more method calls
• Additional parameters allowing you to easily constrain returned events by date ranges

-Shane

If you enjoyed this post, make sure you subscribe to my RSS feed!