LstMeetingAttendee
Retrieves the attendees information of a session hosted on the site. The
session can be one of all the WebEx session types including Meeting
Center, Training Center, Event Center, Sales Center, or
Teleconference-only sessions.
Request
The following schema diagram shows the structure of the elements in thelstMeetingAttendee request message.
Figure 11-8 • Schema diagram for lstMeetingAttendee
The sample XML document is a query for all meeting participant
services for the meeting that received the WebEx-generated meetingKey
value of 82679427. Be sure to use a valid value for a meeting of one of
the users on your website.
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<header>
<securityContext>
<webExID>hostid</webExID>
<password>hostpassword</password>
<siteID>0000</siteID>
<partnerID>9999</partnerID>
<email>johnsmith@xyz.com</email>
</securityContext>
</header>
<body>
<bodyContent
xsi:type="java:com.webex.service.binding.attendee.LstMeetingAttendee">
<meetingKey>82679427</meetingKey>
</bodyContent>
</body>
</serv:message>
For descriptions of the global elements in the security context of the
header, see Global Request Elements in Security Context. For
descriptions of the non-global elements, refer to “Elements in WebEx XML
Schema Definitions for the Meeting Attendee Service”.
Response
The following schema diagram shows the structure of the elements in thelstMeetingAttendeeResponse message.
Figure 11-9 • Schema diagram for lstMeetingAttendeeResponse
The sample XML document shows an example of a possible response for the
preceding query XML document.
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service"
xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="att:lstMeetingAttendeeResponse"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<att:matchingRecords>
<serv:total>3</serv:total>
<serv:returned>3</serv:returned>
<serv:startFrom>1</serv:startFrom>
</att:matchingRecords>
<att:attendee>
<att:person>
<com:name>James Kirk</com:name>
<com:firstName>James</com:firstName>
<com:lastName>Kirk</com:lastName>
<com:address>
<com:addressType>PERSONAL</com:addressType>
</com:address>
<com:phones />
<com:email>Jkirk@sz.webex.com</com:email>
<com:type>VISITOR</com:type>
</att:person>
<att:contactID>28410622</att:contactID>
<att:joinStatus>INVITE</att:joinStatus>
<att:meetingKey>803754412</att:meetingKey>
<att:sessionKey>803754412</att:sessionKey>
<att:language>ENGLISH</att:language>
<att:role>ATTENDEE</att:role>
<att:locale>U.S.</att:locale>
<att:timeZoneID>4</att:timeZoneID>
<att:languageID>1</att:languageID>
<att:attendeeId>28410622</att:attendeeId>
<att:confId>65102084</att:confId>
<att:status>
<att:invited>true</att:invited>
<att:registered>false</att:registered>
<att:rejected>false</att:rejected>
<att:accepted>false</att:accepted>
</att:status>
</att:attendee>
<att:attendee>
<att:person>
<com:name>test2</com:name>
<com:firstName>test2</com:firstName>
<com:address>
<com:addressType>PERSONAL</com:addressType>
</com:address>
<com:phones />
<com:email>test2@webex.com</com:email>
<com:type>VISITOR</com:type>
</att:person>
<att:contactID>28411092</att:contactID>
<att:joinStatus>INVITE</att:joinStatus>
<att:meetingKey>803754412</att:meetingKey>
<att:sessionKey>803754412</att:sessionKey>
<att:language>ENGLISH</att:language>
<att:role>ATTENDEE</att:role>
<att:locale>U.S.</att:locale>
<att:timeZoneID>4</att:timeZoneID>
<att:languageID>1</att:languageID>
<att:attendeeId>28411092</att:attendeeId>
<att:confId>65102084</att:confId>
<att:status>
<att:invited>true</att:invited>
<att:registered>false</att:registered>
<att:rejected>false</att:rejected>
<att:accepted>false</att:accepted>
</att:status>
</att:attendee>
<att:attendee>
<att:person>
<com:name>test1</com:name>
<com:firstName>test1</com:firstName>
<com:address>
<com:addressType>PERSONAL</com:addressType>
</com:address>
<com:phones />
<com:email>test1@webex.com</com:email>
<com:type>VISITOR</com:type>
</att:person>
<att:contactID>28411097</att:contactID>
<att:joinStatus>INVITE</att:joinStatus>
<att:meetingKey>803754412</att:meetingKey>
<att:sessionKey>803754412</att:sessionKey>
<att:language>ENGLISH</att:language>
<att:role>ATTENDEE</att:role>
<att:locale>U.S.</att:locale>
<att:timeZoneID>4</att:timeZoneID>
<att:languageID>1</att:languageID>
<att:attendeeId>28411097</att:attendeeId>
<att:confId>65102084</att:confId>
<att:status>
<att:invited>true</att:invited>
<att:registered>false</att:registered>
<att:rejected>false</att:rejected>
<att:accepted>false</att:accepted>
</att:status>
</att:attendee>
</serv:bodyContent>
</serv:body>
</serv:message>
The result and exceptionID global elements allow you to confirm that
an instantiation request was successful. These elements are described in
“Global Response Elements Showing Results and Errors”.