This documentation is archived and is not being maintained.

Live Meeting service API

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Microsoft Office Live Meeting service API consists of XML-based messages that communicate between an Office Live Meeting conference center and a client application.

An application using the Live Meeting service API interacts with a Live Meeting conference center by sending a request in XML to the conference center. The incoming message goes through the Live Meeting service API processor and is translated to appropriate queries that are run against the specified conference center. The query result is then returned as a reply message, also in XML, to the calling application. Because the Web user interface is the gateway to interactive user sessions, the API processor serves as the gateway for programmatic access to a Live Meeting conference center.


The Live Meeting service API provides programmatic access to Live Meeting services, including meeting management, user management, recording and content management, security services, and reporting. The API also enables developers to customize their business solutions built on the Live Meeting technology. Common usage includes single sign-on (SSO), integration with other applications (for example, providing custom user interface and branding, and starting a meeting from a reporting application) and productivity tools, and the extension of Live Meeting features by way of add-ins.

Communication is based on the standard HTTPS protocol. As such, the API can be used in applications written in different languages, for example, ASP.NET, Visual C#®, Visual C++®, and Java and for different platforms, such as Microsoft Windows®, Mac OS, and Linux/UNIX.

A client using the API to transmit and received XML messages has the ability to include user input of a malicious nature. The Live Meeting database servers do not filter or encode XML data received from a client. This same data is sent to other API clients as XML response data from a Live Meeting server. The client is responsible for protecting itself from such malicious messages as SQL injection or XSS strings.

The Live Meeting service API can be used for managing:

  • Meetings, including creating meetings, modifying a meeting, deleting a meeting, reassigning ownership, storing metadata about a meeting, and performing batch processing of other administrative tasks.

  • Users and groups, including creating users, retrieving and modifying user profiles, deleting users, setting default configurations for users, creating groups, modifying groups, and deleting groups.

  • Content, including uploading meeting content and downloading meeting recordings.

  • Attendance and creating reports, including querying meetings held in a specified time period; searching for meetings by name, ID, billing, owner, or title fields; selectively displaying meeting participant information; reporting polling results; and showing the number of seats used in a given period of time.