Calendar-WS: Programmatic Access to Online Campus Calendars

Calendar-WS is a Web Services interface to CalAgenda, the shared calendaring system on the University of California, Berkeley campus.

If you are a developer of a campus or departmental application, this interface makes it possible for your application to interact directly with specified campus calendars. You can use this interface to find, add, and delete meetings, room and equipment reservations, and similar types of events on calendars for people, roles, resources, and events.

Service Status

(Current as of Tuesday, 13-May-2008 12:52:15 PDT)

Server certificate updated on May 13, 2008: A new server certificate was installed on May 13, 2008, replacing an expiring certificate. This change should be transparent to most users. If you notice any issues, please send email to or call Aron Roberts at (510) 642-5974. In the unlikely event that your SOAP toolkit requires that you download and locally store a copy of the relevant certificates, you can obtain these from the sample code page.

addDailyNote procedure added to test server on July 27, 2007: A new remote procedure, addDailyNote, was added to the test server on July 27, 2007. You are invited to test this procedure, which for the first time allows you to programmatically add "Daily Notes" - notes that are attached to entire days - to a CalAgenda calendar.

In the desktop Oracle Calendar application, Daily Notes are displayed below the timed events with "pushpin" icons, and can be useful for adding notes about deadlines, reminders and the like to calendar dates.

The WSDL description of the test service, which now includes this new remote procedure, is accessible at: https://calendar-ws-test.berkeley.edu:8004/calendaraccess/services/CalendarAccessImpl.wsdl. Calling addDailyNote is nearly identical to calling the existing addEvent remote procedure, with only two minor differences:

Send a single String parameter named 'date' to addDailyNote in place of the two String parameters named 'start' and 'end' that you would send to addEvent. Values for this 'date' parameter are in the format 'YYYYMMDD' (e.g. "20070727") in the local Berkeley ("US/Pacific") timezone.
Omit the 'location' parameter, which is not used by addDailyNote.

Server certificate updated on May 14, 2007: A new server certificate was installed on May 14, 2007, replacing an expiring certificate. This change should be transparent to most users. If you notice any issues, please send email to or call Aron Roberts at (510) 642-5974. In the unlikely event that your SOAP toolkit requires that you download and locally store a copy of the relevant certificates, you can obtain these from the sample code page.

Server certificate updated on May 10, 2006: A new server certificate was installed on May 10, 2006, replacing an expiring certificate. This change should be transparent to most users. If you notice any issues, please send email to or call Aron Roberts at 642-5974. In the unlikely event that your SOAP toolkit requires that you download and locally store a copy of the relevant certificates, you can obtain these from the sample code page.

Service goes into production on February 22, 2006: The Calendar-WS Service went into production and was pointed at "live" calendars on the campus calendaring service, CalAgenda, beginning at 5:00 pm PST on Wednesday, February 22, 2006.

Test server: A second, test instance of the service is also available for your use on calendar-ws-test.berkeley.edu. That test instance of the service points at a test calendar server, which contains an older, static copy of CalAgenda's calendars.

This gives you the opportunity to fully test your Web Services client code without altering "live" calendars on CalAgenda itself. In addition, this test instance of the service allows you to test enhancements and bugfixes to the service before they go into production.

Get Started

Review the Web Services interface.: Read the detailed description of the Calendar-WS Web Services interface (updated July 31, 2006) for finding, adding, updating, and deleting events in CalAgenda. This can help you determine whether this interface will meet your application's requirements.
Tell us about your application.: To discuss the possibility of integrating your own departmental or campus application with CalAgenda via this interface, please send email to
Get a calendar account.: When you're ready to start, request a calendar account for your application. Your application will authenticate to the Web Services interface as the user of that account. (In addition, you can also use any of several test accounts which have already been set up for shared use by all developers.)
Set up designate and viewing rights on the calendars you wish to access.: Use the Oracle Calendar native client program for Windows, the Mac OS, or various Unix OSes to set up full designate and viewing rights for your application's calendar user account on each of the calendars which your application wishes to view or edit.
Get coding!: Select a Web Services toolkit and start writing code to integrate your application with campus calendars, by calling the remote procedures offered by the Calendar-WS Web Services interface.
Report bugs and request feature enhancements.: Your feedback is encouraged: please report bugs and request feature enhancements in the Calendar-WS service.

About the Calendar-WS service

Functional Specifications: Summary (DRAFT) (updated July 31, 2006): A high-level summary of the functional specifications for the service. This summary discusses why the service was developed, what design considerations were involved, and several of the alternative methods through which you can also programmatically access CalAgenda calendars.